Tracks
Learn how Tracks keep long-running work, context, files, and memory together in Giga.
A Track is the home for work that has continuity.
Use a Track when a subject will keep evolving over time, such as a client account, product launch, hiring effort, research project, ongoing function, or any other body of work where context and progress accumulate.
Instead of starting from scratch in every Chat, a Track gives Giga and your team a durable place to keep the information that belongs to that work.
Track overview
Video placeholder
Tracks overview video.
What lives around a Track?
Chats
Chats about the work can stay connected to the Track.
Context Notes
Keep standing background and instructions that Giga should know about the work.
Memory
Keep the Track's decisions, commitments, open questions and know-how current.
Files
Keep reports, drafts, code, documents, and other work product with the Track.
Image placeholder
Track anatomy diagram showing Chats, Context Notes, Memory, and Files around one ongoing body of work.
When should you use a Track?
A Track is useful when continuity matters.
Create or use one when:
- the work will continue across more than one Chat
- people need a shared understanding of what has already happened
- files, decisions, or research should stay attached to the same subject
- you want Giga to retrieve the right history without re-explaining the topic every time
- progress will accumulate over days, weeks, or months
For quick one-off questions that do not need durable context, a normal Chat may be enough.
How Tracks keep context useful
Giga separates different kinds of information instead of flattening everything into one giant history.
| Layer | What it is for |
|---|---|
| Context Notes | Standing background and instructions that should remain true across the Track |
| Memory | Decisions, commitments, ideas, open questions, preferences, facts and procedures |
| Files | Authored work product such as reports, drafts, code, documents, and data files |
| Chats | The Chats where people and Giga work through tasks |
This separation helps Giga retrieve the right kind of context for the question being asked.
Files and memory are separate
An empty Track folder does not mean the Track has no history. Files are work product, while Track context and memory are stored separately.
Tracks and Groups
Every Track lives inside a Group. The Group determines the access scope the Track sits inside.
| Use a Track for | Use a Group for |
|---|---|
| One ongoing project, area, client, or body of work | A broader people and permission boundary |
| Keeping subject-specific context and history together | Organizing who can access shared work |
| Files and memory related to one subject | Holding multiple Tracks and other shared resources |
A Track’s visibility currently follows the Group it lives in. Personal work should usually live in your existing private Group, while shared work belongs in an appropriate shared Group.
Track context and memory
Tracks carry more than files.
Giga can use:
- standing context about what the Track is and how the work should be handled
- memory: the Track's current decisions, open commitments, ideas, open questions, preferences, facts and procedures, each with the evidence behind it
- authored files that people and Giga create over time
When you start work in a Track, Giga reads its memory first. When someone asks about the latest progress, decisions, or what changed, Giga answers from the Track's memory before assuming the answer lives in a file.
Explore Tracks
Creating and organizing Tracks
Learn when to create a Track and how to keep your workspace organized.
Context Notes
Give a Track durable background and instructions.
Memory
Understand how Giga keeps useful continuity around long-running work.
Files in Tracks
Keep work product attached to the right body of work.
Sharing and permissions
Understand who can access a Track and why its Group matters.