mrkeyoor.comAsk

Fei-Away/Codex-Dream-Skintested 14 Nov 2026commit 6fc42df

Codex-Dream-Skin review

Codex-Dream-Skin has named user reports of successful themes alongside version-linked interface failures.

  • Safety failed
  • Tests failed
2 sto install
  • 0 packages
Dev Toolsevaluationupdated 16 Nov 2026
+28stars / 7d

Codex-Dream-Skin is an unofficial visual customization tool for the Codex desktop app on macOS and Windows. Fei-Away's README describes local CDP injection without modifying the official application package. Theme installation and API-provider configuration are separate.

Verdict

Codex-Dream-Skin has named user reports of successful themes alongside version-linked interface failures. Consider it for a personal workstation where you can inspect Home, Task and the composer after updates and follow Fei-Away's Restore/restart guidance. Keep stock Codex where losing conversation or input access would interrupt essential work, or where unauthenticated local debugging access is prohibited.

Codex-Dream-Skin infographic: applies backgrounds and theme styling to Codex desktop, plus our test result and who it suits
Tested 30 September 2026: the source install took 8 s.

We ran it

Lab card: what happened when we ran Codex-Dream-Skin
Lab card from our sandbox run
Screenshot of Codex-Dream-Skin (www.dreamskin.cc)
www.dreamskin.cc
Install✓ · 2s0 packages · 5 MB
Buildn/ano build script
Tests✗ · 3sran, no count parsed
Known vulns00 critical · 0 high · 0 moderate · 0 low (npm audit)
Repo296 files~33,074 lines of source · 32.1 MB · 2 CI workflows · tests dir

Answers from our run

Does Codex-Dream-Skin build from source?

Dependencies installed in 2 seconds (0 packages), and the project has no separate build step. We cloned commit 6fc42df into a clean Debian container with 3 CPUs and no project-specific setup.

Do Codex-Dream-Skin's tests pass?

No. The project's own test command exited unsuccessfully after 3 seconds, and its output did not expose an individual test count.

Does Codex-Dream-Skin have known vulnerabilities in its dependencies?

npm audit found none in the dependency tree at the time of our run.

Who should not use Codex-Dream-Skin?

Workstations where losing conversation or composer access would interrupt essential work: issue #415 reports both disappearing.

What are the alternatives to Codex-Dream-Skin?

CodeFace, codexskin.io. Codex-Dream-Skin has named user reports of successful themes alongside version-linked interface failures.

Setup4/5Our source checkout installed in 2 s with 0 dependencies, but we did not run a README task.Editor’s note: The source-workspace install succeeded, but the evidence contains no completed setup and theme application on a supported desktop.
Docs2/5The 11,578-character README has no usage instructions or examples.Editor’s note: The supplied README covers installation, import and shutdown; the record contains no assessment of users completing those instructions.
Community5/5Last push on 2026-10-15, 15,421 stars and maintainers answered or closed 10 of the 10 most-discussed issues we sampled.Editor’s note: Named contributors supplied diagnoses and retests, but the sample does not assess support capacity or sustained response expectations.
Maturity2/5Latest release v1.5.21 on 2026-10-15, repository created 2026-07-15 and its test suite did not pass in our sandbox.Editor’s note: The issues document specific version-linked regressions and repairs, without a long-term reliability assessment of supported desktop use.

How we score

Who it’s for

Codex desktop users who want saved visual themes and can inspect Home, Task and the composer after updates.
Developers comfortable distinguishing theme-package validation, desktop handoff, CDP startup and renderer-layout failures.
Theme authors who want the documented Gallery, Online Studio and ZIP-import workflow.

Who it’s NOT for

Workstations where losing conversation or composer access would interrupt essential work: issue #415 reports both disappearing.
Users whose security requirements exclude unauthenticated local renderer-debugging access.
People seeking model-capability or API-provider changes through a visual theme.

Setup reality

Our November 14, 2026 sandbox used commit 6fc42df and the npm project under ./macos/. Installation succeeded in 2 seconds, with 0 dependencies recorded and 5 MB on disk. Build was skipped because there was no build script or target. Tests failed with exit 127 after 3 seconds. npm audit reported 0 known vulnerabilities. The test tail contains individual passing cases and explicit platform skips, without an overall passing-test count.

