Feature request: UI export/import for portable Codex profile across Macs

What variant of Codex are you using?

APP

What feature would you like to see?

I would like Codex to support exporting and importing a portable local Codex profile so I can move the same Codex setup between my own Macs.

This is related to #26691, but this request focuses specifically on making the workflow available from the Codex desktop UI, not only through manual folder copying or a possible CLI.

Desired behavior:

• Export one portable folder or archive that can be copied to another Mac.
• Import that folder/archive on the second Mac and restore the same Codex setup to the same logical paths.
• Provide the workflow in the Codex UI, ideally under something like Settings -> Profile -> Export / Import.
• Keep a CLI path as well for advanced users and automation.

Suggested UI flow:

1. User opens Codex settings.
2. User clicks Export Codex Profile.
3. Codex shows checkboxes for what to include:

• user skills, such as ~/.agents/skills and/or ~/.codex/skills
• project-local skills selected by the user
• global/user AGENTS.md
• selected project AGENTS.md files
• safe non-secret Codex settings
• plugin/skill restore metadata needed to recreate the same layout

1. Codex shows a clear warning that secrets, sessions, caches, logs, databases, and runtime state will not be exported.
2. User chooses a destination folder, for example Desktop.
3. Codex creates a portable folder/archive with a manifest.
4. On the second Mac, user opens Codex and clicks Import Codex Profile.
5. Codex shows a dry-run preview before writing anything:

• files to add
• files to overwrite
• conflicts
• skipped sensitive files
• source paths and target paths

1. User confirms import.
2. Codex restores the selected setup on the second Mac.

Suggested CLI shape:

codex profile export --to ~/Desktop/codex-profile-backup
codex profile import --from ~/Desktop/codex-profile-backup --dry-run
codex profile import --from ~/Desktop/codex-profile-backup

The export should include safe portable user setup:

• user skills, for example ~/.agents/skills and/or ~/.codex/skills
• selected project-local skills
• global/user AGENTS.md
• selected project AGENTS.md files
• safe non-secret Codex configuration
• plugin/skill metadata needed to restore the same layout
• a manifest with original paths, target paths, file hashes, Codex version, and export date

The export must not include secrets or machine-specific runtime state:

• auth files
• API keys or tokens
• sessions
• logs
• caches
• SQLite databases
• runtime histories
• machine IDs
• temporary files
• absolute project trust paths unless explicitly approved

Optional sync workflow:

Codex could also support choosing a portable profile folder and keeping selected profile files synchronized through that folder. Users could place that folder in iCloud Drive, Dropbox, Syncthing, Git, or another user-controlled sync system. The same secret and machine-specific file exclusions should still apply.

Additional information

Codex skills and AGENTS.md rules are personal workflow configuration. Users often work on more than one Mac and want the same Codex behavior on each device.

Today this is error-prone because the setup can be spread across hidden folders and project folders. A native UI export/import flow would make this discoverable, safer, reversible, and easier to use without manually copying internal Codex directories.