check-agent-logslisted

<!-- Generated from https://github.com/nielsmadan/agentic-coding — edits here are overwritten. --> # Check Agent Logs Recover prior context by searching stored agent transcripts, reading the relevant session, and continuing from its diagnosis or decision. ## Instructions ### 1. Choose a query and agents Use a distinctive regex such as an error string, symbol, ticket ID, or unusual phrase. With no agent selector, the script searches all agents. Selectors compose: ```bash python3 scripts/search_agent_logs.py "QUERY" [--claude] [--codex] [--droid] [--opencode] [--pi] [--current] [--all] ``` - `--current` selects the harness running the skill. - `--all` and no selector both select all five agents. - `--scope siblings` is the default project scope. `--scope current` searches only the current checkout; `--scope all` searches every recorded project. - `--app NAME` searches session cwd values containing `NAME` and overrides scope. - `--days N` limits the search to recently updated sessions. - **`--kind message` is the highest-value filter.** Every entry is classified as `message` (what was said), `tool` (calls and their output), or `meta` (reasoning and summaries). Tool traffic dominates raw match counts — a real session here matched 5117 times, of which 4668 were tool output — so search conversation first and widen to `--kind tool` only when hunting a command or a stack trace. - Results are ranked by weighted score (`message` 3, `meta` 2, `tool` 1, title 5), hig