Codex Cache
Codex stores a local cache under ~/.codex/cache for app and connector metadata that helps the desktop client avoid re-fetching model catalogs, tool descriptors, provider manifests, icon assets, and other short-lived API responses on every launch. When those JSON metadata snapshots, HTTP response bodies, image thumbnails, and temporary index files go stale or become inconsistent after an app update or connector change, the interface can show outdated providers, missing icons, or failed refreshes; Kudu removes only this rebuildable cache while leaving sessions, archives, memories, attachments, generated images, credentials, configuration, plugins, and installed runtimes untouched.
Why clean Codex Cache?
- Stale connector manifests can leave renamed or removed tools visible in the picker, causing launch errors or actions that fail immediately when selected
- Corrupted cached metadata responses can trap the app in endless loading spinners during startup or while refreshing available models and providers
- Outdated provider catalogs may hide newly added models or keep showing deprecated ones, so the user sees the wrong options even after reconnecting
- Broken cached icon and thumbnail assets can produce blank provider logos or incomplete sidebars, making connectors look missing even though the account is intact
- Cache files accumulated from repeated metadata syncs can grow unexpectedly large, wasting disk space without affecting chats, archives, or saved attachments
- Schema changes after a Codex update can make older cache entries unreadable, leading to repeated refresh prompts, partial UI rendering, or metadata fetch failures until the cache is rebuilt
- If Codex stores metadata in SQLite-backed cache files, page fragmentation can bloat disk usage over time; VACUUM rewrites the database pages compactly without deleting any sessions or user content
Cache paths Kudu targets
Windows
~/.codex/cache |
macOS
~/.codex/cache |
Linux
~/.codex/cache |
Common questions about Codex Cache
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.