session-searchlisted

# Session Search Use Moraine when the user assumes continuity that is not visible in current context: earlier decisions, unfinished work, old failures, branch history, other agents, or unexplained implementation choices. ## Tool Choice - Use `search_sessions` for content clues: issue numbers, branch names, file paths, function names, commands, errors, model names, tool names, and unusual phrases. - Use `list_sessions` for time clues: today, this morning, last night, the last hour, or currently active sessions. - Use `open` to expand any `session:`, `turn:`, or `event:` ID returned by Moraine. - Use `file_attention` when the clue is a file path or when you need to know which sessions read or changed a file across worktrees. In plugin installs, the MCP tools may appear with names like `mcp__plugin_moraine_moraine__search_sessions`; use the corresponding Moraine tool available in the current harness. ## Query Shape Moraine search is BM25 keyword search, not semantic search. Prefer compact keyword queries over natural-language questions. Good query shapes: ```text issue 398 claude plugin marketplace launch.sh sandbox clickhouse deadline_exceeded agent-smoke-e2e crates/moraine-mcp-core contract file_attention codex/issue-402 command modules ``` Start broad enough to find candidate sessions, then narrow with exact terms. After opening a relevant event or session, search again with `within_id` when more detail is needed from the same conversation. ## Expansion Pattern 1.