Skip to content

Nine laps. One minute. Then the rest.

The open-source Conductor alternative, in 60 seconds.

Foreman is a free, open-source desktop app for macOS and Windows that runs AI coding agents in parallel. Claude Code, Codex, Cursor and OpenCode each work in their own git worktree on their own branch, while you review diffs, answer questions and open pull requests from one window.

  • macOS & Windows
  • Apache-2.0
  • No account
  • v1.2.4
Four Foreman workspaces side by side in Tiles: a failed turn, a finished fix and two questions from AI employees waiting for an answer
The real window Two workspaces side by side in Tiles, each on its own branch.
0:00Start ▸
Start the clock

0:06Lap 1 of 9

How do you run several coding agents at once? One agent. One branch.

Each agent works in its own git worktree, on its own branch. Four agents edit one repository at once, and nobody overwrites anybody.

Try it Tap a hat or a work order, then sign off the lane.

Next lap: Team

Tap a hat or a work order. Each agent gets its own lane: a git worktree on its own branch.

Work orders
  1. 01osaka

    Open lane · waiting for a hat

    fix-login-redirectClaude Code

    +12 −3 · ready for review

  2. 02lisbon

    Open lane · waiting for a hat

    add-rate-limitCodex

    +10 −1 · ready for review

  3. 03kyoto

    Open lane · waiting for a hat

    write-testsCursor

    +48 −0 · ready for review

  4. 04lima

    Open lane · waiting for a hat

    update-docsOpenCode

    +6 −2 · ready for review

4 worktrees open · 4 signed off

Off site? Answer the crew from your phone

Agents sharing a folder: none. Each agent works in its own git worktree.

0:12Lap 2 of 9

Can AI agents work as a team? Hire the crew.

Hire AI employees from 15 job templates: a role in plain words, a hard hat each, access you approve and a memory kept in git.

Try it Hire a role on the left. Remove one with ×.

Next lap: Plans

Open roles 15

Engineering

Design

Product

Data

Writing

Marketing

Customers

Hat rule A hat says who, never state. If a job's colour is taken, the new hire wears the least-worn colour instead.

Slack posts and Linear changes start held for you. Since v1.2.4 an employee pushes and opens draft pull requests on its own; this switch is the one-line rule that holds those too.

Your team 3

  • You

    The person · one of the team

    Approve each plan and each hire, and anything you've asked the team to hold.

  • Priya Lead

    Program manager

    Plans every project, proposes who it needs, reviews each part and accepts the result.

    Starts
    When you @Priya
    Access
    Writes project filesNo shellSlack · held
  • Ravi

    Staff software engineer

    Builds and fixes features, with tests, on its own branch.

    Starts
    When you askWhen assigned in Linear
    Access
    Write · atlasNo shellPush & PR · heldSlack & Linear · held

0:18Lap 3 of 9

What is a Foreman flow? Draw it once. Loop until green.

A flow is a graph of agent steps, with loops that stop on facts like passing checks and gates where you decide. Experimental, off by default.

Try it Press Run it and answer the gate.

Next lap: Tools
Start from a built-in flow

⁠, ⁠, ⁠, ⁠, ⁠.

Tap any underlined part to change it.

Matches the built-in flow fix-until-green.

Ready · 4 rooms · 2 loops · 1 gate

IN · {{task}}OUT · done01implementdeveloper · edits the worktreeTURN · CLAUDE CODE02checksnpm test · tsc · lintCHECKS · NO AGENT03reviewqa-engineer · read-onlyREVIEW · CLAUDE OR CODEX04ship-checkyou · ready to ship?GATE · YOU≤ 4 roundson failed · 45 min≤ 2 roundson findingssent backJOB
IN · {{task}}OUT · done01implementdeveloperTURN · CLAUDE CODE02checksnpm test · lintCHECKS · NO AGENT03reviewqa-engineerREVIEW · CLAUDE OR CODEX04ship-checkyou decideGATE · YOU≤ 4 roundson failed≤ 2 roundson findingssent backJOB
.foreman/flows/fix-until-green.tomlSimplified for this page
# .foreman/flows/fix-until-green.toml · simplified for this page
name = "Fix until green"
description = "Skip the plan, the developer builds, the checks run until green, at most 4 rounds, the QA engineer reviews until clean, and I approve before it ships."

[inputs]
task = "What to build or fix"

[start]
step = "implement"

[steps.implement]
kind = "turn"                  # code steps run on Claude Code
persona = "developer"
loadout = 1
prompt = "{{task}}"

[steps.checks]
kind = "checks"                # the repo's approved check commands, never an agent

[steps.fix]
kind = "turn"
same_tab = "implement"
prompt = "Address what failed or what you were sent back for, and run the checks again."
context = ["checks.results"]

