sync-codex-dotfiles

To sync Codex global configuration into dotfiles without copying local state, run the sync script to preview a sanitized diff of shared settings, then apply the changes. This process filters out machine-local credentials and runtime paths, ensuring only consistent preferences are synced across devices.

Keeping Codex settings consistent across multiple devices is best achieved by automating config synchronization into your dotfiles. This approach filters out machine-local state like project trust, caches, and credentials, ensuring that only shared preferences, models, and profiles are synced across machines.

The Codex dotfiles sync filtering mechanism works by extracting global configuration from your local Codex directory and filtering out machine-local state. It specifically isolates shared preferences, agents, features, and plugins while excluding local project data, sessions, credentials, and runtime paths from the sync.

To preview sanitized Codex config changes before applying them to dotfiles, execute the sync script without arguments. This generates a diff of the sanitized configuration, allowing you to review the shared settings before applying the changes with the apply flag.

You cannot use this config automation script to sync credentials and sessions to your dotfiles. The sync mechanism is specifically designed to filter out machine-local state, including credentials, sessions, caches, and local project trust, ensuring only shared preferences are synced across devices.

You need to automate Codex configuration management for dotfiles when you require consistent settings across multiple devices and want to avoid manually duplicating local project data. This is ideal for maintaining shared preferences, models, agents, and desktop-wide settings without copying sensitive machine-local state.