1. The service
Get Codex Theme provides an unofficial gallery, free Registry downloads, an automated publishing workflow, theme-pack specification, CLI, and compatibility tools for Codex Desktop. Browsing and installation require no account. Google or GitHub sign-in plus exactly one public GitHub or X contributor profile is required for each publishing session.
2. Unofficial status and compatibility
Get Codex Theme is not affiliated with, endorsed by, or sponsored by OpenAI. Codex and related marks belong to their respective owner. Advanced image-based themes use an unofficial local compatibility runtime and may be affected by Codex updates. The CLI never modifies the signed Codex application bundle.
3. Your submissions
You retain ownership of original assets you submit. You grant us a non-exclusive license to validate, sanitize, store, reproduce, display, package, and distribute a successfully validated theme through the Registry under the license stated in its manifest and rights record. You confirm that you have the rights needed to publish every asset, name, logo, and reference.
4. Automated publication and removal
A release is published only when automated identity, package, checksum, rights-record, and server validation succeeds. Failed validation must be corrected and resubmitted. We may later suspend or remove a theme for credible safety, rights, deceptive metadata, broken installation, or policy concerns. Published versions are immutable; updates require a new semantic version. A theme ID remains associated with its original authenticated publisher to prevent namespace takeover.
5. Attribution and links
Publishers select exactly one GitHub or X profile for public contributor credit. The selected username and profile link are displayed on gallery cards and theme pages. GitHub profiles may be linked through Neon Auth. X profile links are supplied by the publisher and are not verified through the X API. The publishing manifest must use the same saved attribution. By using a profile, you confirm that it represents you or an organization you are authorized to publish for. Do not impersonate another creator or organization.
6. Community requests and engagement
Signed-in members may publish and vote on theme requests. A claim identifies a public creator who intends to work on a brief; it does not transfer rights, promise delivery, or create employment. Requests must be original, concise, and free of private contact information, unlawful instructions, deceptive affiliation, or material the requester is not entitled to share.
7. Acceptable use
Do not upload malware, executable payloads, credentials, private data, illegal material, deceptive interface imagery, or assets you lack permission to distribute. Do not automate downloads, likes, votes, requests, or claims; evade rate limits; overload public endpoints; manipulate rankings; impersonate another creator; or interfere with another publisher's namespace. Uploaded executable files are removed from Registry packs.
8. Reports and removal
We may correct, disable, or remove a listing, profile association, request, engagement count, or release in response to a credible copyright, trademark, privacy, safety, impersonation, or abuse report. Submit those concerns through the private report form. False or abusive reports may be rejected and rate-limited.
9. Licenses and downloads
Each theme is governed by the license included in its download. The CLI and public project components are governed by their repository licenses. Creator attribution shown by the site does not replace the theme's license terms. Download, like, and vote counts are approximate abuse-filtered service metrics, not audited business records.
10. Disclaimers and changes
The service and tools are provided on an “as available” basis without warranties to the maximum extent permitted by law. We may update the service or these terms, with material changes reflected by the updated date. See the Privacy Policy, Content Policy, and Takedown Process; use the private report form for rights or removal requests.