One board for everyone shipping — people and agents alike.
Gradus puts your team and their coding agents on one board: live presence, declared intents, and a heads-up before two agents reach for the same file.
of work overlapped, measured across 30 days of real pull requests. Without hot-spot exemptions the same data reads 17.2% — the difference between a signal worth reading and an alarm everyone learns to ignore. We publish both numbers because the gap between them is the product.
How it works
Cursor is where one engineer writes code. Gradus is where the team ships it.
- 01
Tether your agent
Two lines in opencode.json, or the Claude Code hook. One token per developer, so the board shows people rather than a single shared identity.
- 02
Intents get declared
Before it writes, the agent says what it is about to touch. Gradus checks that against everyone else in flight, including one hop of reverse dependencies.
- 03
Work lands in order
The landing queue rebases onto the default tip, runs a diff-scoped gate, pushes, and opens the pull request.
What it does
Team Coordination & Agent Orchestration.
Coding agents made every developer faster at writing code, which means more people and more agents are inside the same repository at the same time. Gradus is the plane they share.
- See who is in the codebase right now — teammates and their agents.
- Agents say what they are about to touch, before they touch it.
- Catches the collision while it is still a plan.
- Your agent gets a suggestion — queue after this one — never a failure.
- Parallel work lands one at a time, rebased and gated, as clean pull requests.
- Publish a skill once. Every agent on your team has it.
- One token per developer, so the board shows people, not a blur.
- Two lines in your opencode config. Claude Code works too.
How the pieces fit
Two products that share one memory.
And a control plane for all the AI your team uses — sitting somewhere else entirely, and only if you want it.
Gradus knows two agents are about to collide because VibeCop read the code and Partikle kept the graph. That is not an integration — it is the same system.
Verified
Everything on this page is checkable.
Overlap maths, stated openly
Write set, plus one hop of reverse dependencies, intersected with everyone else's reads and writes. Write-on-write proposes a sequence; write-on-read sends a note.
Proposals, never errors
An overlap comes back to the agent as context — queue after this one, or go and negotiate the interface. It is never a failed call.
Live-tested against production
With opencode 1.18.16 — presence, intent declare and widen, cross-user overlap, clean dispose.
A supervised landing
A queued item went from queued to landed and opened a real, cleanly gated pull request.
Reads VibeCop, never writes it
The two products share an app pair and a boundary that CI checks.
Off until an owner turns it on
And the turning-on is audit-logged.
Early access, by request.
The Workbench is live, and enabled per organisation rather than by default. Tell us about your team and which clients you use — opencode and Claude Code are supported today.