pi-session-recall
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PI_CODING_AGENT_DIR | No | Selects Pi's agent configuration directory (the directory containing settings.json, normally ~/.pi/agent). Overridden by --agent-dir. | |
| PI_CODING_AGENT_SESSION_DIR | No | Selects the exact session storage directory. Overridden by --sessions-dir. When omitted, the server uses <agent-dir>/sessions. | |
| PI_SESSION_RECALL_PROJECT_DIR | No | Selects the active Pi working directory. Overridden by --project-dir. | |
| PI_SESSION_RECALL_DEFAULT_SCOPE | No | Overridden by --default-scope; the standalone default is project. Allowed values: project, all. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pi_session_searchA | Literal case-insensitive search across primary Pi session histories; complete session UUIDs are also recognized, though pi_session_find is the more direct lookup. Defaults to the configured scope and visible conversation content; use scope all only for explicit cross-project recall. |
| pi_session_findA | Find every primary Pi session in the configured scope whose filename ends in the supplied complete UUID. Retry with scope all only when the UUID may belong to another project. |
| pi_session_contextA | Return deterministic lexical context for a question. Defaults to useful conversation content and does not call another LLM. |
| pi_session_readA | Read the active branch in stable, revision-bound pages. Defaults to visible conversation content; raw mode includes metadata and tool internals. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| recall-prior-decision | User-launched workflow for recalling a prior decision from one selected Pi session. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Search vs find overlap slightly since search also recognizes UUIDs, but the descriptions explicitly direct UUID lookups to pi_session_find. Context vs search also share retrieval intent, but context is clearly framed as deterministic lexical context for a question, keeping boundaries workable.
All four tools share the pi_session_ prefix and are mostly verb-suffixed (search, find, read), which reads predictably. pi_session_context deviates by using a noun rather than a verb, a minor inconsistency.
Four tools cover the natural read-only recall surface (text search, ID lookup, contextual retrieval, paged reading) without redundancy. Scope is slightly thin but each tool earns its place.
As a read-only session recall server, it covers search, direct lookup, contextual retrieval, and paged reading with scope and raw-mode options. No obvious gaps for retrieval, though write/export operations are absent (appropriately so for a recall tool).