[steps.review]
kind = "review"                # read-only: Claude Code or Codex
persona = "qa-engineer"
                               # its default loadout 3 is Codex
context = ["diff"]

[steps.address]
kind = "turn"
same_tab = "implement"
context = ["review.findings"]

[steps.ship-check]
kind = "gate"                  # you: Continue, Send back or Stop
show = ["diff", "checks.results", "review.findings"]
ask = "Is this ready to ship?"

[edges]
implement  = "checks"
checks     = { passed = "review", failed = "fix" }
fix        = "checks"
review     = { clean = "ship-check", findings = "address" }
address    = "checks"
ship-check = { continued = "done", sent-back = "address", stopped = "done" }

[loops.fix-until-green]
over = ["checks", "fix"]
at_most = { iterations = 4, minutes = 45 }
iteration = "same-tab"         # or "compact-when-full" or "fresh-with-summary"

[loops.review-until-clean]
over = ["review", "address", "checks"]
at_most = { iterations = 2 }

[after]
workspace = "keep"             # keep | archive | delete-unchanged
Project
atlas
Flow
fix-until-green
Drawn by
the assistant
Checked by
you
Revisions
  1. A first drawn

Scale: 1 step = 1 room · persona hats drawn for this page

Site log fix-login-redirect

  1. 00:08developer: moved the redirect after setSession() · +12 −3
  2. 00:45checks: ✕ auth/redirect.test.ts › keeps returnTo after sign-in
  3. 01:22developer (fix, same tab): kept returnTo on the refresh path · +4 −1
  4. 01:59checks: ✓ 214 tests · types · lint
  5. 02:36qa-engineer: clean, no findings
  6. 03:13ship-check: waiting for you · ready to ship?

Illustrative run of the sentence above. In Foreman the Flow tab draws it live and the gate waits in Needs you. Flows are experimental: turn them on in Settings → Experimental → Flows.

Legend

  • A room is a step: a turn, checks, a review, a gate or a PR
  • A loop, with its bound and the fact that sends it round
  • Sent back from your gate, with your note
  • Your gate is a door: nothing passes until you open it
  • The job, walking from room to room on a run

0:24Lap 4 of 9

Which integrations can coding agents use? Load the belt.

GitHub, GitLab, Linear, Slack, Langfuse and MCP. Each connection gets the agent access you choose: nothing, read, or read and write.

Try it Tap a tool to hang it on the belt.

Next lap: Off-site
  1. GitHub
  2. Linear
  3. Slack
  4. Langfuse
  5. MCP
  6. Sandboxes
  7. GitLab

Connections belong to the repository, so every new workspace in atlas starts with this belt.

7 of 7 tools on the belt

0:30Lap 5 of 9

Can coding agents run in a cloud sandbox? Send it off-site.

As an experiment, run a workspace on your own E2B, Daytona, Vercel Sandbox or Docker account. Provider keys never enter the sandbox, and the turn keeps going when you close the laptop.

Try it Pick a container, Create, then close the laptop.

Next lap: Night shift

New workspace · atlas

Workspace

Runs on

Sandbox
E2B
Size
vCPU
Starts from
A fresh clone, set up when it’s made
Sleeps after
20 min idle
Agent sign-in
Claude setup token

Your Claude subscription sign-in stays on this computer. In a sandbox Claude uses a setup token from claude setup-token, or an API key.

On E2B a session ends after 60 minutes. Foreman continues the turn when you’re around; with Foreman closed, the agent stops at the limit and the workspace sleeps.

Remote workspaces run on E2B. Experimental.

This computer

Foreman · atlasZzz

Vault

  • Provider keystays here
  • GitHub tokenstays here
  • Agent sign-instays here
Property line · provider keys stop here
  1. Clone from GitHub The repository comes from its GitHub remote. GitHub’s token goes in as that one command’s environment.
  2. Install the agent host Foreman puts its small agent host in the sandbox, so the agent can run there without your computer.
  3. Set up The install script and the repository’s setup steps run, as they would in a local worktree.
  4. Run The agent takes the turn in the sandbox. Your computer only coordinates.

Session · not started

Turn · waiting to ship

  1. Pick a workspace and a container, then Create. Closing the laptop quits Foreman: remote turns go on in their sandboxes until they finish or reach the session limit, and their chats catch up when you open Foreman again.

This month · no sandbox time yet

0:36Lap 6 of 9

Can Foreman run coding agents on a schedule? Work the night shift.

Schedule a saved prompt hourly, daily, weekly or monthly, in your time zone. Runs use Claude Code, while Foreman runs, with or without a window.

Try it Pin a template, set the time, file the slip.

Next lap: Loadout

The seven templates that ship 7

Saved prompts yours · blanks written out

