The @session tool lets the agent recall earlier saved conversations — “what did we decide about the cache last week?”. Implemented natively over the existing SessionManager. Inspired by hermes-agent’s session_search.
Subcommands
<tool_call name="@session" args='{"cmd":"search","args":{"query":"rate limiter design"}}' />
<tool_call name="@session" args='{"cmd":"list"}' />
| Subcommand | Purpose |
|---|
search {query, limit?} | free-text search across saved sessions; returns matching sessions + snippets (limit = snippets per session, default 3) |
list | list saved session names |
Output
Sessions matching "rate limiter":
• proj-acme (2 matches)
… used a token bucket for the rate limiter
… capped it at 1000 rps per key
Notes
- It is read-only and concurrency-safe.
- Searches both the chat and agent history of saved sessions.
- Pair with Session Management (
/session save) to build a searchable history.
Use alongside @memory (facts) and @skill (procedures): @session is episodic memory (“what we talked about”), while memory and skills are distilled knowledge.
