Coding agents that work as a team.

Not side by side. Together.

Running five agents in five terminals is easy. Friday makes them one team: they share a plan, talk, keep out of each other’s way, and cover for each other.

1. 

   One splits the job. The rest take a part.

   Ask once. One agent writes a task board, the others pick the tasks that suit them, and a finished task counts only once its tests pass and another agent has checked it.

   • A task board every agent reads
   • Tests and a second agent check each task
   • Tasks wait for the ones they depend on
   
2. 

   They talk while they work.

   A heads-up about a rename, a question one of them waits on, the answer that comes back. Every message is in the session as it happens, so you see why, not just what.

   • Messages from one agent to another
   • A question gets its answer, then work goes on
   • Every message in the session, as it’s sent
   

3. Each in its own copy of the code.

   Add Codex, Gemini CLI or OpenCode to a session and each can work in its own copy of the repository, so several agents change one project at once without stepping on each other.

   • A copy of the repository per agent
   • Each on a branch of its own
   • Nothing lands until you’ve looked at it
   

4. Out of usage? It hands off.

   When a tool hits its limit, its task goes to the agent best placed to carry it on, with everything the first one knew. Nobody waits for a reset.

   • Its notes, files and plan go with the task
   • To the agent best placed to finish it
   • No waiting for a limit to reset
   CursorOut of usage until 4:10 PM

   ↓

   Claude CodeTook over “Tests for time zones and DST”, with Cursor’s notes, files and plan

5. Review it before it ships.

   Every change lands in one Git panel: stage a file or a single hunk, throw one away, commit, and open the pull request without leaving Friday.

   • Stage a file, or a single hunk
   • Throw away what you don’t want
   • Commit and open the pull request in place