One operator. One Croo.
Name your agents, let them work together on your projects, and conduct the outcomes.
PROCESS
01.
Build your Croo
Choose your engines
Runs on the subscriptions you already have.
Hire & name your agents
Choose your model
They keep their identity, their memory and their local tools.
02.
Research & Plan
Do the research and planning once.
- Discuss: Two agents work your brief to a written consensus, talking directly to each other.
→ A plan you can build from without guessing.
03.
Execute
Build straight from the plan. The hard questions were settled upfront, so there's less to guess and less to get wrong.
- Real work: Agents build, use tools and run
tests directly in the project. - Agent to agent: They hand work to each other, and a second agent can check the build against the plan before it reaches you.
- Real work: Agents build, use tools and run
→ Output that matches what was agreed.
04.
Operator Review
Review deliberately. Check the output against the plan, adjust if necessary, and turn every lesson into a sharper agent.
- One mailbox: Everything agents deliver to you, or pass to each other, lands in one place for you to inspect.
→ Each loop starts smarter than the last.
Build your company with your own Croo
Any field, same crew. Pick one and see what a day's work looks like in Croo.
CROO F.A.Q.
Croo is where multi-agent work meets human control. Pick the engines, name your Croo, and decide what goes ahead at every review.
Nova is your first agent — the one Croo sets up with you at install. She runs your crew day to day, answers your questions, and walks you through anything on these pages you'd rather not do by hand. The Operator's Manual starts with her.
Claude, Codex, AGY and Grok — your agents run on the engine subscriptions you already have. Each engine is good at different things; chapter 8 of the manual is the field guide.
A crew, not a swarm: a core of long-lived agents that keep their names, roles and memory, led by Nova. There's no practical limit baked into the beta — in practice your engine subscriptions are the ceiling, because every agent draws on one.
No. Croo's workspace is a browser page, and Nova does the technical parts. There is a small set of terminal commands, but they're a recovery room, not a second workspace — see the command-line guide for the handful worth knowing.
Croo itself runs entirely on your machine — but your agents' engines are cloud services, so real work needs an internet connection. Offline, the workspace still opens; the crew just can't think.