coding-agent-sessions
MUST USE when asked to find, read, list, search, inspect, fetch, export, or reconstruct coding-agent sessions across Codex, Claude Code/Desktop, OpenCode, Senpi/pi, oh-my-pi (omp), gajae-code (gjc), OpenClaw, Factory Droid, Amp, Gemini/Kimi/Qwen CLIs, Codebuff, Roo/Kilo/Cline, Kodu, Cursor CLI, Aider, Aside browser-agent sessions, or unknown local agent logs. Covers transcripts, session IDs, rollout JSONL, state SQLite, Claude projects/pre-compact histories, OpenCode messages/parts, child/subagent linkage, cwd/model/time/token filters, archives, and cost clues. Expands fuzzy recall into parall
npx skills add code-yeongyu/oh-my-openagent --skill coding-agent-sessions --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Coding Agent Sessions Find local coding-agent sessions across agent products before answering from memory. Prefer the bundled finder for broad cross-platform search, then read the selected session or raw file when you need exact evidence. ## PHASE 0 - PLATFORM ROUTER 1. **IF the user names a platform, load its reference first.** | Platform | Read | |---|---| | Codex / OpenAI Codex CLI | `references/codex.md` | | Claude Code / Claude Desktop histories | `references/claude.md` | | Senpi / pi coding-agent logs | `references/senpi.md` | | oh-my-pi (`omp`, `~/.omp`) and gajae-code (`gjc`, `~/.gjc`) logs | `references/senpi.md` | | OpenCode / oh-my-openagent (formerly oh-my-opencode) storage | `references/opencode.md` | | OpenClaw, Droid, Amp, Gemini, Kimi, Qwen, Codebuff, Roo/Kilo/Cline, Kodu, Cursor CLI, Aider, Kiro, Goose, Hermes, Crush, Zed, Aside | `references/all-platforms.md` | | Unknown / "any session" / cross-agent search | `references/all-platforms.md` | 2. **Run the broad finder first unless the user gave an exact file path. For fuzzy recall, expand the query first.** When the user remembers a task vaguely ("that OpenCode bug", "the dashboard PR", "when did we fix X"), deriv
- PHASE 0 - PLATFORM ROUTER
- Output Contract
- Filters
- Subagent / Child Sessions
- Codex Notes
- Troubleshooting
- Activation
python3 scripts/find-agent-sessions.py list --limit 20 python3 scripts/find-agent-sessions.py find "commit" --from 7d --platform senpi --platform opencode python3 scripts/find-agent-sessions.py find "proxy" --platform openclaw --platform droid --platform amp python3 scripts/find-agent-sessions.py find "refactor" --platform oh-my-pi --platform gajae-code python3 scripts/find-agent-sessions.py find --query "deploy" --query "token usage" --workers 64 python3 scripts/find-agent-sessions.py find --query "opencode bug" --query "fix opencode" --query "OpenCode parent session" --include-subagents --workers 64 python3 scripts/find-agent-sessions.py read <session-id> python3 scripts/find-agent-sessions.py list --platform codex --from 7d python3 scripts/find-agent-sessions.py find "deploy" --platform codex python3 scripts/find-agent-sessions.py read <session-id> --platform codex
What does the coding-agent-sessions skill do?
MUST USE when asked to find, read, list, search, inspect, fetch, export, or reconstruct coding-agent sessions across Codex, Claude Code/Desktop, OpenCode, Senpi/pi, oh-my-pi (omp), gajae-code (gjc), OpenClaw, Factory Droid, Amp, Gemini/Kimi/Qwen CLIs, Codebuff, Roo/Kilo/Cline, Kodu, Cursor CLI, Aider, Aside browser-agent sessions, or unknown local agent logs. Covers transcripts, session IDs, rollout JSONL, state SQLite, Claude projects/pre-compact histories, OpenCode messages/parts, child/subagent linkage, cwd/model/time/token filters, archives, and cost clues. Expands fuzzy recall into parall
How do I install it?
Run `npx skills add code-yeongyu/oh-my-openagent --skill coding-agent-sessions --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From code-yeongyu/oh-my-openagent, a repository with 67,209 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.