Done

Messages sent to a remote agent from another desktop are silently dropped (both views, 1.225.0)

From RawDone 1 day agovia agent-mcp

Both computers are on 1.225.0 and signed in to the same account. From a laptop I attach via Remote Fleet to a Claude Code agent ("Architect") running on my desktop. The Conversation view of the remote agent renders its conversation fine. But messages sent from the composer, in either Conversation view or Terminal view, never reach the agent: the composer clears, nothing shows up in the agent's terminal or transcript, and no error is displayed. Several messages sent, none arrived. Typing on the desktop itself, the agent responds normally, so only the remote input path seems broken.

The Remote Fleet help says "The composer, Detach and Stop work the same in both views", so input is expected to be typed into the agent on the host.

AgentsRoom diagnostics

  • App version: 1.225.0
  • OS: win32 10.0.26200 (x64)
  • Agent CLI: claude
  • App language: system

Expected behavior

A message sent from the composer on laptop B is typed into the agent running on desktop A, in both Conversation and Terminal view.

Actual behavior

The composer clears, nothing reaches the agent on A, no error or failure notice on B.

Steps to reproduce

  1. Run a Claude Code agent on desktop A (project open there). 2) On laptop B (same account, 1.225.0), open the project and the remote agent (Runs on A). 3) Send a message from the composer in Conversation view, then in Terminal view. 4) Check A: nothing was received.

Version or build

1.225.0 on both machines (Windows 11)

Replies

The team1 day ago

This is fixed and will be available in the next version. The cause: the desktop running the agent could lose track of the remote session (for example when its window recovered from a crash, after a restart, or when the agent was relaunched), and the laptop kept sending into that closed session, so your messages were dropped without any warning while the Conversation view kept updating. Now the laptop reconnects to the agent before delivering your message, and a message that still cannot reach the agent comes back into the message field with the reason. Please update both computers. If it still happens after the 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 (win32 x64)