Threads represent ongoing user-agent sessions. They are especially important for interactive agents that need conversation history.Documentation Index
Fetch the complete documentation index at: https://docs.charmos.io/llms.txt
Use this file to discover all available pages before exploring further.
What Threads Provide
- Multi-turn context.
- Message history.
- Run grouping.
- Follow-up questions.
- User-visible conversation state.
Thread IDs
The Store passes a thread ID when a run belongs to an existing conversation. Agents can use this ID to associate output with a specific user session.State Snapshots
Some runtimes may receive state snapshots or history payloads. Agents should treat these as user/session context, not as global memory.Workspace Isolation
- Serverless and interactive runs should treat each run/thread as isolated.
- Daemon agents may share a longer-lived workspace depending on implementation.
Use Cases
- Chat assistants.
- Iterative research.
- Follow-up edits.
- Support conversations.