Mervin · A control tower for AI coding agents

Before Mervin

Ten agent tabs open.
You, relaying questions between them.
“Wait, did that ship?”
Context gone the moment a chat closes.
A deploy nobody quite approved.

Mervin runs the board. You make the calls.

The board, live

Every ticket flies the same strip.

One fresh agent per ticket, on the assignee’s own Mac, under their own Claude login. Every ticket moves through the same ten stages, so you know where anything stands without asking.

On your phone

The cockpit fits in your pocket.

9:41

Inbox

QuestionAPP-214

Carts made before the change: keep the old rounding rule, or reprice them?

Two open carts would drop by $0.40 under the new rule.

Your answer

Keep the old rule for carts made before the change.

Send answer

Inbox3BoardSettings

Questions find the right person.A stuck agent asks whoever can answer, on their phone, and waits for that person’s reply. Nobody plays telephone between tabs.

9:41

APP-214

Bulk quotes respect the per-item cap

BuildingDana R.

Brief

Goal: Each item in a bulk quote stops at its cap before the total adds up.
Why: “Two orders paid out over the cap last week.” (Ops)
Decided: D-1 The cap applies per item, not per cart. (Dana, 11-08)
Proposed: D-2 Carts made before the change keep the old rounding.
Next: Answer D-2, then review.

Since you looked (11-08)

Changed: 6 tests added for capped items
Yours to judge: D-2

Inbox3BoardSettings

Every ticket remembers.A short brief stays pinned to the ticket: the goal, what a person decided, what is still open, and what changed since you last looked.

9:41

Inbox

Change cardAPP-214 · v1

What: Bulk quotes cap each item before the total adds up.

For: Ops, pricing bulk orders

Check it:

Open a bulk quote with three items.
Push one item past its cap.
Watch the total.

You should see: the item stops at its cap.

Unchanged: single-item quotes, refunds

Confirm card

Inbox3BoardSettings

Review starts with what changed.Every change arrives with a card: what moved, who it is for, how to check it, and what stayed put.

9:41

Inbox

Approve a releasehigh risk

Release r42 to production: 4 tickets, every check green.

APP · expires in 1:52

Approve Deny

Inbox3BoardSettings

Confirm with Face ID

Approve a releaseRelease r42 to productionAPP · high risk

A fresh passkey from this phone, bound to this one approval. Mervin runs it once.

Confirm with Face ID Cancel

You clear the release. Nobody else.Approvals are signed, single use, bound to one action, and they expire. From the phone, each one takes Face ID.

The ground rules

Three rules it never breaks.

01Locked to Jira

No ticket, no run.

Every run, question, approval and result belongs to a Jira ticket. Agents post progress to the ticket as the person they work for, so the board stays the truth.

02Your machines

Your code stays home.

Agents run on your team’s own Macs, each in its own worktree and sandbox, signed in to that person’s own Claude account. The hub coordinates and never makes a model call.

03People decide

It never ships on its own.

Merged is not released. A person clears every release, and every clearance lands in a hash-chained audit log.

In the works

Bring your own assistant.

Your team keeps the ChatGPT or Claude they already use. Connected to Mervin, it can catch them up on their tickets and post their answers and reviews for them. Anything that counts still takes a tap on their phone.

All clear. Nothing on your six.