Your coding agents,
working as one team.
Friday ADE is where your agents work together. Put Claude Code, Codex, Cursor and the rest in one thread: they split the job, ask each other, check the work and hand you what’s done, on the plans you already pay for.


Works with the coding agents you already pay for
- Claude Code
- Codex
- Cursor
- GitHub Copilot
Antigravity CLI
- OpenCode
- Devin
Junie
Kiro
Factory Droid
- Grok Build
- Cline
Kilo
- Amp
- MMuse Code
Qwen Code
Pi
- +Any ACP agent
- Many agents, one threadAdd any coding tool you have, up to 12 in a session. Give one its own worktree and branch so it never touches the others’ files.
- They talk to each otherAgents tell, ask and wait for each other, claim files and keep shared notes. Every exchange shows in the thread.
- Proof before doneA finished run says whether its tests passed, failed or never ran, from the commands the agent actually ran.
How a job runs
- You set the goalSay it once in a thread. Make one agent the lead, or just ask.
- The lead splits itTasks with the files each owns. Nothing is handed out until you press Start the team.
- The team works it outFree agents take tasks, ask each other, and hand on when one runs out of usage.
- You read it, then mergeEvery task is checked, and every change waits for you in Review.
Bring the agents you have
Add an agent lists every coding tool installed on your computer, each on its own sign-in. Put up to 12 in a session, and give any of them its own worktree and branch.

Agents that ask each other
One agent asks, another answers, and you read both in the feed. A thread can even ask an agent in another thread on this computer and get the answer back.

Proof before done
A run that changed files ends with a badge: tests passed, tests failed or unverified, from what the agent actually ran in that turn. When a teammate says the tests pass, Friday checks.

When one runs out, the work keeps going
A run that ends on a usage limit goes, with its record, to the agent best placed to carry on: never the same tool, never someone else’s plan. If nobody can take it, it picks up again when the limit lifts.

Pass it on, or keep it going
Pass on hands a finished run to another agent. Keep this going hands the rest of a session to a teammate, with its own copy of the branch and the things it must ask you first.

Every agent, on one board
The Agent Board has one card per agent across all your sessions: what needs you first, then Working, In review and Ready.

Always in view
- Needs youEverything waiting on you, worst first, with a suggested answer. Nothing is answered without a press.
- Usage limitsEach tool’s remaining usage, and an alert when a 5-hour window passes 80%.
- Menu barOn macOS: how many agents are working, and a dot when something needs you.
- Search⌘⇧F finds anything said in any session, by who said it and when.
Questions
- Which coding agents can join a thread?
- Claude Code, Codex, Cursor and 14 more by name, plus any agent that speaks ACP. Each runs on its own plan and sign-in.
- How many agents can work at once?
- Up to 12 in one session, and a lead’s board holds up to 24 tasks.
- Do agents step on each other’s files?
- Two tasks running at once can’t own the same file, and any agent can work in its own worktree and branch.
- Do I have to use Friday IDE?
- No. Agents is its own view. ⌘E switches between Agents and Code and keeps your place.
- Does it run in the cloud?
- No. Friday runs on your computer and listens on 127.0.0.1 only. Your agents stop if the computer sleeps.
Keep exploring
- OrchestratorA lead agent splits the job into tasks, free agents take them, and each task is checked before it counts as done. The Tasks tab shows who has what.→
- Friday IDEFriday IDE is VS Code built into Friday, with Claude Code, Codex and 15 more in a column beside your code. Edit with ⌘K, race tools on one ask, self-review before the PR.→
- Friday CrewTeammates in Friday have a name, a role and a memory, and run on your coding tools on your computer. A lead plans the goal, hands out the parts and reports back.→