continue codex work

Other Community

Skill notes

Overview

Recover actionable context from a prior Codex CLI session and continue execution in the current conversation. Codex records each session as a rollout JSONL under ~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl (with an optional state_*.sqlite index).

File Structure Reference

For the rollout directory layout, the record/payload schema, and the compaction format, see references/file_structure.md.

Step 1: Extract Context (single script call)

Run the bundled extractor. It handles session discovery (via the shared _core), rollout parsing, noise filtering, and workspace state in one call: Expected output: a structured Markdown briefing. What you should see: A # Codex Resume Context Briefing header, then ## Session Info (id, project cwd, last-active time, title, Codex version). A one-line Session end reason — the single most important routing signal (see Step 2).

Step 2: Branch by Session End Reason

The briefing's Session end reason tells you how the prior run stopped. Route on it: End reason · What it means · Strategy Clean exit · The agent had the last word (a completed turn). · Read the last user request that was addressed; continue from any pending work. In progress · Tools ran but the agent left no closing message — cut off mid-task. · This is the common resume case. Read the recent tool calls + files edited, verify what landed, and finish the turn the agent was in.

Step 3: Reconcile and Continue

Before making changes: Confirm the current directory matches the session's cwd. If the git branch differs from what the briefing shows, note it and decide whether to switch. Inspect the files listed under Files Edited — verify the prior run's changes actually landed (a rollout records that a patch was attempted; confirm the current file state). Do not assume old claims hold without checking — compaction and tool output are lossy.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@daymade · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Extract Context (single script call)

Run the bundled extractor. It handles session discovery (via the shared `_core`), rollout parsing, noise filtering, and workspace state in one call: Expected output: a structured Markdown briefing. What you should see: A `# Codex Resume Context Briefing` header, then `## Session Info` (id, project cwd, last-active time, title, Codex version). A one-line `Session end reason` — the single most important routing signal (see Step 2).

02
Step 2: Branch by Session End Reason

The briefing's Session end reason tells you how the prior run stopped. Route on it: End reason · What it means · Strategy Clean exit · The agent had the last word (a completed turn). · Read the last user request that was addressed; continue from any pending work. In progress · Tools ran but the agent left no closing message — cut off mid-task. · This is the common resume case. Read the recent tool calls + files edited, verify what landed, and finish the turn the agent was in.

03
Step 3: Reconcile and Continue

Before making changes: Confirm the current directory matches the session's `cwd`. If the git branch differs from what the briefing shows, note it and decide whether to switch. Inspect the files listed under Files Edited — verify the prior run's changes actually landed (a rollout records that a patch was *attempted*; confirm the current file state). Do not assume old claims hold without checking — compaction and tool output are lossy.

04
Step 4: Report

Respond concisely: Context recovered: which session, key findings from the briefing. Work executed: files changed, commands run, test results. Remaining: pending tasks, if any.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.