FOR BUILDERS

Hire the
whole team.
Two commands.

27 specialists. 162 skills. Plug into Claude Code, orchestrate with Apex, budget and scope with flags you already know.

Get started How it works

Install . two commands

$ claude plugin marketplace add tonone-ai/tonone

$ claude plugin install tonone@tonone-ai

MIT.27 AGENTS.162 SKILLS

~/project . tonone

$ claude plugin marketplace add tonone-ai/tonone

Resolving marketplace . 162 skills indexed

Installing tonone@latest

depends on: claude-code

$ claude plugin install tonone@tonone-ai

-> 27 agents added to your session

-> roster: apex, spine, prism, form, pitch and 22 more

ready . run apex plan to scope your first task

$

0

AGENTS SHIPPED

0

SKILLS INDEXED

0

COMMANDS TO INSTALL

MIT

OPEN SOURCE

01 / THE ROSTER

Specialists, not chatbots.

Each agent does one thing well and hands off to the next. Apex is the lead, everyone else reports up. Browse the roster, or let Apex pick.

ENGINEERING LEAD

The lead who decides what to build, who builds it, and how deep to go.

Cloud infrastructure, done right the first time. No console clicks.

Automated deployments and pipelines that get out of your way.

APIs and services built for production, not tutorials.

Database schemas and data pipelines that scale without surprises.

Security review and hardening, before attackers do it for you.

OBSERVABILITY + RELIABILITY

Know when something's wrong before your customers do.

02 / HOW IT WORKS

One install. Then you just talk.

Tonone plugs into Claude Code. Apex handles orchestration. You describe the outcome.

01

Install

Drop tonone into Claude Code. Pick your first agent. For 90% of teams that's apex.

02

Describe

Plain English. "Ship the onboarding flow by Friday." Apex scopes, routes, hands off, keeps budget.

03

Review

You get a PR, release notes, and a reviewed diff. Merge it, or send it back with notes. Nothing auto-deploys.

03 / WHAT YOU GET

Boring on purpose.
Built to last.

No theatrics, no demo-mode tricks. The things you'd want in a real teammate.

01 / TERMINAL

Runs where you work

CLI-first. No dashboard to babysit. Pipes into the tools you already run.

02 / HANDOFF

Agents that relay

Scout maps. Apex scopes. Review reads. Ship ships. Each hands off clean.

03 / BUDGET

Token caps, scoped depth

Cap tokens per agent per task. Depth 0 to 5 controls how far they wander.

04 / REVERSIBLE

PRs, not pushes

Every change is a pull request. Nothing merges without your ok.

05 / SKILLS

162 composable skills

Every agent is a bundle of skills. Swap, extend, or write your own.

06 / HOOKS

Plug into your stack

GitHub, Linear, Slack, Vercel. Wire events in, trigger agents out.

"Two commands. Full team shipped by lunch."

EARLY USER . SERIES B CTO

05 / FAQ

The questions
everyone asks.

Short answers. If we're hiding something, tell us.

Do I need to know how to code?+

No for Tonone. Yes eventually. Tonone writes code your engineer can read. If you don't have one yet, that's fine. The PR is the deliverable, and you can hand it to any contractor later.

How is this different from Cursor or Copilot?+

Cursor and Copilot help one developer write code faster. Tonone runs a team. Apex delegates, Review reviews, Ship ships. You describe the outcome, the roster handles the middle.

What if an agent does something dumb?+

It opens a PR. Nothing auto-deploys. Depth caps stop it from touching files outside its scope. Budget caps stop it from burning tokens. You always have the last click.

Can I self-host?+

Yes on Enterprise. The runtime is a single binary. Agents and skills are config. We don't need to see your code.

What models does it use?+

Claude by default. You can route specific agents to specific models. Warden on Claude Opus, Drafter on Haiku, etc. Bring your own keys.

Two commands. Monday morning.

Install tonone. Describe the outcome. Merge the PR. That's the whole flow.

Get started Read the docs