Features
Everything from a sentence to a merged PR.
Scopes, agents, worktrees, review, permissions and usage in one system. Here is what each part does.
Scopes
The unit of work, in plain words.
Describe the outcome. A planner turns it into tasks, and every task belongs to a role.
- Describe work in the app, Telegram or Slack
- The planner creates tasks with roles and acceptance criteria
- One branch and worktree per scope
- Progress, review and landing live on the scope
- 1Friendlier 404 copyWriter · claudeDone
- 2New fox illustrationDesigner · codexReview
- 3Route-not-found pageFrontend · opencodeBuilding
- 4Check redirectsQA · geminiPlanned
- 1Audit colour tokensFrontend · opencodeDone
- 2Add the theme toggleFrontend · claudeBuilding
- 3Test contrastQA · geminiPlanned
- 1Rewrite the pricing copyWriter · claudeDone
- 2Legal reviewQA · geminiReview
Agents
Bring the agent you already use.
Claude Code, Codex, opencode, Gemini, Pi, or any ACP agent. They report to the same queue.
- Detected when installed and signed in
- A default model per agent at the organization
- Override per project, role or task
- Any ACP agent via a launch command
Agents on this machine
detectedAnything that speaks ACP can be added with a launch command.
Review
The gate before merge.
A read-only reviewer checks acceptance criteria and sends concrete changes back. The builder never approves its own work.
- Read-only reviewer; it does not edit files
- Three rounds, then a person decides
- Failed reviewer runs get three tries in total
- Landing is a setting: branch, PR, merge or merge + push
- Round 1 · changes requestedAdd alt text to the illustration.
- Round 2 · approvedAcceptance criteria met.
- LandingLeave branchOpen PRMergeMerge + push#42 Redesign the 404 pageOpened
Needs you
One inbox for every decision.
Questions, permissions, failed landings and stuck reviews collect in one place instead of stalling a run silently.
- Answer permissions, questions and review stalls
- Failed landings and blocked tasks surface here
- Stalled running tasks are flagged after 20 minutes
- Answer from the app or your phone
- QuestionKeep the old illustration on the 404?Designer · New fox illustration
- PermissionRun `npm run build` in the worktree?Frontend · claude on this-mac
- ReviewReviewer asked for changes three timesQA · Check redirects
Machines
Your machines, not ours.
Run the connector on a laptop, server or VPS. Repositories, worktrees and agent sessions stay there.
Usage
See the work and the spend.
Token usage by project, model, scope and task. Telegram and Slack alerts for the events you choose.
Token usage
Demo App · all time| Model | Input | Output | Thinking | Cached | Total | Runs |
|---|---|---|---|---|---|---|
| claude-sonnet | 820k | 96k | 41k | 310k | 1.3M | 14 |
| codex | 240k | 22k | — | 110k | 372k | 6 |
Usage is counted in tokens. Some agents also show an estimated cost per thread. Agents that do not report usage are left out.
Pick smaller models for roles that do not need the big one.
Alerts
- Task ready for reviewon
- Task failedon
- Agent needs permissionon
- Agent has a questionon
More events available.
Needs you also flags a running task with no activity for 20 minutes.
Signals
The work, at a glance.
Running tasks, review rounds, permissions, token usage, devices and scopes on one page. No spreadsheet, no status meeting.
Running now
3 agentsClaude, Codex and opencode on three tasks.
Review queue
2 waitingThe reviewer is read-only. You see every round.
Needs you
2 itemsAnswer once; the agent carries on.
Token usage
1.3MTokens by model, scope and task, not a bill.
Devices
3 onlineHeartbeats, versions and the agents on each machine.
Scopes
3 activeOne branch and worktree per scope.
Chat
Work from where you talk.
Add the bot to a team or customer channel. Mention it with an instruction and the planner picks it up.
- Telegram and Slack channels
- Mention the bot to create a scope
- Threads keep the conversation with the work
- The same queue as the app
Mobile
The same queue in your pocket.
Answer a permission, approve a review or check a scope from your phone. The same queue and the same gate.
Tracked by model, scope and task.Swipe to see the four screens.
How it works
A scope's first hour
One scope, six steps, and nobody asking for a status update. Timings are illustrative.
- 09:0001Input
A sentence becomes a scope
You describe the work in the app, Telegram or Slack.
New scopeRedesign the 404 page. Friendly copy, the fox, and a redirect check.
- 09:0202Plan
The planner makes tasks
It reads the project and gives each task a role and acceptance criteria.
WriterFriendlier 404 copyDesignerNew fox illustrationFrontendRoute-not-found page - 09:0403Branch
A branch and a worktree
The scope gets one branch and one worktree on a connected machine.
scope/404-pagewt/404-page - 09:1204Build
Builders run in parallel
Claude, Codex and opencode work on separate tasks at the same time.
claude · this-macrunningcodex · hexabaserunningopencode · this-macrunning - 09:2605Review
The reviewer asks for one change
Round 1 returns concrete notes; round 2 approves the work.
Round 1 · changes requestedRound 2 · approved - 09:3106Land
The gate lands it
Leave the branch, open a PR, merge, or merge and push. You choose per project.
#42 Redesign the 404 pageOpenedLeave branchOpen PRMergeMerge + push
Ready to connect a machine?
Get access, connect a machine, and describe your first scope.