Chat history
How Chats relate to Tracks, observations, and longer-running continuity in Giga.
A Chat is one interaction with Giga. Longer-running continuity is organized around the work itself, especially through Tracks, rather than relying on a raw transcript alone.
Chats and Tracks
A Chat can be linked to at most one Track. Giga should never silently choose that Track because Track attachment affects where observations from the Chat can become visible.
When a Track is explicitly selected, the Chat can contribute useful context to that ongoing body of work.
What carries forward
Giga separates several kinds of continuity:
- Chat history keeps the Chat itself.
- Observations capture durable things that happened or were learned.
- Track context holds standing background and instructions.
- Track state captures where the work currently stands.
This separation helps Giga retrieve the right kind of information instead of treating every past message as equally important.
For project history, start with the Track
For decisions, progress, or what changed, Giga should look at the relevant Track and its structured memory before relying on raw files alone.