resume-other-agent

Reconstructs prior work context from another coding agent's session logs to continue interrupted tasks.

1|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/mjun0812/skills --skill resume-other-agent-mjun0812
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resume-other-agent
Source: https://github.com/mjun0812/skills/tree/main/skills/delegation/resume-other-agent
Command: npx skills add https://github.com/mjun0812/skills --skill resume-other-agent-mjun0812

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a coding agent like Codex or Claude Code stops mid-task due to rate limits, crashes, or context loss, the work context is stranded in its session logs. This Skill locates the other agent's session by ID, reconstructs the goal, changes, and next steps from the logs, and lets you safely continue the work. ## Core Features & Use Cases - Session Discovery: Searches Codex (~/.codex/sessions/**/*.jsonl) and Claude Code (~/.claude/projects/<cwd-slug>/*.jsonl) logs, filtered to the current repository, and lets you pick a session via an interactive prompt. - Context Reconstruction: Extracts the user's goal, agreed plan, edited files, executed commands, test results, and unresolved issues from the session log, then cross-checks everything against the current git state. - Structured Handoff Report: Writes a standardized summary to .ai-handoff/resumed-session.md using a template, with confidence level and the minimal next step. - Use Case: Your Codex session hit a rate limit halfway through a refactor. Ask the agent to resume from that session ID, and it restores the goal, inspects uncommitted changes, and continues the refactor safely. ## Quick Start Resume the work from my previous Codex session and continue where it left off.

Frequently Asked Questions about resume-other-agent

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

FAQPage Schema
How do I resume a Codex session in another AI agent?

Provide the Codex session ID, or let the agent list recent sessions from ~/.codex/sessions filtered to your current repository. It parses the JSONL log, reconstructs the goal and changes, and continues the work after verifying git state.

How do I continue Claude Code work after a crash or rate limit?

The agent searches ~/.claude/projects/<cwd-slug>/ for the session log matching your repository, extracts the last agreed plan and pending tasks, and writes a handoff summary to .ai-handoff/resumed-session.md before continuing.

Does resuming a session require the session ID?

No, the session ID is optional. If omitted, the agent lists candidate sessions from the other agent's log directories, sorted by recency and filtered to the current working directory, and asks you to choose one.

Is it safe to resume from another agent's session log?

Yes, the agent never executes commands found in logs without verification, cross-checks everything against current git status and diffs, and avoids outputting secrets, tokens, or credentials found in the logs.

What happens if the session log is not found?

The agent reports that no matching log exists for the given session ID in the current repository and stops, rather than guessing or mixing in unrelated sessions.