vibeforge1111/keep-codex-fast

Keep Codex Fast is a maintenance tool for Codex, OpenAI's coding agent. After weeks of heavy use, long chats, multiple terminals, old project branches, and accumulated logs, Codex can start to feel sluggish. This project gives you a safe, structured way to clean up that local clutter and speed things back up without losing any of your work or context. The core philosophy is "archive, don't delete." Before any cleanup happens, the tool creates handoff documents: short notes that capture what you were working on, what changed, which files matter, and what to do next. Then it backs up your current state and moves old chats and stale project files into archive folders rather than permanently removing them. It also rotates large log files, prunes dead project references, and can detect when thread titles or preview metadata have bloated to the point of slowing down chat navigation. That bloat happens because some Codex builds store the entire first user prompt as both the thread title and list preview, sometimes growing to hundreds of thousands of characters. The tool operates in three modes. Inspect is read-only and just reports what it finds. Maintain applies the cleanup: backing up, archiving old sessions, moving stale worktrees, rotating logs, and pruning dead config. An optional repair mode trims oversized title and preview metadata, but only when you explicitly opt in with a special flag. Nothing happens automatically, you review the report first, then decide what to archive and when to apply changes. The tool also refuses to modify anything while Codex is still running. This is built for people who use Codex intensively: developers juggling multiple repositories, long-running chat threads, several terminals, and dev servers. If you frequently resume old conversations or keep extensive chat history around, you will likely hit slowdowns. The tool also supports a recurring reminder mode that runs the read-only report on a weekly or biweekly schedule, nudging you to create handoffs and clean up, but never mutating anything on its own. The project's mental model is simple: chats are for execution, handoff docs are for memory, archives are for history, and fresh threads are for speed. That philosophy drives every design choice, and the safety-first approach, backups before changes, archive instead of delete, human confirmation before applying, makes maintenance feel manageable rather than risky.