Builder images stay local
The public Builder uses object URLs and Canvas and does not send your selected wallpaper to the server. Recipes and share links contain settings only.
Local data · Transparent packages · Explicit CDP boundary
A theme should be inspectable before it is attractive.
The Builder keeps images in browser memory. Installation is a separate upstream process with more power and a different risk boundary.
ZIPs stay data-only
Package v1 contains a wallpaper, canonical recipe, manifest, CSS tokens, readable install/restore/verify notes, and complete SHA256SUMS. It contains no script, executable, credential, or hidden installer.
CDP remains powerful
Loopback blocks ordinary network access but does not authenticate other same-user local processes. Run only trusted software and Restore when done.
Compatibility needs evidence
Record platform, architecture, Codex version, upstream commit, checked date, real routes, and restore outcome. A thumbnail is not verification.
Supply-chain rules
- Use the original repository and compare the current main branch with
611c10176a27. - Read commands before running them. Stop on package mutation, signature bypass, credential access, or non-loopback debug exposure.
- Verify SHA-256 values for transported files, while remembering that checksums prove identity—not benevolence.
- Never redistribute character, celebrity, game, film, or brand artwork without rights.