# `/recall` slash command (mempalace summary recall)

**Captured:** 2026-05-06 (auto-extracted from harness build of BUILD_SPEC v3 — embedded-claude-terminal)

## Why deferred

Auto-injection of mempalace summary at session start was rejected per Gemini round-1 review (CLI cleanliness — bloats `claude --resume <id>` startup with synthetic context the user didn't ask for, makes the first turn's behavior depend on what the model autoloaded vs what the user typed).

A `/recall` slash command instead would let JT pull mempalace context on demand. Phase 10's `chat_project` tag (project↔session_id binding) is the substrate this command would query.

## Prior decisions
- BUILD_SPEC v3 §"Future work" item 3
- Phase 10 spec note: "Do NOT auto-inject summary at session start (that's a future-work `/recall` slash command, NOT this phase)"

## Status
- [ ] Defer until JT identifies a concrete recall workflow he wants to support. The substrate (chat_project tag) is now in place if/when this lands.