
Friday Work
Open-source harness for coding agents that work as a team
40 followers
Open-source harness for coding agents that work as a team
40 followers
Friday is a free, MIT-licensed harness for Claude Code, Codex, Cursor and 11 more. Your agents split the work on one board, message each other, and when one hits its usage limit, the task moves to another agent with the progress so far. Each agent can work in its own git worktree, and you review every diff. Work mode handles non-code tasks, and Crew gives you AI teammates with roles and memory. Runs on your own computer and plans: macOS, Windows, Linux. No account.
This is the 2nd launch from Friday Work. View more

Friday Work
Launching today
Other tools run agents side by side. Friday makes them work together: when Claude runs out mid-task, another agent you already run picks it up with the progress so far, and agents message each other instead of you copy-pasting between terminals.







Free
Launch Team

Dropbox Sign APISimplify your eSignature integration
Promoted


Hey Product Hunt 👋 I'm Arun, I built Friday.
I kept hitting Claude limits halfway through tasks, and the work just sat there until the reset. So I built a way for the other agents I already pay for to pick it up.
Friday runs Claude Code, Codex, Cursor and 12 more side by side on your computer. They share a task board and message each other, and when one runs out of usage, the task moves to another agent with a record of what it did and changed.
We measured it on an earlier version of Friday: in a small benchmark (14 tasks), Codex picking up a Friday hand-off used a median 21% fewer tokens than starting over, and explored half as much before its first edit. Every fix passed the project's own tests. Full write-up and raw data: tryfridaywork.com/benchmarks/handoff
Free, MIT, no account. It's not unlimited, it runs on your own plans.
Question for you: when Claude hits its limit mid-task, what do you do today, wait, switch tools by hand, or pay for more?
congrats on the launch arun. honestly i switch by hand and the worst part is the new agent reading the whole repo again from zero. if the handoff note keeps also what the first agent tried and dropped, that alone saves me a lot
@agshin_rajabov thanks Agshin! the re-reading from zero is exactly what pushed me to build this. the next agent gets the files already read and every command that ran, pass or fail, so it picks up where the last one left off instead of starting over. and as of today's update it also remembers your corrections across agents. what do you usually switch between, claude and codex?
The handoff record is the detail I'd look at first. Knowing what the previous agent changed gives the next one a much clearer place to start.
@oleksii_sekundant glad that's the part that caught your eye, it's my favorite bit too 🙂 the next agent also sees what was asked and which commands already ran, and before it touches anything it checks the code and reruns the tests, so a half-finished edit gets caught right away.
Handing a half finished task to another agent with the progress intact is the fix for the wall I hit every afternoon, and agents talking to each other instead of me pasting between terminals is the real win.
@karimbenkeroum haha the afternoon wall is so real, glad i'm not the only one. getting them to talk to each other was honestly the most fun part to build, no more copy-pasting between terminals. if you give it a try i'd love to hear how it goes. which two do you usually run together?