AGENT TEAMS FOR THE SDLC

An AI dev team that asks before it acts.

Squadron runs a team of agents — Architect, Acceptance, Developer — against your repo and opens a pull request. Every phase waits for your approval. Every risky action becomes a card you can allow or deny. Your API key, your code: nothing stored on our side.

Start a run on your repo Or join the waitlist

Free during the beta. You bring your own Anthropic key and pay them directly — a run costs about $0.40 in tokens.

run a1f3c2 · payment-retry-logic

attended

Architect

1m48sapproved

Acceptance Criteria

54sapproved

Developerrunning

4m12s· 2/3 tasks

Pull Request

An agent needs approval for one action

Developer · task-2 · destructive · rule /migrate reset/

Bash: npx prisma migrate reset --force

Allow onceAlways allow Bash:prismaDeny

▍write src/jobs/retry.ts · +64 −0 · auto-accepted

A live run: the Developer paused on a destructive command and is waiting for you.

HOW IT WORKS

From an idea to a reviewed PR, in three moves.

Connect a repo

Sign in with GitHub and pick a repository. Squadron installs as a GitHub App — access is scoped to what you grant and revocable any time.

Bring your own key

Paste your Anthropic API key and pick a model per role. The key lives in your browser, rides TLS into the run’s VM, and dies with it.

Approve, steer, merge

Phases stream live. You approve each gate, steer when needed, and the team opens a pull request on your repo — notes included.

WHY SQUADRON

Autonomy is table stakes. Control is the feature.

Every agent product promises to work without you. Squadron is built for the moments it shouldn’t.

destructive · rule /rm -rf/

Bash: rm -rf migrations/

Allow onceDeny

Permission cards

Destructive or sensitive calls pause the agent and escalate to you — allow once, allow the pattern, or deny. Unattended runs fail closed.

prefer the retry queue in lib/jobs — don’t touch billing

picked up by Developer · turn 7

Steer mid-run

Drop a note into a running phase and the agent folds it in mid-flight. No restart, no lost context, no re-prompting from zero.

### Agent notes — Developer· Chose idempotent retry keys over table locks
· Backoff caps at 60s — verify against the SLA
· Start review at RetryQueue.claim()

Agent Notes in the PR

Every PR ships with the team’s working notes: decisions, tradeoffs, where to start. You review the reasoning, not just the diff.

ZERO DATA AT REST

Nothing of yours is stored. By architecture, not by policy.

One run = one ephemeral microVM, with your key in its environment and an egress allowlist of exactly two hosts: Anthropic and GitHub. When the run ends, the VM and its disk are destroyed. The only durable output is the pull request on your repo.

DATAWHERE IT LIVESNEVER

Your Anthropic keyBrowser → TLS → the run VM’s env — dies with itOur DB, disk, or logs

Your codeCloned inside the run’s microVM, ephemeral diskServer volumes or object storage

Run outputA pull request on your GitHubServer-side artifacts

Your sessionStateless signed cookieA session table

Point it at a repo and read the PR.

Sign in with GitHub, bring your own Anthropic key, and approve each phase. Free during the beta — about $0.40 of your own tokens per run.

Start a run on your repo

BYOKephemeral VMsPR on your repo

Not ready to run one? Leave your email and we’ll tell you when things change.