Skip to main content
The Session Context Store captures the current state of a conversation: what’s been discussed, what the goal is, and what progress has been made. Unlike other stores that accumulate data, session context is a snapshot that gets replaced on each update.

Basic Usage

The agent knows the ongoing context about REST API design.

Summary Mode

Default behavior. Captures the essence of the conversation without detailed planning.
What gets captured: what’s being worked on, key decisions made, current state, open questions.

Planning Mode

Enable planning to track goals, plan steps, and progress.

Data Model

Accessing Session Context

Context Injection

Session context is injected into the system prompt:

When to Use

Session context is essential when:
  • Message history gets truncated: long conversations lose early context
  • Sessions are resumed: user returns after a break
  • Complex multi-step tasks: track progress through long workflows
  • Handoffs: another agent or human needs to understand the state

Combining with Other Stores

Session context works well alongside user-level stores:
Long-term user knowledge plus short-term session state.