The recorded sandbox configuration was 3 CPUs, 8 GB RAM and image label lab-node:22. The November 13 desktop attempt failed the runner's Compose-file prerequisite; its deployment summary conflicts with that failed step, while teardown reported success.

Fei-Away's current README directs ordinary users to a DMG or Setup.exe after installing and quitting the official app. Packaged installation requires no source checkout or separate Node.js installation. Public packages are unsigned and updates are manual.

Codex-Dream-Skin can put custom artwork around the real Codex desktop interface, but installed styling can coexist with a broken composer. Issue #373 records passing checks alongside incorrect renderer mapping. This review concerns Fei-Away/Codex-Dream-Skin, whose supplied latest-release metadata names v1.5.21. The practical decision is whether a personalized interface is worth maintaining compatibility with the desktop app. Composer compatibility discussion.

Consider it for a personal workstation where you can inspect conversation visibility and input controls after updates. Keep the stock interface where temporarily losing those controls would interrupt essential work. Named users report successful themes as well as failures. A useful acceptance check includes opening an existing conversation and using the composer, rather than judging the result by its wallpaper or a green status label.

Launch stars show attention; user retests show working themes

The 4,808 launch stars measure attention; Prometheus-first's v1.5.14 retest reports successful theme application. The July 16, 2026 announcement reported that star count roughly 27 hours after repository creation. The supplied announcement identifies EIN Presswire distribution, and its disclosure identifies paid placement. Its compatibility statements are project claims. Prometheus-first's report instead connects a named theme and Dream Skin version to that user's application result. Project announcement, theme-application retest.

The supplied GitHub metadata records the last push on October 15, 2026, and the latest-release metadata names v1.5.21. Earlier issue discussions describe contributor diagnostics, partial repairs and subsequent retests. Those records answer different questions: a merged change identifies source work, a release identifies a distributed version, and an affected user's retest describes that user's result. Keep those statuses separate when deciding whether a repair matches your installation. Repository metadata.

What people use Codex-Dream-Skin for

Users report applying library themes, repairing Windows styling and inspecting macOS composer mappings through CDP. These uses involve both selecting artwork and maintaining the interface that displays it. Reports become more useful when they identify the theme, application version and steps taken, because successful import and a usable conversation surface describe different parts of the workflow.

Who What they did Reported outcome
Prometheus-first Applied Hogwarts · Enchanted Night from the theme library Reported success after reinstalling the official Store app, using Dream Skin v1.5.14, reapplying and accepting a restart. Issue #352
QingYe-05 Supplied Windows selector changes and shared theme assets Reported strong improvement in v1.5.16, with voice and send-button details remaining. Issue #373
GreenLv Inspected the macOS composer through read-only loopback CDP Located styling on the inner footer rather than the outer composer root. Issue #373
moxiangjing Injected and removed the skin on a healthy window Reported content collapse after injection and recovery after removal. Issue #415

M66Y reported recovering conversation content and the input box by changing a CSS hiding rule, then found that reapplication could overwrite a runtime-only patch. X user zyhwitness23 also described 熊家's open-source character-themed workstation as based on Codex-Dream-Skin. These are attributed repair and creator reports, respectively, rather than results from our sandbox. CSS repair report, derivative workstation post.

Prometheus-first's sequence involved several actions, including reinstalling the Store app and confirming a restart. GreenLv's inspection addressed a different problem: styling attached to the wrong surface. For a theme author, these examples support checking the controls after applying artwork. A library selection, an accepted package and a correctly styled composer are separate outcomes that deserve separate entries in a compatibility report.

What happened when we ran it

Our November 13, 2026 attempt failed the runner's required Compose-file check. The error names compose.yaml, compose.yml, docker-compose.yaml and docker-compose.yml as absent. This was a runner prerequisite; Fei-Away's installation overview directs desktop users to platform packages. The summary's deployment claim contradicts the specific failed step.

