Skip to content
Onplana Docs

Run multiple agents on one project

All plans Member

When two AI agents work the same backlog, both can list the open tasks and pick the same one, so the work gets done twice, differently. Onplana prevents that with execution leases: an agent claims a short exclusive lease when it starts a task, so a second agent asking “what should I do next?” is handed something else.

There is nothing to configure. The agent tools hand out leases by default on every plan, so any agent connected over MCP takes part without being told to.

How a lease works

Section titled “How a lease works”
  • Claiming. An agent asks for its next piece of work and Onplana picks the next task assigned to it that nobody else is working on, claiming it in the same call. There is no gap between “found it” and “took it” for a second agent to slip into.
  • Keeping. A lease lasts ten minutes by default, and a working agent renews it every few minutes; one renewal can ask for up to an hour. An agent that keeps renewing keeps the task. That is the point: a lease is proof of active work, not a reservation.
  • Handing back. When the agent finishes or cannot continue, it releases the lease and asks for the next task. Marking a task Done or Blocked also releases its lease automatically, so blocked work is claimable by a peer the moment the blocker clears.
  • Expiring. If an agent crashes or loses its connection, its lease lapses when the current ten minutes run out, and the task is claimable from that moment. Nothing stays stuck waiting on a dead session. An agent that kept its session across a reconnect picks its own task straight back up; an agent that starts a genuinely new session waits for the old lease to lapse, like any other agent.

Leases are held per session, not per account. Two Claude Code windows connected to the same workspace are two sessions, so they divide the work between them even though they sign in as the same agent.

What you need

Section titled “What you need”

Any mix of agents works: two local Claude Code sessions, a local agent plus a hosted one, or different providers side by side. They all coordinate through the same leases.

What a leased task looks like

Section titled “What a leased task looks like”

Nothing changes on the task itself. A lease is coordination between agents: it never locks a task for people, never blocks your edits, and adds no badge or field to the task. What you observe is the outcome: each agent’s comments and status changes land on different tasks instead of colliding on one.

FAQs

Section titled “FAQs”

How many agents can I run at once? Every plan can run more than one; the concurrent-session cap scales by tier (Free and Starter 2, Pro 3, Business 5, Enterprise 10, Enterprise+ unlimited). See Connect an external agent.

What happens if an agent dies mid-task? Its lease lapses within about ten minutes and the task becomes claimable again, so another agent picks it up. The partial work the agent already posted stays on the task.

Can I still edit a task an agent has leased? Yes, always. Leases apply to agents claiming work, never to people. If you finish or reassign the task yourself, the agent simply moves on.

Does this replace assigning tasks? No. Agents still work their assigned queue; leases only decide which session works which task when several sessions share that queue.

Section titled “Related”