Resources
Reference guides for understanding Giga's features, terminology, common questions, and troubleshooting.
The Resources section is the quickest place to get oriented across Giga’s product model.
Use it when you need a compact reference, want to choose the right Giga feature, or need help diagnosing something that is not working as expected.
Reference guides
Feature Overview
See the main Giga primitives, how they fit together, and which problems each one solves.
Giga Dictionary
Look up Giga terminology such as Chat, Group, Track, Context Note, Agent, Skill, Workflow, Pulse, and Connection.
Choosing the right Giga feature
Start from what you are trying to do and choose the Giga primitive that fits.
FAQ
Find concise answers to common product questions.
Troubleshooting
Work through common access, context, Connection, file, and product-behavior issues.
The core Giga model
Giga is organized around a small set of primitives.
| Primitive | What it is for |
|---|---|
| Chat | Direct work with Giga |
| Group | Placement and permission scope |
| Track | Ongoing work with continuity |
| Context Note | Durable standing Track background |
| Agent | Named reusable AI role |
| Skill | Reusable task method or instructions |
| Workflow | Reusable ordered process |
| Pulse | Recurring scheduled work |
| Connection | Permissioned access to an external system |
These primitives can be combined around the way your team actually works.
Company Brain underneath the work
Giga’s Company Brain is the permission-aware company context layer available to the current task.
Depending on relevance and access, it can draw from:
- workspace and Group guidance
- Tracks
- Context Notes
- Observations
- Current Track State
- files
- Connections and live external data
- Agents
- Skills
- Workflows
- user-level context
The live workspace remains the source of truth for what a user or Agent can actually access.
Use Giga across different surfaces
Giga can be used from:
The same core Giga model and permission boundaries stay underneath, while file handling, rich UI, and exact tool availability can differ by surface.
Product behavior stays live
Some parts of Giga are dynamic by design.
Current workspace membership, Connections, model availability, provider capabilities, permissions, schedule slots, and surface-specific features should be resolved from the live product rather than treated as fixed documentation facts.
Use the docs for the product model. Use the live workspace for the current state.
Where to go next
New to Giga?
Start with the product introduction and learn how the main pieces fit together.
Know what you want to do?
Match your task to a Chat, Track, Agent, Skill, Workflow, Pulse, Connection, or other Giga primitive.
Image placeholder
Giga product map showing Company Brain and permissions underneath Chats, Tracks, Agents, Skills, Workflows, Pulses, and Connections.