Features

Run more agents. Lose less.

Everything below is built and on every plan. What's still coming is marked.

The floor

Every agent, live, as an office.

Each Claude Code session is a room, labelled by person and branch. Your whole team's work on one floor, in a view anyone can read.

  • Rooms light up while agents work and fade when they go quiet.
  • Several repos? Each gets its own district. Work in another repo shows as a drone.
  • A plain-words feed of what happened. Click an item to jump to its room.
  • A key explains every icon and status.
Priya · feat/billingSam · fix/auth-timeout
Handoff

Hand off in a click.

The next person gets the branch and a brief written from the full session. Take handoff opens Claude in a fresh worktree on that branch.

  • The work is pushed to its own branch first. Main is never touched.
  • A running clock while the brief is written and the handoff opens.
  • Take it in a plain terminal, or open it in Orca.
  • Hand a room to a new session of your own, and pick it up later.
Today
Agent writes a summary→Pasted into Slack→Fresh session→What it left out is gone
With Isoplan
Hand off from the floor→Branch and brief→Take handoff→Ask the original session
Ask the room

Ask the agent that did the work.

After a handoff, the new agent asks the original session what it knew. Answers come from the full session, not a summary.

  • Only a handoff grants the right to ask.
  • The owner sees every question and every answer.
  • The owner can revoke it any time.
Sam's agent asks Why is the retry capped at three?
Priya's session answers The payment provider locks the card after four tries.
Priya sees this questionRevoke
Answer from anywhere

Questions don't wait in a terminal.

When an agent asks its owner a question, it shows on the floor and on your phone. Answer it there and the agent carries on.

  • The question sits at the owner's desk in the room.
  • The agent's options, ready to pick.
  • Rather answer in the terminal? That still works.
Kofi's agent asks Run the migration on staging first?Yes, staging firstSkip staging
Waiting for Kofi2 min
Early warnings

Catch problems early.

Clashing edits, stalled and failed agents come first, so nothing sits broken until someone looks.

  • A possible conflict is a file more than one agent edited recently.
  • The later editor's agent is told, so it can sort it out itself.
  • Filter the feed down to what needs action.
Possible conflict src/billing.ts, Priya and Sam
Stalled Leo, chore/deps-upgrade12 min
Failed Mei, feat/export-csv
Question for Ana
Results

See what it's worth.

Admins see handoffs and adoption per person, measured against your own baseline.

  • A full-screen Results page, for admins only.
  • Handoffs taken over, and who uses the floor.
  • Measured in your office, not borrowed from someone else's.
Setup

Sits on top of your setup.

One plugin, one click. Nothing to migrate, and nothing to maintain after install.

  • Install the plugin, then press Connect Claude Code on the floor.
  • In Claude Code, /isoplan:connect says whether it worked.
  • See and revoke your connected computers in Settings.
  • Admins add the team's repos and invite people by link.
  • Sign in with Google or GitHub.
On topIsoplan
HarnessClaude CodeConductorOrcaHerderAny terminal
KnowledgeYour RAGCLAUDE.mdMemories
SessionsLocal Claude CodeRemote sessions: coming
Coming

Not built yet. On the way.

These aren't in Isoplan today. They're what we're building next.

Coming

Orchestration

A lead agent directing other lead agents you can see, each keeping its memory.

Coming

Company guardrails

Company-wide rules and automated checks for every agent.

Coming

Remote sessions

Agents running through the API, on the floor with the rest.

See your agents today.

We'll only email you about Isoplan.

Join early access

We're opening Isoplan a few teams at a time. We set up your office and email you an invite.

Talk to us

Enterprise, open source or a pilot for your team.