phase-10i-transcript-search-research — Claude Code prompt guide
phase-10i-transcript-search-research guides an architectural study for historical chat transcript search in Phantom after Murph compaction. Useful when planning agent context retrieval.
Apache-2.0 ★ 1,497 updated 2026-06-16
.claude/commands/phase-10i-transcript-search-research.mdWhat phase-10i-transcript-search-research does
This prompt instructs Claude Code to act simultaneously as a principal engineer, architect, and product manager. The assistant inspects 15 repository files, covering message-store.ts, event-log.ts, continuity-context.ts, database schemas, and unit tests. Its explicit goal is delivering an in-depth design memo rather than modifying application code.
The output writes directly to phase-10i-transcript-search-research.md. The prompt tackles eight core questions, including whether SQLite suffices over Qdrant memory, how to redact credentials or raw payloads, and how to verify retrieval tests.
Because the instructions reference absolute local paths under /Users/truffle/work/phantom-murph-hardening, the prompt fails on different directory structures unless those paths are adjusted first.
What it helps with
- design historical transcript retrieval after context window compaction
- evaluate SQLite queries against Qdrant vector memory for initial rollout
- define redaction rules for secrets and authentication tokens in agent tools
- build a test strategy to verify recovery of older conversation details
Example prompts for the agent
- Run the transcript search research prompt against the Phantom chat codebase
- Analyze context compaction files and produce the phase-10i research report
- Draft the transcript lookup tool contract without touching application code
How to install phase-10i-transcript-search-research
Manually: put the files in place
.claude/commands/phase-10i-transcript-search-research.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about phase-10i-transcript-search-research
How to install phase-10i-transcript-search-research in Claude Code?
Add the prompt contents to .claude/commands/phase-10i-transcript-search-research.md in your project.
What does phase-10i-transcript-search-research do?
It guides an in-depth architectural analysis of chat persistence to design transcript search tools for compacted agent sessions.
Does this prompt modify any source code?
No, it contains an explicit instruction forbidding code edits and restricts deliverables to a specific markdown research report.
Source text
phase-10i-transcript-search-research.md · Apache-2.0
ultrathink. ultrathink. ultrathink. You are a principal engineer, principal architect, and principal product manager at Anthropic, all three at once. You are researching historical transcript search for Phantom chat after Murph compaction. No context anxiety. No token limits. No time pressure. No cost anxiety. No "v2" thinking. There is no v2. Build it right. Take as long as you need. ## Mission Design the smallest production-ready mechanism that lets the agent access historical chat transcript details that may have been compacted out of the provider context. Write your report to: `/Users/truffle/work/phantom-murph-hardening/research/chat-experience/phase-10i-transcript-search-research.md` Do not edit application code. ## Required Reading Read these files directly: 1. `/Users/truffle/.claude/AGENTS.md` 2. `/Users/truffle/.claude/CLAUDE.md` 3. `/Users/truffle/work/phantom-murph-hardening/CLAUDE.md` 4. `/Users/truffle/work/phantom-murph-hardening/research/chat-experience/phase-10g-pi-continuity.md` 5. `/Users/truffle/work/phantom-murph-hardening/research/chat-experience/phase-10h-phantom-chat-review.md` 6. `/Users/truffle/work/phantom-murph-hardening/src/chat/message-store.ts` 7. `/Users/truffle/work/phantom-murph-hardening/src/chat/event-log.ts` 8. `/Users/truffle/work/phantom-murph-hardening/src/chat/continuity-context.ts` 9. `/Users/truffle/work/phantom-murph-hardening/src/chat/run-timeline.ts` 10. `/Users/truffle/work/phantom-murph-hardening/src/chat/http.ts` 11. `/Users/truffle/work/phantom-murph-hardening/src/chat/http-handlers.ts` 12. `/Users/truffle/work/phantom-murph-hardening/src/db/schema.ts` 13. `/Users/truffle/work/phantom-murph-hardening/src/agent/in-process-reflective-tools.ts` 14. `/Users/truffle/work/murph/packages/core/src/substrate/pi-harness.ts` 15. `/Users/truffle/work/murph/packages/core/src/query/query.ts` Also inspect tests under `src/chat/__tests__` and `src/agent/__tests__`. ## Questions To Answer 1. What durable data has enough fidelity to reconstruct pre-compaction history? 2. Is SQLite search enough for the first slice, or should we use Qdrant memory? 3. Should transcript lookup be an agent tool, an injected continuity summary, a user-visible API, or all three? 4. How should the tool avoid exposing secrets, login links, raw attachment payloads, and large outputs? 5. What query/filter shape is enough: current session only, all sessions, date windows, roles, sequence ranges, artifact-only? 6. How should the agent know the tool exists and when to use it? 7. How do we test that post-compaction follow-up can recover a detail from earlier transcript? 8. What is the smallest implementation slice that is valuable and low-risk? ## Design Constraints - Compaction should touch provider context only. It must not close tools, MCP clients, or transcript search capability. - The search mechanism must work after reload and process restart. - Search results should be compact, cited by session id and seq, and safe to paste into the model context. - Do not create a full vector-search system if SQLite plus existing memory is enough for this slice. - Do not force the user to manually search if the agent can use a tool. ## Deliverable Format Write: 1. Executive recommendation. 2. Current persistence model. 3. Proposed transcript search contract. 4. Safety/redaction model. 5. Test plan. 6. Builder slice proposal with exact files likely touched. ultrathink. This is a product trust feature. Get the boundary right.
© ghostwright · Apache-2.0 · ghostwright/phantom