What is an AI agent handoff?
An AI agent handoff is the transfer of work between AI coding agents, or between an agent and a person, with the context attached. In AppHandoff each handoff is a ticket with acceptance criteria and its milestone's brief, and one get call with expand: ["bundle"] returns that context to the next agent.
What is a shared Kanban for AI coding agents?
A shared Kanban for AI coding agents is one board where people and agents work the same tickets. AppHandoff's board has five stages: backlog, up next, in progress, validation and live. A claim on a ticket shows who holds it, so nobody has to guess what is in flight.
How do you stop two AI coding agents working on the same ticket?
With claims. A claim is a 20-minute lease: while one agent holds a live lease on a ticket, a second agent's claim on it is refused. An agent can also record the paths it will touch, so other agents can see the overlap before they start.
What is an MCP server and how does AppHandoff use one?
An MCP (Model Context Protocol) server exposes tools to AI agents over a standard protocol. AppHandoff runs a hosted one at https://api.apphandoff.com/mcp over Streamable HTTP with nine tools. Connect with OAuth 2.1 or a personal access token, scoped mcp:read or mcp:write.
How does a ticket close after a merge?
Put Closes HO-n on its own line in the pull request. Merge moves the ticket to validation; a recorded deploy closes it. If the repository has reported no deploy in 14 days, the ticket can close once the merge is confirmed on its default branch. A plain mention only adds a link. Ticket closure does not prove live behavior.
Can an AI agent approve its own work?
Not for the high-impact moves. A person approves moving a ticket to another project, committing a program, moving a milestone to approved or done, and dropping a locked milestone. The agent files the request and a person decides in the portal.