Keep Codex Fast

Install

npx skillfoxx add skills/keep-codex-fast

npx skills add vibeforge1111/keep-codex-fast --skill keep-codex-fast -a claude-code -y

npx skills add vibeforge1111/keep-codex-fast --skill keep-codex-fast -a cursor -y

npx skills add vibeforge1111/keep-codex-fast --skill keep-codex-fast -a github-copilot -y

npx skills add vibeforge1111/keep-codex-fast --skill keep-codex-fast -a codex -y

npx skills add vibeforge1111/keep-codex-fast --skill keep-codex-fast -a gemini-cli -y

npx skills add vibeforge1111/keep-codex-fast --skill keep-codex-fast -a cline -y

npx skills add vibeforge1111/keep-codex-fast --skill keep-codex-fast -a roo -y

npx skills add vibeforge1111/keep-codex-fast --skill keep-codex-fast -a opencode -y

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.

Example request

Inspect my local Codex state and suggest a safe maintenance plan

Limitations

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.

Security check

• Runs a script that moves and archives local Codex files and rotates logs
• The repair option edits title metadata in the SQLite file

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.

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.

Related