Run a few coding agents without babysitting them

developerlanes (the lane command) gives each agent a task and its own Git worktree. Answer its questions when it gets stuck, then read its report before deciding what to merge.

The local workflow works today in Herdr. You can also read task status from remote machines. We're working toward coordinating agents across machines, with an inbox in your browser, on your phone or in Teams.

Tell us what you'd change

When an agent needs you

An agent spots a file-format change that could break existing files. Instead of guessing, it asks you to pick between two options.

This is how we want that decision to look in a browser. Today, you can answer question cards in the terminal.

Planned: in your terminal

developerlanes lives in the terminal first. This is the planned terminal design inside Herdr, not shipped, using invented tasks and machines.

Planned terminal design in Herdr: an attention-sorted task list stays beside a question, answer choices and a separately attributed agent report.
List and detail. The queue stays in view while you consider an answer.
Planned remote-machine flow: an asleep machine's last tasks remain visible, followed by explicit wake stages and a checked handoff to Herdr's remote view.
Another machine. Waking it takes a key press, not a status check.
Planned narrow terminal at 100 by 40 cells: one decision card replaces the list, with choices, agent-reported context and Esc to return.
A narrow terminal. Open one card, then return to the list with Esc.

These are mockups, not terminal captures. Open any image to read it at full size.

Inbox mockups

These browser, phone and Teams inboxes are design drafts, not shipped screens, using invented data.

Desktop design draft: needs-you questions lead the inbox beside a decision and separately attributed agent evidence.
Desktop inbox. Questions that need an answer go at the top.
Phone inbox design draft: at least two lanes need you, three cannot be confirmed, and one machine is offline.
Phone inbox. Unknown and offline work stays visible.
Phone answer design draft: a question with context, three choices, an optional note and an explicit send-once action.
Answer from a phone. Choose, then deliberately send once.
Teams light-theme design draft: a lane needs a click in its own agent window, not an answer from the decision UI.
Inside Teams. Tool permissions still need the agent's own window.
Stale-data desktop design draft: an offline machine’s old question is greyed out, timestamped and cannot receive an answer.
Offline. You can still see the machine's last question.

How it works

  1. Prepare a lane.A separate checkout, an agent session and a place for its report.
  2. Let it work.The agent leaves a report or asks a specific question.
  3. Review the evidence.A report is the agent's account, not proof that its changes or tests are correct.

Copilot and Pi work locally without Azure. Current setup requirements still apply; broader platform support needs validation.

Read-only remote status uses Azure Relay. For an already paired worker, lane connect opens its Herdr session over owner SSH. Explicit Dev Box wake works for saved Azure Dev Box bindings: reading status never powers up a box.

Git worktrees separate edits, not machine permissions. Owner SSH grants the account's access; it isn't a restricted task-status connection.

A few rules

Check an uncertain launch
If delivery is uncertain, inspect and reconcile. Don't automatically submit the same task again.
Show stale status
Missing or old observations stay visibly uncertain, not an empty queue with nothing to do.
Keep answers tied to questions
An answer belongs to its original question, not whichever prompt happens to be visible later.
Separate reading from access
Read-only status and owner SSH are different capabilities. Neither observation nor reconnect should silently start work or wake a machine.

Where it stands

This is an early project, not a generally available release. The source repository is private today.

Working today

  • Local lanes with separate worktrees and start-once task launch.
  • Needs-you question cards and lane answer.
  • The two-task onboarding demo.
  • Read-only remote task status over Azure Relay.
  • lane connect to already paired workers over owner SSH.
  • A shared Relay connection core.
  • An offline machine catalog and azcommandr import.
  • Explicit Azure Dev Box wake.

Planned / exploring

  • The terminal list-and-detail view shown above.
  • Worker pairing and a fleet view across machines.
  • A decision inbox in the browser, on your phone and in Teams.
  • Possible cluster workers later.

The machine-access work comes from David Gamero's azcommandr. developerlanes brings that direction together with task coordination and decisions.

What would you change?

  1. Which questions would you answer from your phone? When would you want the full agent session?
  2. What would you need in a report to start reviewing the work?
  3. If a machine goes offline, when would you want a heads-up?