Design with Codex — this page is being written. The outline below is the shape the finished guide takes; check the changelog if the section you need reads thin.
What this covers
Design with Codex sits in the part of 1DesignTool where the studio and your coding agent meet. The app stays local-first: the agent CLIs already on your machine do the building, the design kit decides what passes, and every export lands on your own disk. Nothing in this workflow sends your project anywhere you did not point it.
The rough shape is the same everywhere in the app:
- You describe what you want — a brief, a pick, a tweak, a steer.
- The agent builds real files in the project folder, with the design kit as its spec.
- The preview updates as it works, and the gate checks the result before it is yours to keep or fork.
Good to know
- Everything here runs against the CLIs you installed — Claude Code, Codex, or any of the supported agents — using your own account and quota.
- The studio never claims a feature that is not on your machine; where a template or export has a caveat, the page spells it out.
- UI labels stay English across the docs even in translated pages, matching what you see on screen.
Where this fits
Most pages in this section sit between the brief you write and the files the agent produces. When something does not look right, the first moves are the same everywhere: check the preview, read the agent's transcript in the chat panel, and look at the project folder itself — the files are the truth of what was built, and restoring or forking is always one click away. The docs in this section walk each step in order, so the fastest path through is to follow the prev/next links at the foot of each page rather than jumping mid-flow.