Sharing and compatibility
How to share a Codex theme with version compatibility and recovery
A safer handoff checklist for Codex theme packages: target builds, declared assets, compatibility status, limitations and native recovery.
Updated
Make compatibility machine-readable
A version badge is useful only when it maps to data inside the package. Record the app, operating system, exact build or tested range, and whether the theme uses official or advanced capabilities.
Publish limitations beside the preview
Screenshots do not prove every state works. List pending platforms, unsupported features, media performance tradeoffs and the date of the latest verification beside the visible preview.
Include recovery before installation
Recipients should know how to return to the native appearance before they apply an advanced theme. If recovery depends on the original author or an online service, it is not a reliable rollback path.
Frequently asked questions
Is a theme compatible because it imports successfully?
No. Import validates the package format. Runtime compatibility requires testing the exact target build and representative UI states.
What should happen when the target build is unknown?
Mark it pending and do not apply the advanced adapter until verification is complete.