How to Share and Export a Codex Theme Safely
Review a Codex theme share string for privacy, provenance, compatibility, and licensing before sending it to someone else.
Quick answer
Export the theme through Codex Appearance settings, inspect the complete text, document the app build and platform, and share the string through a channel where recipients can verify its source. Never bundle a native theme with an unrelated installer.
This review reflects Codex App build 26.707.72221 on macOS as of July 17, 2026.
Inspect the payload
A native theme share string should describe appearance values. Review it for unexpected tokens, local file paths, email addresses, project names, or user data. The current codex-theme-v1 shape contains a variant, a code-theme identifier, colors, contrast, font choices, and an opaque-windows preference.
Colors and font names are not automatically private, but a custom font name or copied project label can reveal more than intended. Remove unrelated data by recreating the theme in Codex and exporting again; do not hand-edit unknown fields and hope the result remains valid.
Attach provenance
Publish the theme name, source URL, verified date, tested Codex build, platform, and license. If you use artwork in a separate external Skin package, confirm you have redistribution rights. A native color share string and a wallpaper package are different artifacts with different rights questions.
Recipients should compare the source, inspect the string as text, and import only through Codex Appearance. A string that arrives with commands, binaries, or instructions to enable CDP is no longer just a native theme.
Keep the previous appearance available and test the imported result before continuing work. For design guidance, see create a custom theme. For recovery, see reset or remove a theme.