Storage

ID	session_storage
Category	Storage
Features	secrets, key_value (unlocks Storage tab)
Dependencies	None

Two storage mechanisms scoped to the current session:

• Key/Value store — plain-text storage for general data
• Secret store — AES-256-GCM encrypted storage for sensitive data

Tools

kv_store

Manage plain-text key/value pairs.

Parameter	Type	Required	Description
operation	enum	yes	set, get, delete, or list
key	string	conditional	Required for set, get, delete
value	string	conditional	Required for set

secret_store

Manage encrypted secrets. Same interface as kv_store but values are encrypted at rest.

Parameter	Type	Required	Description
operation	enum	yes	set, get, delete, or list
name	string	conditional	Required for set, get, delete
value	string	conditional	Required for set

Use Cases

• API key management — store third-party API keys securely during a session
• State persistence — save intermediate results between conversation turns
• Configuration — store user preferences or settings for the session
• Credential handling — securely store tokens needed for multi-step workflows

Example

User: Store my GitHub token so you can use it later

Agent:
  → secret_store({ operation: "set", name: "github_token", value: "ghp_abc123..." })
  ← "Secret 'github_token' stored successfully"

  (later in conversation)
  → secret_store({ operation: "get", name: "github_token" })
  ← { "name": "github_token", "value": "ghp_abc123..." }

Notes

• Data is session-scoped — no cross-session access
• set uses upsert semantics (overwrites existing keys)
• Secret operations require SECRETS_ENCRYPTION_KEY to be configured
• list returns keys/names only (not values) for secrets

See Also

• Session — session metadata
• File System — file-based storage alternative
• Capabilities Overview