Giga Dictionary
Definitions for the core terms used across Giga.
Use this page as a quick reference for Giga’s product language.
The definitions below follow the current Giga product model. Exact workspace state, permissions, provider capabilities, and model availability still come from the live environment.
Agent
An Agent is a named reusable AI role in Giga.
An Agent can have a role, instructions, context, access to permitted Connections, and Skills.
Use an Agent when a reusable operating identity should be available across multiple tasks, people, or repeated interactions.
Brain
Brain is where your memory lives in the Giga web app. It shows current memory by type, the To file inbox, the Evidence log and Brainstorms, and lets you add memory by pasting notes or importing a link.
Chat
A Chat is the direct working surface between a user and Giga.
Use a Chat to ask questions, reason through work, create or edit supported work product, use Connections, and ask Giga to take supported actions.
A Chat can be linked to at most 1 explicitly selected Track.
Chat history
Chat history is the transcript of the interaction inside a Chat.
It is separate from durable Track context such as Context Notes, memory, and files.
Company Brain
Company Brain is Giga’s permission-aware company context layer.
Depending on relevance and access, it can draw from workspace and Group guidance, Tracks, Context Notes, memory, files, Connections, Agents, Skills, Workflows, and user-level context.
Company Brain is structured around permissions and the work it belongs to.
Connection
A Connection gives Giga permissioned access to an external system.
Connections can represent apps, APIs, databases, MCP servers, browser sessions, messaging systems, and other supported services.
A Connection can provide live information and support actions when the current Giga and provider permissions allow it.
Context Card
A Context Card is background information kept in the Library, such as who you are, what your company does, or how a Track works. Giga adds it to every relevant chat, like a briefing it always reads first.
Context Note
A Context Note is the durable standing context for a Track.
Use it for stable background such as:
- what the Track is about
- standing instructions
- terminology
- durable constraints
- long-lived handoff context
Fast-changing progress and decisions belong in Track memory.
Credential
A credential is secure authentication material behind some Connections.
Examples can include authentication tokens, API credentials, connection strings, or login material depending on the Connection method.
Credentials are kept in the Vault and should stay in the secure connection flow rather than ordinary Chats, Context Notes, or files.
Database
A database is a structured store for records that are repetitive, tabular, updated field by field, filtered, sorted, aggregated, or expected to grow.
Current Giga doctrine supports SQLite and hosted Giga databases where the relevant capability is available.
Use files for authored narrative work such as reports and drafts.
File
A file is authored work product.
Files can hold reports, drafts, notes, code, webpages, exports, and other supported artifacts.
Files are separate from Track memory. A Track can have rich context and history even when its file area is empty.
Group
A Group is a placement and permission scope in Giga.
Groups can contain or scope resources such as Tracks, Agents, files, credentials, Connections, and shared context.
Use a Group when there is a real team boundary, shared area, or top-level access scope.
Evidence
Evidence is the append-only record behind each memory: what was said, a quote, who said it, when, and where it came from. Evidence is never rewritten. You can read all of it in Brain → Evidence log.
Instant tools
Instant tools are data tools and AI models your agents can use on Giga's account, with nothing to connect and no API key needed. Calls are paid from your workspace credits. You'll find them in Integrations → Instant. Instant tools are part of Giga Gateway.
Memory
Memory is what Giga knows about your company's work: one clear statement per memory, each with a type (decision, commitment, idea, request, preference, fact or procedure), who said it, and the evidence behind it.
Memory belongs to a Track and is visible to the people on that Track, or stays private to the person who saved it until they file it. It stays current: a new decision replaces the old one, and a commitment closes when someone says it's done.
Model provider
A model provider is a source of AI models Giga can use. Every workspace has the Giga managed provider; you can add your own keys for other providers in Vault → Model Providers.
Private Group
A private Group is a Group scoped to its owner.
Each member has an existing private Group for private work.
A separate Group is generally unnecessary simply to make a Track private.
Learn about Personal vs shared work →
Pulse
A Pulse is recurring scheduled work.
Use a Pulse when Giga should run a check or task on a schedule instead of waiting for someone to ask in a Chat.
A Pulse can target an Agent, target a Track, or run without a target.
Shared Group
A shared Group is a Group used for team work.
Membership in the shared Group helps determine which people can access the resources inside its permission scope.
Skill
A Skill is reusable instructions and supporting context for a specific kind of task.
Use a Skill when the reusable asset is primarily the method, rules, standard, template, or reference context for doing the task.
Surface
A surface is a user-facing interface where someone can work with Giga.
Current official Giga surfaces are:
- Giga Web
- Slack
- ChatGPT
- Claude
- Microsoft Teams
The underlying Giga context and permissions stay consistent, while exact UI, file behavior, and available capabilities can differ by surface.
Learn about using Giga anywhere →
Track
A Track is Giga’s core long-running work primitive.
Use a Track when context, decisions, files, and progress should accumulate around an effort over time.
A Track can contain durable context across Context Notes, memory, linked Chats, and files.
Track visibility currently follows the Group it lives in.
To file
To file is the inbox in Brain for memory saved without a Track. Items there are private to you, each with Giga's suggested Track. File them to a Track to share them with that Track's people, or keep them private.
Vault
The Vault is where the credentials behind your connections are kept: API keys, OAuth connections, logins, databases, browser sessions and model provider keys. Secrets are encrypted and never shown to the AI or sent back to your browser.
Workflow
A Workflow is a reusable multi-step process.
Use a Workflow when several meaningful ordered stages should be saved, standardized, or run again later.
Current Workflows can have a name, description, ordered steps, plain-language instructions, and optional runtime inputs.
Workspace
A workspace is the top-level Giga environment for a company or team.
Workspace membership, Groups, context, Connections, and other resources all sit within that environment.
The current workspace state is the source of truth for what a user can access.
Quick reference
| Term | Short definition |
|---|---|
| Chat | Direct work with Giga |
| Group | Placement and permission scope |
| Track | Ongoing work with continuity |
| Context Note | Durable standing Track background |
| Memory | What's been decided, committed, proposed and learned |
| Evidence | The record behind each memory |
| Brain | Where memory lives in the web app |
| Vault | Where credentials are kept |
| Agent | Named reusable AI role |
| Skill | Reusable task method |
| Workflow | Reusable ordered process |
| Pulse | Recurring scheduled work |
| Connection | Permissioned external-system access |
| File | Authored work product |
| Database | Structured growing records |
| Company Brain | Permission-aware company context layer |