coding-agent-sessions

Search and inspect local coding-agent session transcripts across multiple agent platforms.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/hugefiver/ocmm --skill coding-agent-sessions-hugefiver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-agent-sessions
Source: https://github.com/hugefiver/ocmm/tree/main/plugins/deepwork/skills/coding-agent-sessions
Command: npx skills add https://github.com/hugefiver/ocmm --skill coding-agent-sessions-hugefiver

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? When you need to recall what you worked on, find a past fix, or audit delegated work, session history is scattered across many coding-agent products with incompatible storage formats. This Skill locates, searches, and reads those sessions from one place instead of digging through each tool's private logs. ## Core Features & Use Cases - Cross-platform session search: Scans Codex, Claude Code/Desktop, OpenCode, Senpi/pi, oh-my-pi, gajae-code, OpenClaw, Factory Droid, Amp, Gemini/Kimi/Qwen CLIs, Codebuff, Roo/Kilo/Cline, Kodu, Cursor CLI, Aider, Kiro, and Aside from a single finder script with parallel workers. - Fuzzy recall expansion: Turns vague memories ("that OpenCode bug", "did we already migrate X") into multiple query lanes with match reasons, then filters by platform, cwd, model, and date range. - Subagent tree reconstruction: Links child sessions to parents via Claude subagent directories, Codex thread_spawn_edges, and OpenCode parent_id, so delegated work hidden in child transcripts is discoverable with --include-subagents. - Use Case: Ask "what did I work on a few days ago" and get JSON results with session IDs, first/last user prompts, token usage, and a ready-to-run read command for the full transcript. ## Quick Start Ask the agent to find the coding session where you fixed a specific bug last week, and it will run the finder across all platforms and read the matching transcript.

Frequently Asked Questions about coding-agent-sessions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search coding agent session history across multiple tools?▼

Run the bundled finder with a query, for example python3 scripts/find-agent-sessions.py find "deploy" --from 7d. It scans all registered platforms in parallel and returns JSON results with session IDs, prompt previews, and match reasons.

How do I find what I worked on in a past Claude Code or Codex session?▼

Use fuzzy recall expansion: derive several short query lanes from product names, repos, or error text, then pass them as repeated --query flags. Narrow hits with --platform, --cwd, --model, and date filters like --from 7d.

Which coding agents does the session finder support?▼

It supports Codex, Claude Code/Desktop, OpenCode, Senpi/pi, oh-my-pi, gajae-code, OpenClaw, Factory Droid, Amp, Gemini, Kimi, Qwen, Codebuff, Roo Code, Kilo Code, Cline, Kodu, Cursor CLI, Aider, Kiro, and Aside browser-agent sessions.

Can I search subagent or delegated child sessions?▼

Yes, pass --include-subagents to list and search commands, since child sessions are hidden by default. Reading a main session returns a subagents array with each child's id, agent label, and raw transcript path.

Why are some platform sessions missing from search results?▼

The store may live in a nonstandard location, such as a custom CODEX_HOME, PI_CONFIG_DIR, or an alternate OpenCode data directory. Pass that directory with --root so the scanner includes it alongside the default roots.

Does the finder require external Python packages?▼

No, the scripts use only the Python 3.11 standard library, including sqlite3 and concurrent.futures. OpenCode lookups optionally call the opencode CLI when it is installed, falling back to file scans otherwise.