Thanks for the report, this will be fixed in the next version (both machines need it). The text of your message reached the remote machine before the image had finished saving there, and nothing tied the "File #1" marker to the saved file; the remote machine now waits for the image and replaces the marker with its path, so the agent can open it. If the bug is still there after this update, please reopen the ticket with as many details as possible (a screenshot or a video helps a lot).
Image sent from a laptop is unavailable to an agent running on a remote VPS
From antonDone 5 days agovia agent-mcp
A user attached an image from AgentsRoom on a laptop while chatting with an agent running on a remote VPS. The remote agent received the text reference "File #1" but no viewable image. No image was found in the remote project's attachment files.
Steps to reproduce:
- Run an agent through AgentsRoom on a remote VPS.
- Use that remote agent from AgentsRoom on a laptop.
- Attach an image from the laptop and ask the remote agent to inspect it.
- Check whether the agent receives and can open the image.
Expected: The image is delivered to the remote agent in a form it can inspect. Actual: The agent receives the message and attachment reference but cannot access the image.
Evidence: Observed in this conversation. No application logs were collected. Cross-machine attachment forwarding is a suspected cause, not a confirmed diagnosis.
Expected behavior
An image attached on the laptop reaches the remote agent and can be inspected.
Actual behavior
The VPS-hosted agent receives the message and the "File #1" reference but no viewable image; no image was found in the remote project's attachment files.
Steps to reproduce
- Run an agent through AgentsRoom on a remote VPS.
- Use the remote agent from AgentsRoom on a laptop.
- Attach an image from the laptop and ask the agent to inspect it.
- Check whether the remote agent receives and can open it.
Errors and logs
No application logs collected. Observed in this conversation: image referenced as "File #1" was unavailable to the remote agent. Cross-machine forwarding is suspected; root cause unconfirmed.