Done

SSH disconnect leaves agents marked live and injects mailbox notifications into the local shell

From antonDone 1 week agovia agent-mcp

Environment: AgentsRoom 1.214.0, Codex agents running on a Linux VPS over SSH from a Kali Linux desktop.

Steps:

  1. Run several saved agents in an SSH project.
  2. Disconnect the desktop from the Internet, then reconnect.
  3. Agent terminals show Shared connection to <ssh-host> closed. and return to the local shell.
  4. Send an agent-to-agent mailbox notification.
  5. Try agents_resume for an affected agent.

Actual:

  • agents_list_live still reports the disconnected agents as idle or waiting for input. On the VPS, a process check found only the newly resumed PM Codex process.
  • agents_resume refuses: already has a live console: there is nothing to resume.
  • The mailbox notification is injected at the LOCAL shell prompt instead of reaching the agent. The user observed the full notification followed by quote>.
  • agents_message_status reports these notices as delivered, although no agent has read them.

Expected: Detect that the remote CLI is no longer running, update the agent state, and allow resuming its previous conversation. Never inject agent prompts or mailbox notifications into a fallback shell. Restore SSH connectivity and validate the remote CLI before delivering queued messages.

The network loss itself is expected; stale console state, blocked recovery, and notification injection into the local shell are the reported defects. Hostnames and paths have been redacted.

Replies

The team1 week ago

SSH had stopped, but the remaining local terminal was still treated as a live agent. A fix is prepared to close that console, allow resuming its recorded conversation, and hold notifications until the remote agent is verified. Validation with a real network interruption is still pending. If this persists after the fix is released, please reopen the ticket with as many details as possible; a screenshot or video helps.

The team1 week ago

Thanks: the bug is fixed and the fix ships in the next release. If it still happens after that, tell us and we will gladly take another look.

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