01Plan
Drop in a task doc. The planner splits it into tasks per repo and orders them in waves.
Octopus AI turns task docs into reviewed code across every repo your team owns. Sign in, connect Git and your AI provider, and let the agents work — nothing is pushed until you approve it.
Watch waves of agents land work across your repos in real time. When something needs a human, it waits — in amber — for you.

The agents do the heavy lifting. You stay in the loop at the two moments that matter.
01Drop in a task doc. The planner splits it into tasks per repo and orders them in waves.
02Parallel agents work in isolated worktrees — one task, one branch, no collisions.
Every change is tested and reviewed, with evidence you can open and read.
04 · gateRepairs and pushes stop at a gate. Nothing leaves without your approval.
05Approved work lands on your branches, with a clean audit trail behind it.
Everything happens in the browser. Most teams start their first mission in under ten minutes.

Agents move fast, but they never move without you. Every rule below is enforced on the server — not left to a prompt.
QA repairs and final pushes both wait for an explicit approval. Always.
Keys, tokens and auth headers are scrubbed from every log, diff and screen.
Agents can only touch the repos and paths a project allows. Nothing else is visible.
Every task gets its own branch and worktree, so parallel work never collides.
Force-push, history rewrites and protected-branch pushes are refused outright.
Owners, admins and members — each sees and approves only what they should.
Group repos into projects, invite people into departments and teams, and decide exactly who can start missions and who approves pushes. Agencies can run each client as its own project.
Every push approved by a human.
No. Sign in, create your organisation, add projects, connect Git and an AI provider. Octopus AI runs the agents for you.
Claude Code and Codex, with Gemini available as a second provider for an organisation. Agents only start once a provider proves it can actually edit files — we check with a real request.
Never. Every QA-derived repair and every final push waits for a human approval. Force-push, history rewrites and pushes to protected branches are always refused.
GitHub is connected in one click. Each project picks the repositories it may touch; agents cannot see anything else.
Provider keys and Git tokens are encrypted on the server and never reach a browser. Keys, tokens and auth headers are redacted from every log, diff and screen.
Yes. Give each client its own project — repos, knowledge agents and mission history stay separate, and roles control who can reach what.
Bring your repos and your AI provider. Octopus AI brings the arms.