Blanks fill in order: foreman run fix-a-bug "the login page loops". A scheduled run can't stop to ask, so only templates without {{blanks}} go on a schedule. Repository templates live in.foreman/templates and travel with the code.

Schedule slipNo. 0042

nightly-triage on atlas

Every
in Europe/London
Runs on
Claude Code, a Sonnet by default
Max
30 minutes5 to 480
After
Approved
its text, the repo's setup, checks and MCP servers

Runs every day at 00:30 (Europe/London) · stops after 30 minutes · keeps the workspace

foreman schedules add nightly-triage --repo atlas --every daily --at 00:30 --tz Europe/London

0:42Lap 7 of 9

Which coding agent should do which job? Deal the right crew.

Claude Code builds, Codex reviews read-only, personas set the rules and you hold the gate. Pick a job, get the four-card team.

Try it Pick a job, then Deal a loadout.

Next lap: Phone

The job

Loadout for fix flaky tests

  1. DeveloperClaude CodeAgent · Anthropic

    Writes the fix. Flow steps that change code run on Claude Code, the one agent Foreman runs unattended.

  2. ReviewerCodexAgent · OpenAI

    Reads the diff read-only, inside its own sandbox. A flow’s review steps can run on Codex.

  3. Review personaqa-engineerFlow persona · reviewer

    What the reviewer wears: it finds what breaks, never fixes it, and ends with findings.

  4. At the gateYouThe foreman · one of one

    Quarantine the test, keep the fix, or send it back with a note. Nothing ships before you look.

Plays as the built-in flow flaky-test-triage. Flows are experimental and off by default: Settings → Experimental.

Run them side by side in Foreman, each in its own worktree.

0:48Lap 8 of 9

Can you control Foreman from your phone? Answer from the couch.

Pair a phone with a QR code to answer approvals, steer agents and comment on diffs, live: straight over the same Wi‑Fi, or from anywhere over your own Tailscale network.

Try it Pick an access level, then answer the plan.

Next lap: vs Conductor

ForemanNeeds you · 1

lisbon · Claude Code

Plan ready: rate-limit the login

  1. Add a limiter to /api/login
  2. Answer 429 with Retry-After
  3. Test the sixth try in a minute

Watch can see this plan but can't answer it.

Private · OperateIllustrative

What may this phone do?
Same Wi‑Fi
Straight to your computer.
Away
Over your own Tailscale network. No Foreman relay.
Another computer
The whole app in a browser at /app.

Native iOS and Android apps are on the way.

Today: pair your phone with a QR code and add the phone view to your Home Screen.

0:54Lap 9 of 9

How is Foreman different from Conductor? Open source. Windows too.

Foreman is open source under Apache-2.0 and runs on Windows as well as macOS, while Conductor is a closed-source Mac app. Foreman also drives OpenCode and any ACP agent, and adds flows that loop until checks pass, AI employees and a scriptable command line.

Next lap: the longer version

A dash means not listed on their site

Foreman compared with Conductor and T3 Code
FeatureForemanConductorT3 Code
Open sourceApache-2.0NoMIT
macOSYesYesYes
WindowsYesMac onlyYes
One git worktree per agentYesYesYes
AgentsClaude Code, Codex, Cursor, OpenCode, any ACP agentClaude Code, Codex, CursorClaude Code, Codex and more
Flows that loop until checks pass, with human gatesYes——
AI employees with git-backed memoryYes——
Scheduled automations and auto-fix CIYes——
Your own cloud sandboxes (E2B, Daytona, Vercel, Docker)Experimental——
Scriptable CLI, --json on every commandYes——
Approve from your phoneYes—Yes
No account, no telemetry uploadYes——
From each project's own site as of November 2026. “—” means it isn't listed there, not that it's missing. Spot a mistake? Tell us.

1:00 Time.

What didn't fit in a minute?

Review, approvals, auto-fix, memory, the command line and the privacy model. Here they are, a line each.

Eight modules, nine laps, sixty seconds.

  • +0:05

    Review every change

    Read each change as a diff before you commit, push or open a pull request. Checkpoints let you rewind a workspace to any turn.

  • +0:10

    Approvals that spell it out

    An approval breaks a command down part by part, marks anything that leaves your computer, and says exactly what Always allow adds.

  • +0:15

    Auto-fix CI and auto-review

    Opt in and Foreman sends a failing CI log to your agent within a budget you set, and a read-only reviewer reads each finished diff. Checks can run after every turn, and a chat that hits a usage limit resumes by itself.

  • +0:20

    A memory kept in git

    Every organization remembers in its own private git repository, with a commit for each run, and your code repositories stay clean.

  • +0:25

    A real command line

    Almost everything in the window works from a terminal with the foreman command. Every command takes --json and exit codes are stable, so scripts and CI can rely on them.

  • +0:30

    Local-first. No account.

    Foreman runs on your computer. There is no Foreman account, no cloud service and no telemetry upload. Agents use your own logins and API keys.

