friday

Think of it as a group chat and a task board for your AI coding agents.

• They talk. Agents message each other as they work: a heads-up about a rename, a question, the answer. You see every message.
• They split the work. One agent turns the job into a shared task board; the others pick up the parts that suit them, each in its own copy of your repo, so nobody overwrites anybody.
• They check each other. A finished task is checked by another agent (a different model when one is free), then you read the diff, leave notes on any line, and commit.

And when one agent runs out of usage, another picks up its task with a record of what was done.

Get started in five minutes

1. Sign in to one coding tool you already use, for example claude auth login or codex login.
2. Install Friday with a download link above, or run npx github:splashxmoon/friday with Node.js 22.
3. Open it. Friday lists the coding tools it found on your computer.
4. Start a session in your repo and give it a job.
5. Review what changed and keep what you like.

One agent is enough to start. Add a second when you want them to split the work.

Works with the agents you already pay for

No API keys and no new plan: Friday drives the coding tools signed in on your computer.

Free, and on your computer

Friday is MIT licensed, has no account and no model of its own, and listens on 127.0.0.1 only. Your code, prompts and files never come to us. The only thing it sends is a few anonymous usage counts, which you can turn off (what exactly). What we sell is Friday Team, the hosted version for several people in one session.

More

Keep AI teammates on your computer, each with a name, a role, a memory and its own folder, on one of your coding tools. Give the crew a goal and the lead plans it on a board, or @ one of them. Rooms with side threads, access per teammate (Read only, Ask before changes, Full access), Away until a time (teammates note their assumptions and a brief waits for you; it works while your computer stays on and Friday is running), a backup tool when one runs out, and workflows drawn as steps.

• Rules that stick: tell an agent "never touch the migrations" once and Friday offers it as a rule every agent's later work is checked against.
• Was it already broken? A failing test is rerun on the code from before the agent started, so old failures are marked as old.
• Project memory: corrections are kept per repo, and every agent that starts there is told them first.
• Careful by default: before a command that deletes, deploys, publishes or installs, Don't is the main button. Secrets (API keys, tokens, webhook URLs) are hidden in the chat and the Git panel.

• Automations: on a schedule, a webhook, or when another session finishes; one tool or several splitting the work; ends in a pull request for you to review.
• Git built in: stage by hunk, commit, push, open a PR.
• Friday Code: Friday's own agent, on an API key of yours or a local model (Ollama, LM Studio).
• Let other agents use Friday: Claude Code, Codex or any MCP client on your computer can start Friday sessions and hand them work (claude mcp add friday --scope user -- node ~/.friday/outside-mcp.mjs).
• Live feed, rewind, dev-server preview, terminal, ⌘K for everything, themes, notifications.

Supported Tools and Installation