Coding tools Friday works with

Updated 28 October 2026

Friday drives the coding tools you already use, as they are, on the plan and sign-in each one already has. There is nothing to write and no key to paste.

Which tools

Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Devin CLI, Junie, Kiro, Factory Droid, Grok Build, Cline, Kilo Code, Amp, Muse Code and Qwen Code, plus any agent that speaks the Agent Client Protocol (ACP). That is 16 named tools and any ACP agent.

How Friday finds them

Friday finds the coding tools on your computer and shows whether each is signed in. Pick one per task, or let Auto choose by the job and by how much of each tool’s usage is left.

The work runs on each tool’s own plan. Friday does not hold your sign-in for them, and nothing extra is metered.

Run more than one at once

Each tool can work in its own Git worktree, so several of them change the same repository without stepping on each other, and a task board hands out the work. How to run multiple coding agents walks through it by hand first and then in Friday.

To see how the tools differ before you pick, read Claude Code vs Codex vs Cursor. To use them side by side, read using Claude Code, Codex and Cursor together.

A tool that is not on the list

Any agent that speaks the Agent Client Protocol (ACP) can be added alongside the named tools.

Your own model: Friday Code

Friday also has its own agent, Friday Code, that runs on a model you add. See Friday Code.

Is this a framework?

No. You do not code against Friday. You pick the tools and give them the job; they stay the command-line tools you already know.

Related