Your image stays local
Your image and recipe are processed on your own machine. We never receive them — by design.
Install guide · macOS
No terminal skills, no account, no GitHub. From Studio export to a skinned Codex, all you need is a double-click.
Step 1
Tune your image, colors and framing in the Studio, then hit “Export recipe” at the bottom right. Your browser downloads a ~300 KB ZIP — one image, one config file and two double-click scripts. Nothing to install yet.
Step 2
Double-click the downloaded ZIP and a folder with five files appears. You only need to care about the first two.
Step 3
The script came from the internet, so macOS stops it the first time. That is expected. Right-click “Apply Codex Skin” → Open, then click Open in the dialog. Once per file — after that a plain double-click works.
No right-click? Control-click instead, or go to System Settings → Privacy & Security → “Open Anyway”.
Open
Move to Trash
Get Info
“Apply Codex Skin” was downloaded from the internet. Are you sure you want to open it?
Step 4
A Terminal window pops up and does the work: on the first run it also downloads the skin engine (~2.5 MB, once only). Done: means your skin is live. Close the window and open Codex.
If Codex is already running the skin applies instantly; otherwise it shows up on the next launch.
$ ./Apply Codex Skin.command
# first run only: fetch the engine (~2.5 MB)
Downloading / updating the CodexSkins engine...
Switching...
Done: my-first-skin ✓Undo anytime
The engine never modifies the Codex app or its signature — the skin is just a layer over the window. Double-click Restore.command to remove that layer and return to the original look immediately.
Your image and recipe are processed on your own machine. We never receive them — by design.
Every line of the skin engine is public. Source is linked in the footer — read it before you run it.
The installer is macOS-only for now. A Windows package is in testing and will be marked site-wide.