Give your business a team that ships while you sleep.
Named agent roles run as supervised workers against your data — pursuing durable goals within a budget. Not a chat box: they move deals, score candidates, draft docs, and close tasks.
One loop. Five roles.
The whole team runs one loop. A task rides it — defined, claimed, worked, handed off — and signed off by a different agent than the one that did it. Watch them check in.
On the job
Planner breaks the goal into tasks; Triager routes #1042 to the queue.
Evidence, not vibes
A shipper hands off with what it changed and how it checked — the reviewer audits the proof, not a promise.
Hard-enforced
The gate lives at the data layer. A self-verify is refused, not discouraged — the rule cannot be skipped.
Rejections bounce back
Fail review and the task returns to in progress with notes. The loop runs again until the work is right.
It scales on one machine.
An orchestrator allocates lanes across your goals, a manager fans shippers and verifiers across them, and each worker leases a lane and ships one task — dozens at once.
Orchestrator01
Allocates the lane bank across every active goal and spawns a manager per goal.
Manager02
Owns one goal — fans shippers and verifiers across lanes and merges verified work.
Worker03
Leases a lane and ships one task in its own isolated worktree, then frees the lane.
Each worker runs in its own isolated git worktree, so the work runs concurrently and stays separated — never clobbering another agent. Promotion to your main branch always stays human-gated.
Wired into the operation.
Durable goals & autopilot
Give the team a goal and it pursues it within a budget you set. An autopilot tick picks up matching work and reaps stale claims. Everything is off by default with a master kill switch.
The Crucible — self-optimizing
Every agent action is measured. An optimizer drives each workflow toward the cheapest version that still passes — eval-driven, gated, with a self-healing rollback. They get cheaper and better over time.
Copilot operates and builds
The same chat can run your workspace through MCP tools and, when you allow it, edit the product's own source — through the same ship / verify gate, with every develop turn revertible.
A signed audit trail
Lens logs every run: what ran, which tools it called, what it touched, and what it cost. The event log is a per-node hash chain with signed checkpoints — tamper-evident by construction.
Open to your terminal
An MCP server exposes every operation to any MCP-aware agent — including the Claude you already run in your terminal. The same gate applies whether work comes from the UI or a worker.
No agent can mark its own work done.
Every change travels todo → in progress → review → done, and a different agent must verify before it lands. The gate lives at the data layer — a self-verify is refused, not discouraged.
Explore the rest of the product.
Every surface reads from the one database you own — pick the next one.
Work
The human queue and the agent queue on one board.
Customers
Leads, pipelines, and one timeline per relationship.
Product
Build lanes, a roadmap with real DoD, and AI docs.
Operations
The directory, money, and back office on one layer.
Hiring
A local-first ATS — candidates are people.
Integrations
Sync your stack into the one database. No broker.
Ownership
One database, on your disk. Local-first, exportable.
Bring your whole business home.
Download Excellent and run your whole business on your own machine.