Another minute

Get started in a minute

Download the app, point it at a git repository, and give each task its own workspace.

  1. Download Foreman

    Free for macOS (Apple Silicon, signed and notarized) and Windows. You need Git on your PATH.

  2. Add a repo, sign in an agent

    Pick any git repository. Sign in Claude Code, Codex, Cursor or OpenCode in Settings → Agents with your own login or key.

  3. Create workspaces

    One per task, each a fresh worktree on its own branch. Watch them in Tiles, review the diffs, open the PR.

Prefer a terminal? Same thing, one line.
foreman run fix-a-bug "the login page loops after sign-in" --repo atlas --wait

# Start a workspace from a template and wait for the turn. CLI reference

Questions

Questions developers ask

Something missing? Open an issue or read the guide.

What is Foreman?

Foreman is a free, open-source desktop app for macOS and Windows that runs AI coding agents in parallel. Claude Code, Codex, Cursor and OpenCode each work in their own git worktree on their own branch, while you review diffs, answer questions and open pull requests from one window.

Is Foreman free and open source?

Yes. Foreman is free and licensed under Apache-2.0, with the full source on GitHub at github.com/elite-build/foreman. There is no paid tier, no account and no Foreman cloud service.

Which coding agents does Foreman support?

Foreman runs Claude Code, Codex, Cursor and OpenCode, plus any agent that speaks the Agent Client Protocol (ACP). Each agent signs in with your own subscription or API key, set in Settings → Agents.

How do I run multiple Claude Code agents in parallel?

Add a git repository to Foreman and create one workspace per task. Each workspace is a separate git worktree on its own branch, so several Claude Code sessions edit the same repository at once without conflicts. Tiles shows them side by side.

Why does each agent need its own git worktree?

A git worktree is a second checkout of the same repository on a different branch. Giving each agent its own worktree means agents never overwrite each other's files, every change lands on a reviewable branch, and your main checkout stays untouched.

Does my code leave my computer?

Only through the agents you choose. Foreman runs locally with no account and no telemetry upload; your agents talk to their own model providers. In your own workspaces, an approval marks any command that leaves your computer before it runs, and AI employees hold Slack posts and Linear changes for you.

Do coding agents need my approval for every command?

Only if you want them to. Approvals are a setting: with Claude Code tool approvals on (Settings → Account), each command is spelled out part by part before it runs, anything that leaves your computer is marked, and Always allow shows exactly what it adds. Every agent still works in its own worktree, and checkpoints rewind any turn.

Which operating systems does Foreman run on?

Foreman runs on macOS (Apple Silicon, signed and notarized) and Windows. You need Git on your PATH and a login or API key for at least one agent.

Can Foreman run coding agents on a schedule?

Yes. Any saved prompt template can run hourly, daily, weekly or monthly in your time zone, and opt-in auto-fix sends failing CI logs to your agent. Scheduled runs use Claude Code and happen while Foreman is running, which can be without a window or from login.

Can I control Foreman from my phone?

Yes. Pair a phone with a QR code to answer approvals, steer agents, comment on diffs and read terminals, live. On the same Wi-Fi it connects directly, and anywhere else through your own Tailscale network. Native iOS and Android apps are coming soon.

Can coding agents run in a cloud sandbox like E2B?

Yes, as an experiment. A workspace's worktree and agent can run in a sandbox on your own E2B, Daytona, Vercel Sandbox or Docker account, for Claude Code, Codex and OpenCode. Provider keys stay on your computer and never go into the sandbox.

Which integrations does Foreman have?

GitHub (pull requests, merges, CI and reviews), GitLab, Linear, Slack and Langfuse, plus MCP. Each connection has a default per service, each repository can pick its own, and you choose what agents may do with it: nothing, read, or read and write.

How is Foreman different from Conductor?

Foreman is open source under Apache-2.0 and runs on Windows as well as macOS, while Conductor is a closed-source Mac app. Foreman also drives OpenCode and any ACP agent, and adds flows that loop until checks pass, AI employees and a scriptable command line.

How is Foreman different from T3 Code?

Both are open-source GUIs for coding agents. Foreman adds flows (agent graphs that loop until tests pass, with human gates), AI employees with a git-backed memory, a foreman CLI where every command takes --json, phone approvals and remote sandboxes.

Can I script Foreman or use it in CI?

Yes. The foreman command starts workspaces, sends messages, answers approvals, opens and merges pull requests and runs flows. Every command takes --json and exit codes are the same for every command.

Your minute's up. Give us a second: star it.

Foreman has shipped 31 releases since 1.0.0 on 27 October, in the open under Apache-2.0. A star tells us to keep going. A fork is yours to change. A first issue makes you part of the crew.