runtime-session-search
/runtime-session-search
Find a past agent session by words or id in Claude, Codex, or Hermes (every profile), read its final reply, and return the native session id so orchestrate can resume it. Use when the person asks what happened before, what was tried before, how a problem was worked across sessions, where a session went, what an agent last said, or wants to pick up old work. Reads the runtimes' own session files directly, read-only; needs no hosted pane.
- Author
- foxrun-ai ↗
- Repository
- foxrun ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 12
- Scripts
- 4
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 4 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: lib/session_stores.py, tests/__init__.py, tests/support.py, tests/test_search.py
What it does and when to use it
Find a past agent session by words or id in Claude, Codex, or Hermes (every profile), read its final reply, and return the native session id so orchestrate can resume it. Use when the person asks what happened before, what was tried before, how a problem was worked across sessions, where a session went, what an agent last said, or wants to pick up old work. Reads the runtimes' own session files directly, read-only; needs no hosted pane.
Original author description
Find a past agent session by words or id in Claude, Codex, or Hermes (every profile), read its final reply, and return the native session id so orchestrate can resume it. Use when the person asks what happened before, what was tried before, how a problem was worked across sessions, where a session went, what an agent last said, or wants to pick up old work. Reads the runtimes' own session files directly, read-only; needs no hosted pane.
How it works
- Steps
- Laws
- Gotchas
SKILL.md preview
---
name: runtime-session-search
description: "Find a past agent session by words or id in Claude, Codex, or Hermes (every profile), read its final reply, and return the native session id so orchestrate can resume it. Use when the person asks what happened before, what was tried before, how a problem was worked across sessions, where a session went, what an agent last said, or wants to pick up old work. Reads the runtimes' own session files directly, read-only; needs no hosted pane."
kind: tool
---
# runtime-session-search
`bin/runtime-session-search` reads the session files each runtime keeps under the home folder and prints JSON.
Summarize the JSON for the person; never paste it raw.
It needs no other skill. The store readers ship beside it in `lib/session_stores.py`.
| Verb | What it does |
|---|---|
| `find "<words or id>" [--runtime claude\|codex\|hermes] [--since 90d\|all] [--limit 15]` | Hits across Claude JSONL, Codex rollouts, and Hermes `state.db` (main and every profile). Ids rank above words. Each hit carries `session_id`, `store`, `profile`, `when`, `cwd`, `attach_or_resume_cmd`, `read_with`, `orchestrate_with`. |
| `read <exact-native-id> [--runtime …] [--profile …]` | The last user message and the final assistant reply, 8 KB or 120 lines at most. Reasoning and tool payloads stay out. `resume_with` is included. |
| `check-memex` | Whether memex passes the exact capability check and its index is fresh. |
## Steps
1. Run `find` with the person's words, or with the id they gave. Done when the status is `found`, `not_found`, or `choice_required`.
2. On `choice_required`, show the choices and ask for the runtime or the exact id. Done when one id is left.
3. Run `read <id>` with `--runtime` (and `--profile` for Hermes) from the hit. Done when the status is `read` or `no_reply`.
4. Tell the person what the session last said, and give the `resume_with` command or hand the id to `orchestrate`. Done when they have the id and the next command.
Question mode: when the person asks a question about past work ("what did we try for the login bug?") rather than for one session:
5. Turn the question into two or three short word searches, and run `find` for each, with `--since all` if the work may be older than 90 days. Done when you hold the hits from every search.
6. Run `read` on the three to five best hits, newest first. Done when each read is `read` or `no_reply`.
7. Answer the question in a few lines. Name the session id and date behind each claim, and say what you did not find. Done when every claim cites a session id.
## Laws
- Native files are truth: `~/.claude/projects`, `~/.codex/sessions`, `~/.hermes/state.db`, and `~/.hermes/profiles/*/state.db`, read-only. `--stores-root` (or `RUNTIME_SESSION_SEARCH_STORES`) points at another home folder.
- memex is a speed layer only when `check-memex` passes and its index is not older than the newest transcript by a day. Otherwise the built-in readers run. memex is optional; the skill works without it.
- Missing or ambiguous matches stay explicit: `not_found`, `choice_required` (several ids match a prefix, or several stores hold the id), `no_reply`. Never guess; ask for the exact id or runtime.
- Saved text never proves task success (`task_success: not_inferred`).
- Search is separate from cleanup: this skill never closes, resumes, or spawns. Hand the id to `orchestrate` (`--session-id`) for more work, or to `herdr resume <id>` when the herdr skill is on the shelf.
## Gotchas
- A runtime that is not installed has no folder. Its store is skipped and `adapter_notes` says so; that is not an error.
- `--since` defaults to 90 days for word searches. Use `--since all` for older work. An id search ignores the window.
- A Codex thread that the Codex app owns resumes with `codex exec fork`, not `codex exec resume`.
Files in this package (12)
- SKILL.md 4 KB
- bin/runtime-session-search 15 KB
- lib/session_stores.py 35 KB
- replays/question-cites-ids.json 1 KB
- replays/read-ambiguous-id.json 1 KB
- replays/read-find-then-read.json 1 KB
- tests/__init__.py 1 KB
- tests/support.py 1 KB
- tests/test_search.py 14 KB
- tests/fixtures/claude_session.jsonl 1 KB
- tests/fixtures/codex_rollout.jsonl 1 KB
- tests/fixtures/hermes_state.sql 1 KB
Versions
The database has no other skills named runtime-session-search.
Database snapshot: 13.11.2026 · package version a5ef4748499e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100agent-sessions
Search, list, and resume AI agent sessions across Claude Code, Codex CLI, Gemini CLI, opencode, Hermes Agent, and Cline CLI. Use when the user asks to find a past conversation, search session history, resume a previous session, list recent agent activity, or check what was… - 100tma1-search
Search past agent sessions on this project by keyword, and read back any session's conversation. Invoke this skill when the answer lives in an earlier session — how something was fixed before, what was decided, what another agent tried last week — or when the user hands you a… - 100resume-codex-session
Use when the user asks Claude to continue, resume, or take over work from a Codex session by session name or session id (UUID or UUID prefix). Examples include "continue the codex session called feature-x" or "/resume-codex-session 019dc08e". Do not use for ordinary Claude… - 100resume-claude-session
Use when the user asks Codex to continue, resume, or take over work from a Claude Code session by session name or session id (UUID or UUID prefix). Examples include "continue the claude session called feature-x" or "/resume-claude-session a3b5c9f2". Do not use for ordinary Codex… - 100sessions
Search and ask questions about coding agent session history across Claude Code, Codex, and Cursor. Use when asking what was worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also… - 100tma1-search
Search past agent sessions on this project by keyword, and read back any session's conversation. Invoke this skill when the answer lives in an earlier session — how something was fixed before, what was decided, what another agent tried last week — or when the user hands you a…