Codex History Manager for Openclaw

A powerful CLI utility for searching, migrating, and exporting local Codex history files and metadata.

severinzhong
v1.0.0
Apr 2, 2026
1
610
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install codex-history-manager

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install codex-history-manager using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Codex History Manager?

The Codex History Manager is a specialized tool designed to interact with local Codex history stored in the ~/.codex directory. As part of the Openclaw Skills collection, it provides a structured way to access thread metadata and rollout event logs without manual database manipulation. It bridges the gap between raw local storage and actionable session management, enabling developers to maintain a clean and searchable record of their AI-driven development workflows while ensuring data portability.

Codex History Manager Use Cases

  • Searching past coding sessions for specific implementation details using the Openclaw Skills search functionality.
  • Generating comprehensive handoff notes and transcripts for team collaboration or documentation.
  • Migrating conversation threads between different workspaces or updating provider metadata for existing sessions.
  • Performing safe, planned edits to message history content with explicit approval cycles to maintain record accuracy.

How Codex History Manager Works

  1. The tool identifies the local storage path for Codex metadata in the SQLite state file and rollout logs in the sessions directory.
  2. Users execute discovery commands like search to find specific thread IDs associated with their work.
  3. A dry run is performed for any modification or migration tasks to ensure data integrity within the Openclaw Skills environment.
  4. For content changes, a dangerous edit plan is generated and presented for user verification within the chat interface.
  5. Final operations are executed using the --apply flag to commit changes to the local state after explicit user approval.

Codex History Manager Setup

Ensure the codex-history-manager CLI is available in your workspace. You can start managing your Openclaw Skills data with the following command sequence:

# Search for a specific topic in your history
./codex-history-manager search --query "payments"

# Export a thread to markdown for review
./codex-history-manager export-thread --id <thread-id> --format markdown --output ./thread-export.md

Codex History Manager Data Schema & Taxonomy

Component Path/Source Description
Metadata Store ~/.codex/state_5.sqlite Central SQLite database storing thread IDs, timestamps, and workspace associations.
Event Logs ~/.codex/sessions/*.jsonl Contains the detailed message rolls and interaction history for active sessions.
Archive ~/.codex/archived_sessions/ Repository for sessions that have been moved out of the active sessions directory.

Codex History Manager Advanced Features

  • Dangerous history content rewrites with built-in planning and approval workflows to prevent accidental data loss.
  • Batch workspace migration and provider metadata rebinding across the Openclaw Skills ecosystem.
  • Multi-format export capabilities for creating high-quality Markdown transcripts or handoff notes.
  • Cross-workspace thread cloning to preserve development context when moving between project directories.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*