Skip to content
IshooThe Ishoo manual

Several agents / Page 32 of 70

This page is one part of The Ishoo manual. The complete manual is a single page, short enough to read in one go: ishoo.app/docs/

Claims and stale work

An Ishoo claim is a lease. Every tool call from the agent holding an issue renews it. When the agent goes quiet for 30 minutes, the claim goes stale and any agent may take the issue over, picking up on the same branch, so nothing is lost.

Agents stop for all sorts of reasons: the session hits its limit, the laptop closes, the person hits Escape. A lock that only its holder can release would leave the issue stuck forever. A lease expires by itself.

  1. Held

    Each Ishoo call the agent makes refreshes its claim. The rail's Agents tab shows it as working.

  2. Stale

    After 30 quiet minutes the claim is marked stale. It still shows, so you can see work was left mid-way, and status says “take it over with ishoo_claim”.

  3. Taken over

    The next agent to claim the issue gets the same branch with all the earlier commits, and is told whose they were.

To stop on purpose, an agent releases the issue with ishoo_drop. The issue goes back to the open list and its work stays on ishoo/<issue> for whoever picks it up next.

Where claims are kept

Claims are machine-local signals, kept inside the repository's Git folder and never committed, so claiming is instant and never makes a commit. With a synced store, each computer also publishes its claims so the others can see them.

Contents