教程
一步步教你应用第一款 Codex 皮肤，并保持可逆。
开始之前
Skins style Codex at the visual layer only, over <code class="font-mono text-fg-2">127.0.0.1</code>. No app files are modified and your API key is never touched.
-
一次性安装引擎
克隆或下载一款皮肤引擎（如 Codex Dream Skin），或使用像 Codex Skin Manager 这样的管理器。这是一次性的本机配置。
-
在索引中选择一款皮肤
按分类浏览或按氛围、颜色搜索。打开皮肤页面查看描述、兼容平台和准确的安装提示。
-
复制并应用
点击提示旁的"复制"按钮，粘贴到 Codex Desktop，或运行 CLI 命令。工作区会立即更新。
-
验证并保留来源
确认新外观后，收藏来源链接。如果 Codex 升级后皮肤失效，重新执行来源还原步骤即可回到默认。
小贴士
- Start with a featured skin — it is the most likely to apply cleanly through the engine's default preset.
- 按原样复制提示文本；任何小修改都可能改变引擎应用的结果。
- 保留来源链接，方便 Codex 升级后还原或重新应用。
- 使用分类和氛围筛选器，从 100+ 款皮肤中快速找到适合你的几款。
选择引擎
引擎决定皮肤的安装方式和可用的格式。全部免费且开源。
| 引擎 | 平台 | 安装方式 | 说明 |
|---|---|---|---|
| Codex Dream Skin | macOS, Windows | Agent prompt / preset | Core open-source engine; local CDP injection, no app modification. |
| Codex Skin Manager | macOS, Windows | Built-in manager | 14 built-in themes plus a theme creator and Codex Skill. |
| Codex Themes (desktop) | macOS | .codextheme import | Gallery and creator center at theme.codexguide.ai. |
| ReTheme | macOS, Windows | Signed themes | Tauri-based; signed, updatable, community themes. |
| Codex Themes CLI | Cross-platform | CLI /theme | Validate, preview, apply, rollback, export palettes. |
| Codepilot | Cross-platform | Built-in TUI /skin | Codex CLI distribution with 16 built-in TUI skins. |
故障排查
四个最常见问题及解决方法。
-
Prompt applies but nothing visibly changes
Confirm the engine is running and pointed at the right Codex window. Restart Codex Desktop, then re-apply.
-
Skin looks different from the preview
Previews approximate the source palette. Check the source link for the exact theme file and version.
-
Codex updated and the skin stopped working
Use the engine's restore-to-default option, then re-apply. Keeping the source link makes this a two-minute fix.
-
CLI /theme says no themes installed
Run the port install script first, then reopen the CLI prompt. Some ports cache colors at startup.
Need the short version? See the install guide, the FAQ, or the full install blog post.