historylisted

# Session history ## Invocation `/history [selector] <query>` searches your conversation history and reports the matching records. - `/history <query>` searches every session in the current project. This is the default and the common case: "we discussed X, what did we decide?" - `/history <selector> <query>` searches one specific session. The `<selector>` is its name (set with /rename), its UUID, or a unique UUID prefix. The session may live in another project. To tell a selector from query text, resolve the leading token with `find`. If it resolves to a session, that token is the selector and the rest is the query. If not, the whole input is the query against the current project. The only ambiguous case is a query whose first word is an exact session name, and resolution is exact, so it is rare. This dispatch is for interpreting a user's typed `/history` line. When the model invokes this skill on its own to investigate history, it calls `history.py` directly with explicit flags (for example `--tool Bash --query …` or `--type system --subtype api_error`) rather than going through the dispatch. ## The driver Everything goes through one script. The current session UUID is available as `${CLAUDE_SESSION_ID}`. Pass it as `--session-id` so the driver can locate the current session and project. ``` python ${CLAUDE_SKILL_DIR}/scripts/history.py search [--query Q] [target] [filters] [output] python ${CLAUDE_SKILL_DIR}/scripts/history.py fetch --index N [N ...] [target] p