Skip to content
IshooThe Ishoo manual

Several agents / Page 31 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/

Several agents

Parallel agents stop overwriting each other when each holds its own task in its own worktree and changes come back one at a time. In Ishoo, an agent claims an issue (no other live agent can), gets a worktree, and lands on main through one call that rebases first.

Two agents in one folder is like two people typing in one document: each one's edits land in the middle of the other's. The usual fixes, “only run one agent” or “give each a separate clone”, either waste the agents or turn the end of the day into a merge marathon. Ishoo keeps them apart while they work and brings them together one at a time.

  1. One issue each

    A claimed issue belongs to that agent while it's active. Another agent asking for it is refused: one of the only two refusals Ishoo has.

  2. One worktree each

    Each claim gets its own folder, .ishoo/worktrees/<issue>, on its own branch, ishoo/<issue>. No agent edits files another is editing, and main is untouched until landing.

  3. Warnings on overlap

    An agent names the files it expects to touch. If another live agent named the same files or folders, the claim reply says who and where.

  4. One landing at a time

    Landing rebases on the newest main first. The next agent to land rebases on that.

What a claim tells the agent#

A claim never fails over a warning. It takes the issue, makes the worktree, and adds a line for each thing worth knowing. These are the lines an agent can see:

WhenThe reply says
Another live agent named some of the same files.Heads up: agent-41c2 on TEAM-04 is in src/sync.rs. Coordinate or split the files.
The issue's last holder went quiet for 30 minutes. Their work is kept.Took over from agent-41c2 (stale); their commits are on ishoo/TEAM-04.
Something this issue depends on isn't done.Unfinished dependencies: STOR-05. Claim kept; work on the prerequisite first unless you can make independent progress.
The issue sat while the code moved on. Days count only when something landed.TEAM-04 was last touched 18 active days ago. Check it against the code first and fix the text if it drifted.
The issue is outside the plan agents are pointed at.TEAM-04 isn't in the active plan "Teams". Fine if it unblocks it; otherwise, is this the most important thing?
A check is known to fail on main.Main is broken since 3e1a9c04b (cargo test fails in sync). Is fixing that more urgent?
Always, for the files named.Rules for these files: store, sync.

Builds that don't cross#

Separate folders aren't enough for compiled projects. In a Rust project, every worktree's build would normally either rebuild all dependencies from scratch or share one target folder, where one worktree's cargo test can run another worktree's test binary and report its pass. Ishoo sets up each worktree so dependencies compile once and are shared, while the project's own code builds under a name unique to that worktree. A pass is that worktree's pass.

Across computers#

When the store syncs to a private home, each computer publishes what its agents hold there, under its own name. Every computer reads the others' claims, so a laptop and a desktop never hand out the same issue, and status shows lines like “agent-41c2 for Sam on desktop”. Each computer only ever writes its own entry, so two computers never fight over one record.

NoteHow many agents at once? As many as you have separate issues for. Issues that touch different files run in parallel happily; issues in the same files work best one after another, and the overlap warning tells you when you're about to do that.

Contents