Codex Skin changelog
Production release notes for the Codex Skin Plugin, Helper, Bootstrap, theme workflow, and any action current users need to take.
This changelog records changes that reached the Production user path and can be observed by users. It does not copy Commit, pull request, CI, Staging, RC, or candidate history into the product timeline.
The public GitHub release is the source for Plugin-side publication dates. Website and theme-catalog changes appear here only when a separate Production record can verify their date and user impact.
Latest
August 25, 2026: Production Paid Alpha
| Product surface | Production release |
|---|---|
| Plugin | 0.1.0-paid-alpha |
| Helper | .17 |
| Bootstrap | .16 |
| API origin | https://codexskin.ai |
| Channel | GitHub prerelease, not stable/latest |
Source: Codex Skin Helper 0.1.0-paid-alpha.17 (Production)
What changed for users
- Apply, Switch, and Restore use one bounded Helper transaction. The Helper verifies the current visible result, commits or rolls back, then exits.
- Apply and Switch show a 20–60 second current-window warning. Browser authorization or Pricing can still be completed in the page opened by the transaction, and a long-running operation gives one reminder instead of inviting a second submission.
- macOS cross-mode changes prefer the verified in-app Appearance path. If that fixed interface is unavailable before mutation, the operation asks for one controlled reload. Windows keeps the one-confirmation controlled reload path for cross-mode changes.
- The first Apply preserves the exact native
system,light, ordarksetting and related code-theme value. Same-mode replacements do not rewrite that setting or restart. Restore writes the original values back. - Offline Restore remains outside the Plugin cache and does not require network, login, active access, Node, or a working Plugin cache.
- Success means the exact theme was visibly verified in the current Codex window. A download, restart acceptance, or running state is not success.
What action do I need?
If $codex-skin-version already reports Plugin 0.1.0-paid-alpha, Helper .17, Bootstrap .16, and https://codexskin.ai, no update action is needed.
For an older installed line, use the canonical Plugin upgrade steps, completely quit Codex, reopen it, and run $codex-skin-version in a new task. Do not replace the release with a manually downloaded Helper.
After completely quitting Codex, restarting the computer, or a later renderer reload, apply the desired theme again. This is the current-window boundary of the Paid Alpha, not a separate update failure.
Release history
The first verified Production entry is the August 25, 2026 Paid Alpha release above. Earlier .2 through .16 Helper tags and the 0.0.1/0.0.2 lines in the public repository are development, Staging, or unreleased history. They are not presented as earlier customer releases here.
Future entries will use their public Production publication date, identify the affected surface, describe what a user can observe, and state whether action is required. A release entry will not appear merely because code was merged or an automated check passed.
Action labels
Each Production entry uses one of these actions:
| Label | Meaning |
|---|---|
| No action | The current installed and verified release already includes the change. |
| Upgrade Plugin | Refresh the Git-backed Marketplace, reinstall the same Plugin ID, reopen Codex, and verify the version in a new task. |
| Reapply theme | Run one new Apply because a full quit, restart, renderer reload, or documented behavior change ended the current-window guarantee. |
| Review Restore guidance | Read the current recovery instructions before another theme operation. |
Sources and corrections
Every dated entry must point to a public Production source. Plugin, Helper, and Bootstrap entries link the matching public GitHub Release. Website or catalog entries require a separately verified Production publication record and a user-visible result.
If an entry needs correction, the page will preserve the original release date and add a correction date with the changed fact. It will not silently rewrite a Staging candidate, internal implementation detail, or automated check into a customer feature.
Current guides:
