coding-agent-sessions
Helps your agent find and understand previous coding sessions. Useful for recovering information or work done in earlier code agent runs.
What it does
This tool helps you find and review past conversations you've had with AI assistants that write code. It can search across different platforms where these conversations are saved.
When to use it
- ✓When you want to recall what you did on a previous project.
- ✓When you need to find a code snippet or explanation an AI assistant provided.
- ✓When you want to see the history of how a coding problem was solved.
Example of what to ask your AI
“Search my conversations about fixing the login bug in project X.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool looks through log files where conversations with AI assistants are stored. It can filter by platform (like Codex or Claude) and by dates to find the right conversation.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add code-yeongyu/oh-my-openagent --skill coding-agent-sessionsOr download just the file:
curl -L https://raw.githubusercontent.com/code-yeongyu/oh-my-openagent/dev/packages/shared-skills/skills/coding-agent-sessions/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
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
IF the user names a platform, load its reference first.
Platform Read Codex / OpenAI Codex CLI references/codex.mdClaude Code / Claude Desktop histories references/claude.mdOMO / Senpi / pi coding-agent logs references/senpi.mdoh-my-pi ( omp,~/.omp) and gajae-code (gjc,~/.gjc) logsreferences/senpi.mdOpenCode / oh-my-openagent (formerly oh-my-opencode) storage references/opencode.mdOpenClaw, Droid, Amp, Gemini, Kimi, Qwen, Codebuff, Roo/Kilo/Cline, Kodu, Cursor CLI, Aider, Kiro, Goose, Hermes, Crush, Zed, Aside references/all-platforms.mdUnknown / "any session" / cross-agent search references/all-platforms.mdRun 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"), derive 3-6 short query lanes before searching: product/tool aliases, repo/package names, exact error text, issue/PR/session IDs, English/Korean phrasing, and likely verbs such as fix, review, plan, deploy, or merge. Run the lanes together with repeated --query so match_reasons shows which wording found the hit.
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>
Use python instead of python3 on systems where that is the available executable.
- Use explorer-style parallel lanes when one query batch is not enough.
If scope is broad (multi-month, many repos/platforms, or a vague "what happened with X"), split independent searches by names/errors, repos/cwds, platforms/models, and time windows. Use available subagent/delegation tools for these lanes when they exist; otherwise run the finder calls in parallel. Merge candidates by id/path, then read the most likely sessions.
Read details from search results before ad hoc digging. Search results include
detail_hint; run thatread <session-id> --platform <platform>command to see the first user prompt, last user prompt, events, and child sessions together.Verify by opening raw transcripts for claims. The finder normalizes formats; the raw
pathremains the source of truth.
Output Contract
The finder prints JSON for stdout and jq. Every result includes:
| Field | Meaning |
|---|---|
platform |
Registered platform key such as codex, claude, senpi, oh-my-pi, gajae-code, opencode, openclaw, droid, amp, kodu, cursor-cli, aider, roo-code, kilo-code, kilo-cli, kiro, or aside |
id |
Session ID or stable file-derived ID |
path |
Raw transcript/index file |
cwd |
Working directory when recoverable |
created_at, updated_at |
ISO-like timestamps when recoverable |
provider, model |
Model metadata when recoverable |
first_user_message |
First user prompt preview (for subagents: task description + delegated prompt) |
last_user_message |
Last user prompt preview when recoverable |
usage |
Token/cost clues when present in the platform log |
parent_id |
Parent session/thread ID when this is a subagent or child session, else null |
agent |
Subagent label (Claude agentType, Codex nickname (role), OpenCode agent name) |
subagent_count |
Number of child sessions spawned by this session |
detail_hint |
Ready-to-run read command for detailed inspection |
match_reasons |
Search-only array explaining which field/content matched each query |
…
FAQ
What are 'coding-agent sessions'?
These are the records of your conversations with AI assistants that help write or debug code.
What platforms does it support?
It supports various platforms like Codex, Claude, OpenCode, OMO/Senpi, and others, as well as local logs.
How does it find conversations?
It uses a script that searches specific directories where logs are stored, allowing you to filter by platform name, dates, and even keywords within the conversation.
Details
Original description by the author
Finds, reads, and reconstructs coding-agent sessions across Codex, Claude, OpenCode, OMO/Senpi, and other local agent logs. Use when asked to find or search past sessions, transcripts, or subagent runs, or to recover what an earlier session did.
Popularity
- GitHub stars
- 70k
- Ranking position
- #1735
- License
- NOASSERTION
- Updated
- 10/16/2026
Comments
- …
More skills from this repository
comment-checker
Helps your agent understand and respond to feedback from automatic comment checkers. It's useful when the agent needs to process information from tools that automatically review code or content.
code-yeongyu/oh-my-openagent
lcx-contribute-bug-fix
Helps your agent contribute bug fixes for LazyCodex-related projects. It creates issues or pull requests to ensure code quality.
code-yeongyu/oh-my-openagent
lcx-doctor
Lets your agent check the health of LazyCodex and Codex CLI installations. It's useful when the system behaves oddly after updates or changes.
code-yeongyu/oh-my-openagent
lcx-report-bug
Helps your agent report bugs in detail for LazyCodex projects. It creates issues with useful information for developers to fix the problem.
code-yeongyu/oh-my-openagent
Similar skills
benchmark-optimization-loop
Has your agent improve something's speed in a measured way. It tests multiple versions and chooses the fastest one that still works correctly.
affaan-m/ECC
change-impact
Helps your agent analyze the impact of code changes before making them. It compares the planned vs. actual results afterward, covering paths, data, tests, and documentation. Useful for risky or system-wide changes.
affaan-m/ECC
click-path-audit
Lets your agent trace all user buttons and interactions to find bugs. It finds issues where functions seem to work alone but fail together. Useful when bugs persist even after debugging.
affaan-m/ECC