November 13 record Recorded answer Verdict Why
Safety step None of the four named Compose files existed Failed prerequisite The runner required a Compose file.
Run summary Claimed deployment with the repository's own Docker Compose, with every port bound to 127.0.0.1 Contradictory summary The preceding prerequisite failed.
Teardown teardown: ok Cleanup reported success Cleanup describes the teardown outcome.

The November run summary and teardown record remain part of the evidence. Their wording does not replace the failed prerequisite. Keeping that conflict visible prevents the harness's Compose requirement from becoming installation advice for a desktop tool whose README describes a DMG or Windows installer.

Our November 14, 2026 run used commit 6fc42df and the npm project under ./macos/. We measured installation at 2 seconds. The recorded sandbox configuration was 3 CPUs, 8 GB RAM and image label lab-node:22. The checkout contained 296 files, approximately 33,074 source lines and 32.1 MB of data. The harness recorded 9 seconds in total.

November 14 step Recorded answer Verdict Why
Install 2 seconds; 0 dependencies recorded; 5 MB on disk Succeeded The npm workspace installation completed.
Build No build script or target Skipped The harness performed no build operation.
Tests Exit 127 after 3 seconds Command failed Individual passing cases coexist with an unsuccessful enclosing command.
npm audit 0 known vulnerabilities: 0 critical, high, moderate or low Clean audit result These are dependency-audit findings.

The test command failed with exit 127 after 3 seconds. Its tail names session preservation after restart cancellation and official cancellation; failure handling for apple-event-timeout, still-running and quit-error; separate restart consent; successful live application without a restart request; cold launch; explicit CLI restart consent respecting official quit cancellation; and CLI start leaving a running app untouched without restart consent. These are individual log entries, rather than an overall passing-test count.

AppleScript was explicitly skipped because it requires macOS. Native SwiftPM build/XCTest were skipped because they require a full matching Xcode macOS platform. The scan found 2 CI workflow files and a tests directory, with no Dockerfile. The recorded failure remains exit 127; the supplied tail gives no command-level cause to attach to that result. The current packaged route requires no separate Node.js installation. Fei-Away installation overview.

Where people get stuck: wallpaper can remain while controls disappear

Issue #415 reports wallpaper and sidebar remaining visible while conversations and the composer disappeared. Other reports concern missing assets, startup, browser handoff and composer styling. Match the failure stage before choosing a repair: replacing a missing background asset addresses a different problem from a CSS rule hiding a content-bearing container. The table preserves the repair and the person reporting its outcome.

Symptom and source Reported repair Evidence status
Missing macOS background file, issue #26 Replaced the stale reference with bundled portal-hero.png; update the checkout or ZIP. Maintainer-reported source repair.
macOS content displaced on Codex 26.721, issue #244 v1.5.2 changes the old banner-wrapper behavior so content can reclaim space. Maintainer-reported release repair.
Windows startup and ZIP-import failures around v1.5.6, issue #307 v1.5.8 includes startup and import repairs. qinyogi reported recovered startup and ZIP import; browser handoff still failed.
Windows cold-start application rejected without a live session, issue #352 v1.5.14 establishes a visible baseline before downloading the candidate theme. Prometheus-first reported successful theme application.
Composer backgrounds and double borders, issue #373 v1.5.15 repairs root mapping; v1.5.16 adds omitted compatibility work. Windows contributor reported improvement with remaining button details.
Wallpaper remains while chat disappears, issue #415 Maintainer reports a narrower gradient-hiding selector in v1.5.19. Maintainer-reported release repair and user-reported local CSS recovery.

In issue #415, moxiangjing reported an injection/removal experiment on a healthy window. The composer measured 696x44 before injection; home-hero, composer and homeSurface collapsed to 0x0 after injection; removal restored 696x44. These are the user's measurements. M66Y separately reported recovering conversation content and the input box by removing the content-bearing attribute branch from the hiding rule while retaining decorative-gradient branches.

M66Y reported that reapplying the skin overwrote a runtime-only CSS edit. Their repair persisted after changing both installation-source CSS and installed engine CSS. That account explains why a temporary edit can disappear on reapplication. It supports checking which copy supplies the applied styling. The report identifies the two copies changed locally; the maintainer's release statement identifies a separate route for obtaining the selector repair. Patch-persistence report.

