Keep Codex Fast skill
A Codex skill for safe local-state maintenance: a report-only default, backup and archive instead of deletion, log and worktree cleanup
- 1,602 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Runs a script that moves and archives local Codex files and rotates logs
- The repair option edits title metadata in the SQLite file
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/keep-codex-fastDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Runs a script that moves and archives local Codex files and rotates logs
- The repair option edits title metadata in the SQLite file
This is third-party code. Review the repository files before installing.
What it does
The skill helps Codex figure out why local state has grown and clean it up carefully without losing context. By default it only builds a report: active and archived session size, large chats, bloated title and preview metadata, stale worktrees, log size and heavy Node processes. Before changing anything it recommends handoff documents for active chats, then it backs up and archives rather than deletes. When run explicitly with flags it moves stale worktrees, rotates large logs, prunes dead entries in config.toml and normalizes Windows paths. A separate repair option shortens oversized SQLite title and preview metadata after a backup, leaving the transcript intact.
Who it is for. For heavy Codex Desktop or CLI users who notice the interface has slowed down.
Good fit when
- Codex has slowed down after heavy use and you need to see what grew
- You want to safely trim old sessions, worktrees and logs with backup and archive
- You want to preserve active chat context via handoff documents before cleanup
Not a fit when
- You need to clean another tool's state, not Codex
- You are fine deleting data without backups or archives to save maximum space
Example request
Inspect my local Codex state and suggest a safe maintenance planLimitations
The skill targets local Codex Desktop and CLI state. Running the script needs Python. Mutating actions apply only when run explicitly with flags and when Codex is closed. The repair option touches title and preview metadata only behind a separate flag. Backup folders hold local Codex metadata and should not be published without reviewing what is inside.
How to disable. Remove the keep-codex-fast folder from the Codex skills directory. Previously created backups and archives stay on disk; delete them manually if needed.
FAQ
Does the skill delete my chats?
No. It archives and moves files rather than deleting, and writes manifests and restore scripts. The first run is always report only.
Can I run it while Codex is open?
The report runs either way, but mutating actions apply only after Codex is closed or with the wait-for-exit flag.
Discussion
No questions or reviews yet.
Related
SkillsA utility that brings back Codex threads lost after a provider switch by syncing sessions and SQLite and making backups.
A local task board with the taskctl CLI and a skill for Codex, Claude Code, and other agents: creates issues, moves statuses, and keeps comments under a fixed w
A CLI that shows Codex usage limits and the number of manual resets, and spends one reset after explicit confirmation.
A plugin and MCP tools show where Codex tokens, time, credits and money go, based on local session metadata.
Several desktop Codex copies side by side: each account gets its own icon, sign-in, chats and plugins with no switching.
A personal AI chief of staff on a notes folder: daily plan, meeting prep, tasks and people context in Claude Code and Cursor.
README in short
The README describes three modes: report-only inspect, normal apply with backup and archive, and a separate repair of bloated title metadata. It stresses the principle: handoffs first, archive instead of delete, apply only when ready. The skill installs via Codex from the repository link or by copying the folder into the skills directory, and the script can also run manually with the details, backup-only, apply and repair-thread-metadata-bloat flags. It notes that backups hold private local data. MIT licensed.
README badge
Original SKILL.md
--- name: "keep-codex-fast" description: "Use when Codex feels slow or bloated, when local sessions/logs/worktrees/config have grown over time, or when a user wants safe maintenance for Codex Desktop/CLI state. Provides a read-only report by default, backs up before applying changes, archives instead of deleting, normalizes Windows extended paths, prunes dead config projects, rotates large logs, and moves stale worktrees." metadata: short-description: "Safe Codex local-state maintenance" --- # Keep Codex Fast Use this skill to inspect and safely maintain local Codex state. The goal is to reduce local drag without surprising the user or losing continuity. Primary principle: preserve continuity before applying changes. For active repo chats the user may continue, recommend a comprehensive handoff document and reactivation prompt before archiving anything. ## Safety Rules - Inspect before mutating. - The first run must be report-only. Report mode must not write files, create backups, move folders, or change local Codex state. - Back up before applying changes. Use `--backup-only` when the user wants backups without moving or changing local state. - Archive or move files instead of deleting them. Do not permanently delete user chats, logs, worktrees, memories, skills, plugins, or automations. - Write manifests and restore scripts when sessions/worktrees are moved. - If Codex is running, default to report-only. Apply changes only after Codex is closed or when the user explicitly accepts waiting for Codex to exit.