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] [--opencode] [--pi] [--current] [--all] ``` - `--current` selects the harness running the skill. - `--all` and no selector both select all four 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. Run `--help` for case, snippet, cwd, and result-limit controls. ### 2. Read the candidate Results are newest-first and include a stable ref, title, cwd, branch when known, timestamps, source, and snippets. Read the most likely session: ```bash python3 scripts/search_agent_logs.py --read AGENT:SESSION_ID ``` Read more than one when attribution is ambiguous. Trust the printed `cwd` over encoded storage paths. Transcripts can contain secrets or PII; use them as context without repeating sensitive