Ask Codex for five admin screen redesigns
A developer used Codex CLI to create five alternative admin-screen designs and then chose the one they preferred.
- What they did
- The poster said Codex CLI felt calmer than some of the other tools they were using for interface work and refactors. In this case, they told it to rethink an admin feature and return five separate design directions. Codex moved through the task in small steps, stayed close to the instructions, and waited to offer follow-up ideas until it had finished.
- How it went
- They said they liked every version Codex produced. They also said it usually avoided repetitive loops and often got the edit right without needing a second pass. The discussion did not include screenshots, implementation details, or any measured effect on the product.
- Tips
- If you want side-by-side comparisons, ask for clearly distinct versions and make the agent pause before any irreversible action. This account refers to Codex CLI, not the browser-based version.
Try it yourself with Codex
In [repo path], rework the [admin feature name] interface into five clearly different design options. Save each option in [folder] as a separate branch, file, or mockup, and add a short note explaining the tradeoffs. Leave the current version untouched. Before you do anything that would overwrite, delete, send, submit, or merge work, stop and ask for my approval.
Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.
Get 3 agent uses like this every morning
With the day's top AI news. Free, and one click to unsubscribe.
Related agent uses
Use a coding agent to fix a Slack-reported bug
A Codex agent handled a Slack issue on its own, and an ops agent later confirmed the fix in the same thread.
Create and launch a BaZi reading agent
A developer used coding agents to build a BaZi reader that calculates charts, writes interpretations, and handles language detection and USDT payments.
Contain agent runs and clear old temp files
A developer limited each coding run to a separate cgroup and added a recurring cleanup for forgotten temp files.
Use a long-running agent to chase a stubborn bug
A developer let Codex work overnight against a repeatable test, using debug prints and hypotheses to track down an unexplained bug.
Move builds and tests to a remote Windows VM
A developer had Codex run builds and tests over SSH on WSL in remote Windows VMs instead of using their Mac laptop.
Move Claude Code skills into Codex
Charlie Hills used Claude Code and Codex to migrate 201 skills in an afternoon, then checked which parts worked in both tools and which still needed fixes.