Tracks

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?

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.

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.

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.

Learn more about Groups →

Track context and Current Track State

Tracks carry more than files.

Giga can use:

• standing context about what the Track is and how the work should be handled
• memory about things that happened or were learned
• Current Track State that helps Giga understand where the work stands and preserves the Track’s decision record
• authored files that people and Giga create over time

When someone asks about the latest progress, decisions, or what changed, Giga should use the Track’s structured memory before assuming that the answer lives in a file.

Track attachment affects visibility

Giga should never silently attach a Chat to a Track. The selected Track affects where observations from that Chat can become available, so the user should explicitly choose or confirm it.

Explore Tracks