codex-clean-history

星标1

分支0

更新时间2026年6月4日 19:56

Clean Codex local history artifacts that can contain logs, prompts, user input text, command traces, and session transcripts while preserving memories and configuration. Use when the user asks to delete, purge, wipe, prune, reset, or preview Codex history/log/session/input records, especially `~/.codex/history.jsonl`, `~/.codex/sessions/`, `~/.codex/log/`, `~/.codex/logs_*.sqlite`, or shell snapshots, and explicitly not memories.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

lollipopkit

lollipopkit/agent-skills

打开 GitHub 仓库查看创作者相关仓库

下载

Codex Clean History

Quick Start

Use scripts/clean_codex_history.py to inspect or clean local Codex history artifacts. The script defaults to dry-run and preserves memory, configuration, authentication, rules, skills, plugins, cache, and goal/state databases.

python3 /path/to/codex-clean-history/scripts/clean_codex_history.py
python3 /path/to/codex-clean-history/scripts/clean_codex_history.py --apply
python3 /path/to/codex-clean-history/scripts/clean_codex_history.py --codex-home ~/.codex --days 30 --apply

Workflow

Resolve Codex home from --codex-home, $CODEX_HOME, or ~/.codex.
Run the script without --apply first and show the user the planned deletions.
If the user asked to actually clean, rerun with --apply.
If the user asks to keep recent history, pass --days N to remove only matching artifacts older than N days.
If the user asks to include or exclude specific categories, use the script flags instead of manually deleting files.

Cleanup Scope

Default targets:

history.jsonl
sessions/
log/
logs_*.sqlite, including -wal and -shm sidecars
shell_snapshots/
temporary Codex files under .tmp/ and tmp/

Never target these by default:

memories/
memories_*.sqlite, including sidecars
config.toml
auth.json
rules/
skills/
plugins/
cache/
goals_*.sqlite
state_*.sqlite
models_cache.json
installation_id
version.json

Safety Rules

Prefer the script over ad hoc rm commands.
Keep dry-run output in the response when the user asks what would be removed.
Do not clean memories unless the user explicitly changes the requirement.
If Codex is currently running, warn that open sessions may recreate log/session files after cleanup.

同仓库更多 Skills

同仓库

handoff

lollipopkit/agent-skills

Create concise, evidence-based handoff notes for another AI coding agent. Use when the user asks for a handoff, continuity note, next-agent summary, progress transfer, "告诉别的 agent", "handoff skill", "交接", or wants the current state, completed work, remaining plan items, risks, and next steps captured for another agent without writing a verbose work log.

2026-06-011

linked-doc

lollipopkit/agent-skills

Maintain an evolving linked documentation library for project wikis, ADRs, design notes, research notes, release notes, and decision logs. Use when asked to create, grow, repair, reorganize, or verify a wiki/ADR knowledge base with Markdown pages, YAML frontmatter, Obsidian-style [[wikilinks]], source-backed citations, llmwiki/llm-wiki-compiler projects, or a durable project memory that should compound over time instead of being rewritten from scratch.

2026-06-011

trailbase

lollipopkit/agent-skills

TrailBase project guide for installing and running the single-executable backend, configuring traildepot/config.textproto and migrations, exposing Record APIs, using auth and token flows, integrating first-party SDKs for TypeScript/JavaScript, Dart/Flutter, Rust, C#/.NET, Swift, Kotlin, Go, and Python, calling HTTP APIs directly, implementing WASM custom endpoints, and locating relevant source/docs in the trailbase repository. Use when Codex needs to answer or implement TrailBase setup, SDK, REST/HTTP API, auth, realtime, configuration, migration, deployment, or custom endpoint work.

2026-06-011

use-fllib

lollipopkit/agent-skills

Use fl_lib stores, widgets, utils, and extensions in Flutter apps. Use when requests mention fl_lib APIs or integration.

2025-12-251

name

codex-clean-history

description

Codex Clean History

Quick Start

python3 /path/to/codex-clean-history/scripts/clean_codex_history.py
python3 /path/to/codex-clean-history/scripts/clean_codex_history.py --apply
python3 /path/to/codex-clean-history/scripts/clean_codex_history.py --codex-home ~/.codex --days 30 --apply

Workflow

Resolve Codex home from --codex-home, $CODEX_HOME, or ~/.codex.
Run the script without --apply first and show the user the planned deletions.
If the user asked to actually clean, rerun with --apply.
If the user asks to keep recent history, pass --days N to remove only matching artifacts older than N days.
If the user asks to include or exclude specific categories, use the script flags instead of manually deleting files.

Cleanup Scope

Default targets:

history.jsonl
sessions/
log/
logs_*.sqlite, including -wal and -shm sidecars
shell_snapshots/
temporary Codex files under .tmp/ and tmp/

Never target these by default:

memories/
memories_*.sqlite, including sidecars
config.toml
auth.json
rules/
skills/
plugins/
cache/
goals_*.sqlite
state_*.sqlite
models_cache.json
installation_id
version.json

Safety Rules

Prefer the script over ad hoc rm commands.
Keep dry-run output in the response when the user asks what would be removed.
Do not clean memories unless the user explicitly changes the requirement.
If Codex is currently running, warn that open sessions may recreate log/session files after cleanup.