Skin for Codex
Dream Skin and a native theme solve different jobs.
A Dream Skin can personalize an upstream-supported visual workflow today, while a native theme would be an official configuration feature with a different maintenance and security contract.
Capability and maintenance
Dream Skin exports images, colors, and macOS labels through the current upstream engine. A native theme would be expected to keep a stable official contract; Dream Skin can change when the upstream asset contract changes.
Security and reversibility
A native theme avoids third-party injection. Dream Skin requires inspected files, a version pin, and backups, but the change is reversible when you restore the original upstream assets.
When Dream Skin is appropriate
Choose it only if you accept an unofficial, version-specific workflow and want visual control now. Do not describe it as an OpenAI feature, and prefer official theming if and when it meets your needs.