What is resume-session?

An interactive AI-agent session that keeps conversation history in Markdown files and provides commands for models, saved sessions, branches, skills, exports, and usage metrics.

Use it to run an agent REPL, load skills, continue separate session branches, search history, compact older context, and export conversations.

It gives longer-running work a persistent place to continue, search, branch, compress, or export instead of losing the conversation when the process ends.

resume-session — Command for Claude Code and Codex by mturac

Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/mturac/everything-openai-codex/resume-session/github.svg)](https://agentmods.dev/commands/mturac/everything-openai-codex/resume-session)

Your own site

<a href="https://agentmods.dev/commands/mturac/everything-openai-codex/resume-session"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/resume-session/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/mturac/everything-openai-codex/resume-session"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/resume-session.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,332 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 91% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00026	$0.01332
Opus 5	$0.00013	$0.00666
Sonnet 5	$0.00005	$0.00266
Haiku 4.5	$0.00003	$0.00133

Measured 6d ago against content hash 6eb9207e2bea, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

resume-session scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

91% identical to resume-session — 48 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

commands/resume-session.md · 157 lines

How it starts

The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Resume Session Command

Load the last saved session state and orient fully before doing any work. This command is the counterpart to /save-session.

When to Use

Starting a new session to continue work from a previous day
After starting a fresh session due to context limits
When handing off a session file from another source (just provide the file path)
Any time you have a session file and want Codex to fully absorb it before proceeding

Usage

/resume-session                                                      # loads most recent file in ~/.codex/session-data/
/resume-session 2024-01-15                                           # loads most recent session for that date
/resume-session ~/.codex/session-data/2024-01-15-abc123de-session.tmp  # loads a current short-id session file
/resume-session ~/.codex/sessions/2024-01-15-session.tmp               # loads a specific legacy-format file

Process

Step 1: Find the session file

If no argument provided:

Check ~/.codex/session-data/
Pick the most recently modified *-session.tmp file

If the folder does not exist or has no matching files, tell the user:

No session files found in ~/.codex/session-data/
Run /save-session at the end of a session to create one.

Then stop.

If an argument is provided:

If it looks like a date (YYYY-MM-DD), search ~/.codex/session-data/ first, then the legacy ~/.codex/sessions/, for files matching YYYY-MM-DD-session.tmp (legacy format) or YYYY-MM-DD-<shortid>-session.tmp (current format) and load the most recently modified variant for that date
If it looks like a file path, read that file directly
If not found, report clearly and stop

Step 2: Read the entire session file

Read the complete file. Do not summarize yet.

Step 3: Confirm understanding

Respond with a structured briefing in this exact format:

SESSION LOADED: [actual resolved path to the file]
════════════════════════════════════════════════

PROJECT: [project name / topic from file]

WHAT WE'RE BUILDING:
[2-3 sentence summary in your own words]

CURRENT STATE:
PASS: Working: [count] items confirmed
 In Progress: [list files that are in progress]
 Not Started: [list planned but untouched]

WHAT NOT TO RETRY:
[list every failed approach with its reason — this is critical]

OPEN QUESTIONS / BLOCKERS:
[list any blockers or unanswered questions]

NEXT STEP:
[exact next step if defined in the file]
[if not defined: "No next step defined — recommend reviewing 'What Has NOT Been Tried Yet' together before starting"]

════════════════════════════════════════════════
Ready to continue. What would you like to do?

Read the full file on GitHub · 157 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

6d ago First seen · 157 lines · 26 tokens per session scan A 6eb9207e2bea

Subscribe to this mod's changes

resume-session is a command published in the GitHub repository mturac/everything-openai-codex (89 stars, last pushed 16d ago), licensed MIT. It adds 26 tokens to every session and 1,332 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to resume-session, differing in 48 lines, and is treated as a copy.

Building agents Memory and context agent-harness agent-skills ai-agents automation cli-tools codex

resume-session

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

Resume Session Command

When to Use

Usage

Process

Step 1: Find the session file

Step 2: Read the entire session file

Step 3: Confirm understanding

What this file has done since we first saw it

Other commands, from other repositories

teach

handoff

learn

archive-mail-migrate

context-budget

localize-project