| name | pi-session-query |
| description | Query previous pi sessions to retrieve context, decisions, code changes, or other information. Use when you need to look up what happened in a parent session or any other session file. |
| disable-model-invocation | true |
Pi Session Query
Query pi session files to retrieve context from past conversations.
This skill is automatically invoked in handed-off sessions when you need to look up details from the parent session.
When to Use
- When the handoff summary references a "Parent session" or "Ancestor sessions" path
- When you need specific details not included in the handoff summary
- When you need to verify a decision or approach from the parent or an ancestor session
- When you need file paths or code snippets from earlier work
Usage
Use the session_query tool:
session_query(sessionPath, question)
Parameters:
sessionPath: Full path to the session file (provided in the "Parent session:" line)question: Specific question about that session
Examples
session_query("/path/to/session.jsonl", "What files were modified?")
session_query("/path/to/session.jsonl", "What approach was chosen for authentication?")
session_query("/path/to/session.jsonl", "What error handling pattern was used?")
session_query("/path/to/session.jsonl", "Summarize the key decisions made")
Best Practices
- Be specific - Ask targeted questions for better results
- Reference code - Ask about specific files or functions when relevant
- Verify before assuming - If the handoff summary seems incomplete, query for details
- Don't over-query - The handoff summary should have most context; query only when needed
- Check ancestors - If the parent session doesn't have the info, try ancestor sessions listed in the handoff
How It Works
The tool loads the referenced session file, extracts the conversation history, and uses the LLM to answer your question based on its contents. This allows context retrieval without loading the full parent session into your context window.
