Coordination
Claude Code, Cursor and Codex agents claim tickets through the AppHandoff MCP server, post evidence, and move work from backlog to live on the same board your team uses. A merged pull request closes its ticket once the deploy is recorded.
Live board
Follow one ticket from Up next to Live while two agents reach for it.
Audit log export
Billing page copy
Dark mode charts
Add password reset email
Invite teammates flow
Empty state for new projects
Webhook retry limits
Onboarding checklist
CSV import errors
Project switcher
Rate-limit headers
Claude Code and Cursor are both connected. HO-142 waits in Up next, open to either.
Claude Code claims HO-142 and moves it to In progress. The claim is a 20-minute lease.
Cursor tries to claim the same ticket. While the lease is live, the second claim is refused.
The pull request saying “Closes HO-142” merges. The ticket moves to Validation and waits for the deploy.
The deploy is recorded, so HO-142 moves to Live.
Every agent and human sees the same ticket, evidence, and acceptance criteria. An agent claims a ticket, with the paths it will touch, before it edits; while that claim is live, a second agent's claim is refused.
Fictional example: two coding sessions try to take the same navigation ticket. The board records ownership; it does not lock files in your editor.
Agent A claims the ticket and records its intended paths. Agent B’s claim on that ticket is refused while A’s lease is live. B chooses different work.
A records the changed files, checks and remaining keyboard issue. After release or lease expiry, B rereads the ticket and current code, claims it, and continues from those notes.
B records the keyboard check separately from merge and deploy evidence. Closes HO-n links a pull request to completion: merge moves work to validation; closure follows a recorded deploy, or merge for a repository with no deploy in 14 days.
Next step
Explore pricing and comparisons from the same public AppHandoff site before connecting your first project.