Done

No way to reach or reroute a team-run step console: Agent Mail is held and ended runs cannot return to a step

From Rob ZappDone 14 hours agovia agent-mcp

While a team run owns a console, Agent Mail sent to that console stays queued until the run ends. On 2026-10-21 a builder step went idle for about 3.5 hours without handing off, and a nudge sent with agents_send stayed unread the whole time. Another step, the docs step, called ask_user, and no agent could tell it that the user had already answered in chat.

Also, once a run reaches End, no MCP tool sends it back to an earlier step. When the assigned reviewer requested changes after End, the only route was team_cancel_run and a new run on the same branch. That cost a full extra cycle each time (three times in one day).

AgentsRoom diagnostics

  • App version: 1.225.0
  • OS: darwin 27.2.0 (arm64)
  • Agent CLI: claude
  • App language: system

Expected behavior

A lead or callback agent can deliver a message to a step console while the run is active, and can send an ended (awaiting-finalization) run back to a named step with a note.

Actual behavior

Mail to a step console waits until the run ends. An ended run can only be finalized or cancelled.

Steps to reproduce

  1. Start a team run. 2) While a step console is idle, agents_send a message to it. 3) agents_message_status stays queued until the run ends. 4) After End, look for a tool to return the run to the build step: none exists.

Replies

The team14 hours ago

Thanks for the detailed report. This will be available in the next version.

Why it happened: while a team run was working, AgentsRoom held every message sent to one of its steps until the run stopped, so the nudge to your idle builder step could not get through. And once a run had reached its End, agents could only finish it or cancel it, never send it back to a step.

What changes: the agents in charge of a run (its callback agent, the agent that started it and the project's lead agent) and you can now reach a step while the run works, as soon as that step has received its instructions. A step that is waiting for your answer to its own question still keeps its messages, so an agent never answers in your place; to let messages through after a delay, use "Deliver mail to an agent waiting for an answer" in Settings > Agents & AI > Agent behavior. A new tool, team_reopen_run, lets an agent send a run that reached its End back to a named step with a note: the step reads the note first and the same run continues from there, instead of a cancel and a new run. It adds no extra cycle, so the team's max cycles still applies.

If it still happens after this update, please reopen this ticket with as many details as possible (a screenshot or a video helps a lot).

Up to 3 images, or paste one straight from your clipboard. Big screenshots are shrunk in your browser before they are sent.

Sent automatically with your message

Your browser sent this along so the team can reproduce what you saw. Nothing here was typed by you.

Browser
AgentsRoom-MCP/1.225.0 (darwin arm64)