Compatibility needs both application versions and a retest

Issue #373 reopened after the maintainer acknowledged that v1.5.15 included only part of the submitted compatibility work. Omitted items included Windows background-change persistence, Codex 26.818 sticky gradients and Markdown table overflow. After v1.5.16, QingYe-05 reported strong improvement and remaining voice and send-button details. qiyou011 separately reported all themes failing on macOS Codex 26.820.60940 with Dream Skin v1.5.16. Compatibility discussion.

Issue #235 records a revised Windows startup diagnosis: debugging flags could remain present without a listening endpoint, and the maintainer identified the need for a non-default user-data directory. The supplied synthesis records a managed cdp-profile change merged through PR #390 at commit 7343723, with the issue still open. Record the symptom, revised explanation and merged change separately when following this repair. Windows startup discussion.

Issue #244 reports a normal Home screen alongside an unusable Task screen after Codex 26.721.31836. That difference supports inspecting Home, an existing Task and the composer after applying a theme. Open the views you use and check that messages and input controls remain visible. A landing-screen result answers one part of that practical check, even when the injector reports a successful connection.

Security: loopback CDP permits access by other local software

Fei-Away's README says CDP binds to 127.0.0.1 and has no authentication. Another process on the same computer may connect and inspect or control the renderer. Preserving the official package and code signature protects those files from modification; the active debugging connection creates a local access boundary of its own. The npm audit result concerns dependency findings. Fei-Away safety guidance.

The README says pausing the theme or stopping only the injector leaves an already-running Codex process's debug port open. Its documented route for ending exposure is a full Restore/restart, or quitting every Codex process and reopening the official app normally. Follow that shutdown guidance when ending a themed session, because stopping visual updates and closing the debugging session have different effects.

The documented library handoff accepts one theme-version identifier, downloads from a fixed official API, refuses redirects and requests native confirmation. The importer checks declared payload sizes and SHA-256 hashes. Safe CSS targets 12 registered parts, and archives are limited to 32 MiB compressed, 32 entries and 64 MiB expanded. The README also states that manifest.sig is unused for signature checking and manual folder placement bypasses ZIP archive checks.

Restore instructions belong to a specific repository

Fei-Away's README documents full Restore/restart; page-13 and page-16 belong to codex-dream-skin/codex-dream-skin. The Windows recovery switches and macOS engine-location instructions in those documents describe that separate repository. Their source URLs identify a different owner from the project reviewed here. Use Fei-Away's supplied README for this review's actionable recovery guidance, including the shutdown procedure described in the security section. Separate Windows document, separate macOS document.

Fei-Away's own README documents local saved-theme directories under ~/Library/Application Support/CodexDreamSkinStudio/themes/ on macOS and %LOCALAPPDATA%\CodexDreamSkin\themes\ on Windows. Both platform controls include Open Themes Folder. Its packaged route uses a DMG or Setup.exe, requires no source commands and preserves themes and images during manual updates. Its public packages are unsigned. These documented paths identify where saved themes belong. Fei-Away installation and import documentation.

English documentation exists alongside Chinese repair discussions

Fei-Away's supplied README is English and links a Windows English guide, while several detailed issue discussions are Chinese. Those threads mix explanatory prose with DOM identifiers, version strings and diagnostic output. English-speaking readers can begin with the installation overview and retain exact technical strings when searching repair reports, because they connect a symptom to the relevant application structure.

Issue #373 distinguishes the outer composer root from its inner footer, despite both belonging to the input area. Issue #235 distinguishes a retained launch flag from a listening endpoint. Keep those identifiers and versions intact when translating the surrounding explanation. They help determine whether a report concerns startup, injection or layout, rather than treating every absent theme as the same installation failure.

Codex-Dream-Skin vs CodeFace and browser theme generators

