codex-sessions-manager

To clean up Codex session residues, audit the local Codex root directory to find orphaned files, JSONL indexes, and SQLite rows, then execute safe delete or trash operations with explicit confirmation to remove the leftovers completely.

Codex local session residue consists of leftover files, JSONL indexes, SQLite rows, and global-state references that remain under a Codex root because the Desktop archive or delete process does not fully purge all local storage surfaces.

Scan your Codex root directory using a root-wide residue scanning tool to automatically find likely leftover session candidates, preview what deletion would touch, and generate read-only deletion plans without needing the specific session ID first.

Yes, you can safely restore a deleted Codex session because the cleanup workflow supports exporting backups and using a trash mechanism, allowing you to restore sessions and verify that no data is permanently lost during the audit process.

Yes, the Codex session audit process requires YAML-driven skill activation instructions that coordinate a local CLI and MCP stdio server to perform read-only audit planning and execute explicit-confirmation write actions safely.

The safest way to verify nothing is left behind after purging Codex session data is to inspect the specific session ID for missing family edges and storage surfaces, then run a post-deletion SQLite verification to confirm complete removal.