Use Claude Code, Codex and Cursor together
You can run Claude Code, Codex and Cursor on the same task by putting them in one shared session. Each works in its own lane, your team sees all three, and you pick the right agent for each job.
Why use more than one coding agent?
Teams often end up with two or three, split by the kind of work. A common split is Cursor for everyday work in the editor, Claude Code for large changes that need the whole codebase in mind, and Codex for well-defined tasks that come back as a pull request. Your own mix may differ.
What goes wrong when you do?
- Each agent lives in its own window, so nobody else can see what it is doing.
- Two agents edit the same file.
- Context is lost every time you switch tools.
How do you run them together in Friday?
- Friday links your machine for you and finds Claude Code, Codex and Cursor.
- Add the agents you want to the session.
- Give each its own lane and a clear job.
- Watch the file tree for overlapping changes.
- Hand work from one agent to the next. Handoffs between agents are on Pro and Max.
The agents run on your machine and your own accounts. Friday never meters them.
What makes it work well?
- Give each agent different files to work on.
- Name lanes by job, such as “tests” or “endpoints”, not by model.
- Ask one agent to review another’s diff.
- Keep one person as the driver of each agent.
Common questions
Do I need a subscription for each agent?
Each one runs under your own account with its provider. Friday does not meter them.
Can I add Friday’s own agent too?
Yes. You can mix Friday’s agents, your own custom agents and your coding agents in one session.
How many agents can run at once?
Free allows 1 agent per session, Pro allows 6, and Max allows 10.