Choose Dream Skin for desktop theme application, investigate CodeFace for another manager interface, and use codexskin.io for artwork exports. Fei-Away documents desktop injection and pack import. In issue #157, sundy-li recommended CodeFace as an open-source GUI theme manager. The supplied codexskin.io page describes data-only artwork exports with instructions and no automatic desktop write. The choice depends on whether you need to apply a theme, investigate another manager or obtain artwork. Fei-Away theme workflow, CodeFace recommendation, generator export description.

Option What the evidence describes Choose it when
Codex-Dream-Skin Desktop injection with saved themes, library application and ZIP import. You want Fei-Away's documented desktop-theme workflow.
CodeFace sundy-li's recommendation for an open-source GUI theme manager. You want to investigate another manager interface.
codexskin.io Browser artwork generation with data-only exports and application instructions. You need artwork before choosing a desktop application method.

A browser preview and a desktop installation serve different purposes. The generator's supplied export description includes artwork, metadata and instructions, leaving application to a separate action. Dream Skin's documented workflow includes a local client and renderer interaction. Buying custom artwork is another separate transaction. Choose according to whether you need artwork, a pack-import workflow or help maintaining usable controls after application.

What the other reviews get wrong

AI Agents Directory labels Codex Dream Skin paid, while the supplied project announcement describes a free, MIT-licensed download. The announcement is project-origin evidence distributed through EIN Presswire. Its download statement should be distinguished from paid customization offers and broader compatibility promises. TopAIHubs also lists the project as free and open-source. Directory pricing label, project announcement, TopAIHubs listing.

UPGPTs categorically says skinning does not affect chat or coding features, while issue #415 reports conversations and the composer disappearing after injection. TopAIHubs' risk-free framing conflicts with the unauthenticated CDP access described by Fei-Away. SourceForge's Windows-only operating-system metadata is incomplete against Fei-Away's documented macOS and Windows downloads. UPGPTs FAQ, missing-content report, SourceForge listing.

The announcement's statement that every native control remains interactive is a dated project claim; later reports describe specific failures. Repository identity matters for licensing too: the separate codex-dream-skin/codex-dream-skin record points to MIT platform files while displaying Apache-2.0 repository metadata. That discrepancy belongs to the separate repository. Fei-Away's supplied README and repository facts identify MIT for the project reviewed here. Separate repository record.

FAQ

Fei-Away's README documents library themes and ZIP import, answering the preset request in issue #5 with a current application route. For troubleshooting, the issue records separate startup, browser handoff and renderer layout: issue #307 reports recovered startup and ZIP import alongside failed one-click handoff, while issue #373 describes incorrect composer mapping after passing checks. Match the symptom and version pair to the relevant question. Preset request, Fei-Away import contract, handoff report.

Are there real installed screenshots showing how Codex-Dream-Skin compares with the README previews?

Issue #22 contains user-posted installed screenshots and complaints that the results differed from README imagery; issue #373 includes contributor screenshots and composer diagnostics. Compare conversation visibility, foreground contrast and input controls alongside the background. User images show what the reporter saw; the accompanying version and diagnostic details connect that result to an installation. A visible conversation and usable composer provide more useful compatibility evidence than wallpaper alone. Installed-result discussion, composer screenshots and diagnostics.

Can I use ready-made skin packs or import themes from GitHub?

Fei-Away's README documents a theme library and ZIP import, while issue #5 requests presets or GitHub importing. Users in that thread describe customization as laborious. For the documented workflow, use a library theme or a ZIP following the pack contract, including required styling and image files. The current README says public installers seed the redistributable Gothic Void Crusade preset. Preset request, Fei-Away import contract.

Why does the skin sometimes fail to start even after Codex restarts?

Issue #235 describes retained debugging flags without a listening endpoint, and #307 discusses startup-validation repairs. A running desktop process therefore answers the launch question alone. Match diagnostic output and application versions to the relevant report, then distinguish process launch, endpoint availability and visible renderer state. Those stages explain how restarting can leave the theme absent. Startup diagnosis.

Why does one-click theme application fail to open the desktop client?

Issue #307 distinguishes browser permission, Windows protocol registration and client-handler errors. qinyogi reported working startup and ZIP import while one-click application still failed. Issue #352 describes a separate cold-start guard repaired in v1.5.14. Match the error stage to the thread before choosing its repair, because both discussions concern handoff but describe different reported mechanisms. Desktop handoff discussion.

