Autonomy

Autonomy you can dial.

From “ask me before everything” to founder mode — you choose how much TeamX runs alone. Every notch on the dial is metered by the token governor, gated by QA, and fully auditable.

mode 01 / 03 — click a stop, or watch it sweep

Co-pilot

week one

TeamX preps everything — specs, plans, patches — and waits for your nod at every step. Nothing merges without you.

you approve
every spec · every merge · every release
runs alone
triage, context, drafts, briefs
one night in co-pilot
23:50 · inbox triaged · 3 specs drafted
00:40 · spec TMX-104 ready → waiting for you
02:10 · patch prepared · PR drafted, not merged
08:00 · 4 approvals queued in your morning brief

change modes any time — per project, per epic, or per surface

The resource brain

It spends your tokens like its own money.

Autonomy fails the first time it burns a week of quota on the wrong thing. So every run is budgeted, every window is watched, and heavy work waits for the compute it deserves.

22:0000:0002:0004:0006:0008:0010:00
claude max
window · 71% spent
cooldown
TMX-101 · heavy refactorTMX-118 · auth epic
codex pro
TMX-92 · rerouted from Claude
api · byok
competitor scan
morning brief

one night of compute, scheduled to the minute — nothing you paid for goes unused

Window-aware

TeamX knows your 5-hour Claude windows and weekly caps the way a CFO knows payroll dates. Heavy epics launch into fresh windows; nothing big starts on fumes.

Compute-fit scheduling

Every task is sized in tokens before it runs. The 80k-token refactor waits for a full window; the typo fix slots in anywhere. Your roadmap is scheduled against real compute, not vibes.

Fallback routing

A window runs dry mid-epic? Work reroutes to Codex, an API model, or your local Ollama box — context intact — instead of stopping. The organism never idles because one limb is tired.

Zero markup, ever

Your subscriptions, your keys. TeamX cannot profit from your token burn — which is exactly why it’s built to minimize it. Incentives fully aligned.

The 24/7 CTO

It doesn’t just take orders. It pushes back.

At the top of the dial, TeamX behaves like a technical co-founder: challenging weak specs, watching competitors, proposing the roadmap — and briefing you every morning on the company it ran overnight.

morning brief — wed 08:00auto-generated
Shipped overnight — 9 items

bug #142 fixed + reporter replied · epic TMX-92 “CSV export” live · v1.4.1 perf bump · docs + changelog published

Needs your decision — 1

Pricing page experiment: two specs attached. I recommend variant B — smaller blast radius, same hypothesis. Approve one and I’ll build it tonight.

Competitor watch

Rival shipped bulk import yesterday. Our feedback portal has 14 votes for the same thing — proposed epic attached, scoped to 60% of their surface for the 20% users actually use.

Challenged

Your “rebuild settings in new framework” idea: cut. Usage shows 2% of sessions touch it. Wrote a one-day polish spec instead — same outcome, 1/10th the tokens.

Challenges your ideas

Every spec gets a devil’s-advocate pass before a token is spent. Weak scope gets questioned, gold-plating gets cut, risky changes get flagged — like a CTO who isn’t afraid to say “why?”

Watches your market

Scheduled competitor scans — launches, changelogs, pricing moves — distilled into “what this means for us.” When it warrants action, it arrives as a proposed, pre-specced epic.

Proposes the roadmap

It ranks the backlog against real usage, feedback, and strategy — then shows up with “here’s what I’d build next, and why.” You veto or approve. Direction stays yours.

Reports like a CTO

A morning brief and a weekly pulse: what shipped, what’s blocked, what needs a human decision. Your standup is already written when you wake up.

You stay the founder. Every strategic move ships as a proposal — one tap to approve, one to veto.

Guardrails

Trust, but verify everything.

The dial only goes up because the floor never moves. Six guarantees hold at every autonomy level — they’re the reason founder mode is brave, not stupid.

01

Spec-first, always

Agents cannot start unspecced work — the API refuses. The rare bypass is possible, and every bypass is logged for review.

02

Blast radius computed

Before anything merges, TeamX maps what the change touches downstream. Surprises are a failure mode, so they’re engineered out.

03

QA gates on sensitive surfaces

Auth, billing, data deletion — these demand a human signature. The epic stays open until you sign.

04

Escalation, by name

When an agent is uncertain, it doesn’t guess — it escalates to you with the context attached. Uncertainty is a feature, not a crash.

05

Everything attributable

Every action, every commit, every decision carries who did it, when, and why. The audit trail isn’t an add-on — it’s the data model.

06

Instant revoke

Any agent’s tokens die in one tap. The kill switch is always closer than the work.

your quota window is open right now

Right now, your agents are asleep.
Wake them up.

Connect your first agent in two minutes. By tomorrow morning there’s a brief in your inbox about everything that shipped overnight.

free for solo devs · your keys, zero markup · nothing to install in your repo