Codex Studio is moving toward a polished open-source preview while staying local-first, Codex-first, and library-backed.
- Make first run easier to understand and recover.
- Finish the catalog-first transition for generated assets.
- Improve diagnostics for jobs, storage, providers, and Codex session readiness.
- Keep the desktop path credible without making packaging the center of the project.
- Prepare a small, presentable release candidate.
- Local assets, logs, transcripts, and SQLite state live in a Studio Library outside the repo.
- The main flow runs through
codex app-serverand does not requireOPENAI_API_KEY. - Jobs, events, transcripts, and catalog entries are traceable.
- Generation Tasks and Generation Providers are separate concepts.
- Recipe Modules and Style Preset Manifests are becoming the durable authoring surface.
| Phase | Goal | Expected result |
|---|---|---|
| 0 | Stabilize the current shell | Clearer navigation and global state |
| 1 | Finish catalog-first behavior | UI aligned around SQLite and Image Catalog truth |
| 2 | Improve operations | Common failures produce actionable diagnostics |
| 3 | Harden setup and portability | Smoother Windows/macOS/Linux development setup |
| 4 | Release candidate | Public repo is clear, safe, and reproducible |
- Improve onboarding and error messages.
- Strengthen job recovery and detail views.
- Reduce orchestration debt in shell code.
- Keep validation focused during iteration and complete at closeout.
- Keep public docs short, current, and easy to scan.
- Fresh checkout can run
bun run studio:init. -
bun run devstarts UI and backend. -
/api/healthreports local backend status. - UI shows useful readiness state when Codex auth is missing.
- Public docs, troubleshooting, and contributing notes agree with current scripts.
- No local DBs, logs, transcripts, secrets, or Studio Library assets are committed by mistake.
- Turning Codex Studio into a hosted SaaS.
- Making API keys mandatory for the default Codex flow.
- Publishing it as a reusable npm library.