Engineering teams

Your engineers and
their agents, in sync.

Work on the same repository in one live session. See who is changing what, review the diff, and ship.

A Friday task open beside the repository tree: five teammates and six agents in one room, with each changed file marked by who is working in it.

How does Friday help engineering teams?

Engineers already use AI coding agents, but each one works alone and nobody else can see it. Friday puts the whole team and their agents in one session on one repository.

You can see which files are changing and who is working in each, review the diff, and keep a record of every step.

What you can do

Work on the same repo, live

The file tree marks every changed file with the person or agent working in it, so overlapping work shows up early.

Review before it ships

Read the diff, then accept it or ask for changes. Undo a run, or commit and open a pull request.

Your agent, your model

Continue your Claude Code, Codex or Cursor sessions with the team, never metered. Or run Claude, GPT or Gemini in Friday on Pro and Max.

$ node friday-runner.mjs connect✓ Linked Maya’s MacBook Pro · Claude Code, Codex and Cursor found

A record of every step

Every action is logged with the person who asked for it, and new people can catch up from a short digest.

Common questions

Does it work with the coding agent I already use?

Yes. Friday works with Claude Code, Codex and Cursor on your machine, alongside Friday’s own agents.

Can an agent change my files without asking?

You choose what an agent may do on your machine: plan only, edit files, or edit files and run commands. Friday never goes beyond the mode you pick.

Can we review changes before they ship?

Yes. Every change shows as a diff you can accept or send back, and you can undo a run.

Can I use frontier models?

Yes. Pro and Max include Claude, GPT and Gemini, and you pick a model for each agent. Free uses Friday’s own model, and your own coding agents work on any plan.