← Back to Skills Marketplace
severinzhong

codex-history-manager

by Severin Zhong · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
75
Downloads
1
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install codex-history-manager
Description
Search, read, export, hand off, clone, move, or rebind local Codex history stored under ~/.codex. Use when the user wants to inspect past Codex sessions, bri...
README (SKILL.md)

Codex History Manager

Use codex-history-manager when the task is about local Codex history, not general ChatGPT or web chat history.

Codex stores local history in two places:

  • ~/.codex/state_5.sqlite for thread metadata
  • ~/.codex/sessions/.../rollout-*.jsonl and ~/.codex/archived_sessions/... for event logs

The bundled CLI is the source of truth for reading and mutating that state:

  • ./codex-history-manager ...

Default workflow

  1. For discovery, start with search.
  2. For context, use show-thread or handoff.
  3. For exports, use export-thread.
  4. For cross-workspace reuse, prefer clone-thread over move-thread.
  5. For writes, run a dry run first, then rerun with --apply.
  6. For history body rewrites, always do plan-dangerous-edit, show the warning and change list to the user, get explicit approval in chat, then run apply-dangerous-edit.

Core commands

  • Search threads: ./codex-history-manager search --query "payments"
  • Read one thread: ./codex-history-manager show-thread --id \x3Cthread-id>
  • Export transcript: ./codex-history-manager export-thread --id \x3Cthread-id> --format markdown --output /tmp/thread.md
  • Create a handoff note: ./codex-history-manager handoff --id \x3Cthread-id> --output /tmp/handoff.md
  • Plan a dangerous history content rewrite: ./codex-history-manager plan-dangerous-edit --id \x3Cthread-id> --find "old" --replace "new" --output /tmp/edit-plan.json
  • Clone a thread into another workspace: ./codex-history-manager clone-thread --id \x3Cthread-id> --to-cwd /abs/path --dry-run
  • Move all threads in one workspace: ./codex-history-manager move-workspace --cwd /abs/src --to-cwd /abs/dst --dry-run
  • Clone all threads in one workspace: ./codex-history-manager clone-workspace --cwd /abs/src --to-cwd /abs/dst --dry-run
  • Move a thread to another workspace: ./codex-history-manager move-thread --id \x3Cthread-id> --to-cwd /abs/path --dry-run
  • Rebind provider metadata: ./codex-history-manager change-provider --id \x3Cthread-id> --provider openai1 --dry-run
  • Rebind provider metadata for one workspace: ./codex-history-manager change-provider-workspace --cwd /abs/path --provider openai1 --dry-run
  • Rebind provider metadata for all local threads: ./codex-history-manager change-provider-all --provider openai1 --dry-run

Safety rules

  • Never perform a write first. Use the default dry run or pass --dry-run.
  • Only use --apply after reviewing the plan.
  • Prefer cloning over moving unless the user explicitly wants to change ownership.
  • Do not hand edit state_5.sqlite or rollout files if the CLI can do the job.
  • If the user asks to modify message content, stop and confirm. You must first produce a dangerous edit plan, present the warning and change list in the conversation, and wait for explicit user approval before running apply-dangerous-edit.

Read these references only when needed:

Usage Guidance
This tool appears to be what it says: a local CLI to inspect and manage Codex history under ~/.codex. Key precautions: (1) Review and run any destructive command with --dry-run first and inspect the generated plan file; (2) keep in mind apply-dangerous-edit can rewrite stored conversation text — follow the plan → present → explicit-approval → apply flow exactly; (3) backups are created by default under the package's backups/ directory—consider specifying --backup-root to a location you control; (4) the skill operates on local files only (no network calls in the included code), but these files may contain sensitive conversation data — only run it in a trusted local environment. If you want extra assurance, inspect the included scripts (scripts/codex_history_manager.py) before executing any write operations.
Capability Analysis
Type: OpenClaw Skill Name: codex-history-manager Version: 1.0.0 The codex-history-manager skill provides a CLI and agent instructions for managing local Codex chat history stored in ~/.codex. While the tool is well-documented and includes safety mechanisms such as mandatory backups, dry-run modes, and a two-step confirmation process for content rewrites, it possesses high-risk capabilities including the ability to globally modify or delete historical database records and session logs (scripts/codex_history_manager.py). These capabilities are aligned with the stated purpose but represent a significant risk if the agent is manipulated into performing unauthorized data modification or deletion. No evidence of malicious intent or data exfiltration was found.
Capability Assessment
✓ Purpose & Capability
Name/description, README, SKILL.md, and the included Python scripts all focus on reading and mutating local Codex data under ~/.codex (state_5.sqlite and rollout JSONL). The requested/required resources (none) and provided code match the purpose; there are no unrelated credentials, network endpoints, or external services referenced.
ℹ Instruction Scope
Runtime instructions tell the agent to run the bundled CLI to search, export, clone/move, rebind provider metadata, and perform 'dangerous' history rewrites. The SKILL.md explicitly limits scope to ~/.codex and prescribes dry-run and explicit approval flows for destructive changes. This is coherent, but the skill does permit high-risk local modifications (rewriting transcript bodies) so users must follow the stated approval steps (plan → present changes in-chat → explicit approval → apply).
✓ Install Mechanism
No install spec is provided (instruction-only at registry level), but the package includes Python scripts that can be executed directly. There are no external downloads or third-party install sources in the manifest. Running the CLI will execute local code included in the skill bundle.
✓ Credentials
The skill requires no environment variables, no external credentials, and only accesses local Codex data paths (~/.codex) and a default backup directory inside the package tree. Requested access is proportional to the declared functionality. There are no unexplained SECRET/TOKEN/PASSWORD requirements.
✓ Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. It does write backups and can mutate local files when run with --apply; those behaviors are documented in references/safety.md and guarded by dry-run and explicit-ack flags for dangerous edits.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install codex-history-manager
  3. After installation, invoke the skill by name or use /codex-history-manager
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial public release of codex-history-manager. - Search, read, export, and hand off local Codex history threads. - Clone or move threads/workspaces; rebind provider metadata. - Export transcripts and generate handoff notes. - Strict safety workflow: dry-run for all writes, explicit approval for dangerous content edits. - CLI as source of truth—do not edit storage directly.
Metadata
Slug codex-history-manager
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is codex-history-manager?

Search, read, export, hand off, clone, move, or rebind local Codex history stored under ~/.codex. Use when the user wants to inspect past Codex sessions, bri... It is an AI Agent Skill for Claude Code / OpenClaw, with 75 downloads so far.

How do I install codex-history-manager?

Run "/install codex-history-manager" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is codex-history-manager free?

Yes, codex-history-manager is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does codex-history-manager support?

codex-history-manager is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created codex-history-manager?

It is built and maintained by Severin Zhong (@severinzhong); the current version is v1.0.0.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments