codex-history-sync

Codex history migration uses conservative one-way copying between .codex directories, preserving session files and thread title metadata. It excludes sensitive files by default and supports dry-run validation to prevent overwriting existing target data.

Yes, Codex history sync supports dry-run validation, which reports what files would be copied, skipped, or renamed without modifying the destination. This prevents accidental overwrites of existing target data or credentials.

Yes, Codex history sync repairs and preserves thread title and name metadata across SQLite, JSONL, and JSON records. The process ensures metadata consistency across session files after copying to the destination directory.

Using safety-first defaults during Codex history sync automatically excludes sensitive files and cache-like folders from the backup. This ensures you copy session files without risking credentials or configuration data.

You can filter Codex history records for a specific project by applying regex filtering during the directory sync. This selectively copies relevant session files while excluding unrelated history, enabling targeted project-scoped sharing.

Use the optional force overwrite control when replacing existing files in the destination .codex directory. Apply force only after dry-run validation confirms no critical configuration or credentials will be lost during the sync.