Page 1 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/
What Ishoo is
Ishoo is a companion app for Claude Code, Codex and other MCP coding agents. It keeps the project's plan, issues and decisions beside the code, lets several agents work without colliding, and records every change that landed: who, what, why and which tests ran.
You talk to your agent the way you already do. Through Ishoo's tools the agent reads the plan, takes an issue, works in its own copy of the project, and lands the change on main with a note of what changed and why. The Ishoo window shows the plan, who is working on what, and everything that landed.
Status
The agent asks Ishoo what the plan is, what matters, who holds what, and whether main is broken.
Claim
The agent takes one issue and gets its own worktree, so it never edits the files another agent is editing.
Work
The agent works as it normally would.
Land
One call commits, rebases on main, pushes, and records the landing.
Without Ishoo
The plan lives in a chat that ends. Two agents edit the same file and neither notices. “Done” means the agent said so, and nobody wrote down why.
With Ishoo
The plan lives with the project, so a new session picks it up. Each agent holds its own issue in its own worktree. Every landing is recorded with its reason and the tests that ran.
NoteIshoo does not include an AI model and doesn't talk to one. You bring your own coding agent and AI plan. Ishoo is the shared project record that your agents work through.
Trust, nudge, trace
Ishoo trusts agents to do their job. It nudges instead of blocking: it comments when an issue is outside the plan, when two agents touch the same files, or when a landing names no tests. It refuses only two things: taking an issue another live agent holds, and landing on top of a main known to be broken. Slow checks run at night, while nobody waits.