Split UI and backend across desktop agents
A developer runs Codex desktop for backend and architecture while Claude Code desktop handles UI and Figma-to-code via MCP.
- Agent or tool
- Codex
- Topic
- Software Development
- Reported on
- Blog
- Added
- 2026-10-15
Why it matters
Coding agents are moving from autocomplete to doing whole tasks: reading a codebase, making a plan and changing many files. This case is a concrete example of where that works in practice. It is one of 106 sightings filed under Software Development on Agent Sightings (number 87 by interest), and one of 32 involving Codex.
How you could try it
Here is a reusable prompt, written by us in our own words, that captures the task. Paste it into Codex or any similar agent and adjust the details to your situation.
Backend agent: design the API and data model for this feature. Frontend agent: implement the UI from the Figma MCP once the API contract is in api.md. Do not share a working tree.
The prompt breaks down into 3 steps you can check as the agent works:
- Backend agent: design the API and data model for this feature.
- Frontend agent: implement the UI from the Figma MCP once the API contract is in api.md.
- Do not share a working tree.
Tip: Work on a fresh branch, ask for a plan before edits, and review the diff and test results before merging.
Source
Read the original first-hand account on Blog: https://dev.to/taruntomar122/my-actual-ai-coding-setup-in-2026-and-how-i-decide…. Our summary is a paraphrase; details are in the source.