Why is only the wallpaper visible while the chat and input box disappear?

Issue #415 attributes disappearing content to a CSS hiding rule after Codex moved a gradient-related attribute onto a content-bearing container. The maintainer reports narrowing the selector in v1.5.19, and users reported local CSS recovery. Restore the stock interface when conversation access is the immediate priority, then compare both application versions with the repair discussion. Missing-content report.

Can a Codex update break the skin again even after upgrading Dream Skin?

Issue #373 records successive compatibility repairs, and #415 describes missing content after a later Codex layout change. A release's changes address particular structures. Record the Codex version and Dream Skin version together, then inspect Home, an existing Task and the composer after updating either application. The version pair identifies the reported environment more precisely than the skin version alone. Update-related failures.

Why does Verify pass when the theme still looks wrong?

Issue #373 records passing checks and installed renderer styling alongside incorrect composer mapping. Styling reached the inner footer instead of the intended outer root. Package acceptance and style installation can succeed while the visible result is wrong. Inspect the composer boundary and conversation area directly after application, using automated status as one part of the result. Passing-check mismatch.

How do I remove a third-party packaged version, and where did it install?

Issue #157 includes a removal question about a shared community executable. Identify the package and its author before choosing removal instructions. Fei-Away's current README points to its platform installation and uninstall guides. Paths and switches from codex-dream-skin/codex-dream-skin belong to that separate project, rather than serving as removal instructions for every executable bearing a similar name. Community packaging discussion.

What we have not tested yet

Our evidence contains no completed supported-desktop installation, theme application or restoration, and no completed hands-on Q&A or screenshot records from our runs. The November image label does not establish actual runtime or operating-system versions. CPU use, memory consumption, latency, long-session readability, productivity and eye-strain effects are outside the measurements. The source-workspace results and attributed user reports form this review's evidence.

Applicability of the separate repository's -RestoreBaseTheme appearance-key restoration switch, -RecoverConfigBackup byte-for-byte configuration-recovery switch, ~/.codex/codex-dream-skin-studio engine path and Application Support state layout to Fei-Away/Codex-Dream-Skin is unverified. Fei-Away's saved-theme directories are not a complete installation inventory. Arbitrary GitHub importing and the community executable's removal route are also unassessed. The current unsigned installers and v1.5.21 have no supported-desktop test in this record; the measured checkout was commit 6fc42df.

Affected-user confirmation is absent for the v1.5.19 upgrade, the specific macOS Codex 26.820.60940 failure with Dream Skin v1.5.16, the issue #244 release repair and the final Windows profile repair. The anonymous CodeFace README endpoint returned 404, so the comparison retains the attributed recommendation. CodeFace and codexskin.io have no side-by-side execution results here. Rendered layout, accessibility, related links, recommendation modules and publication-template behavior remain untested. This correction covers supplied text and evidence, with no new execution or acceptance test.

All four editorial score dimensions remain unassessed. The npm installation result measures a source workspace; reading installation, import and shutdown instructions describes documentation coverage. Named diagnoses and retests show participation, while the sampled regressions describe particular versions. These observations do not supply a completed desktop setup, a documentation-usability assessment, a support-capacity assessment or a long-term reliability assessment from which to assign editorial numbers.

Alternatives

ProjectWhat it isPick it when
CodeFacesundy-li recommended CodeFace as an open-source GUI theme manager in issue #157.Investigate it when you want another manager interface; the supplied comparison rests on an attributed community recommendation.
codexskin.ioA browser artwork generator whose supplied page describes data-only exports and application instructions.Choose it when artwork generation is your immediate task and you want to select the desktop application method separately.

Sources

  1. Fei-Away README, installation, import and safety guidance
  2. Composer compatibility and partial release repair
  3. Content disappears after Codex update
  4. Windows cold-start theme application
  5. Windows startup diagnosis and correction
  6. Separate repository's Windows recovery documentation
  7. Separate repository's macOS documentation
  8. Browser generator export boundary

More dev tools reviews