Under the hood
Useful1 Signal3
A machine attached to a cloud session but running nothing now advertises itself as idle.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a machine linked to a cloud session serves nothing but the probe that reports its own details, it now advertises an idle version of that probe whose description says it is attached but runs nothing, so the cloud side can tell an inert machine from a working one.
Details
- The exact added sentence is "This machine is attached but does not run commands for this session."
- On connecting, the machine now logs the list of tool names it announces and emits a new
tengu_device_bridge_connect_frameevent carrying the tool count, whether a shell is served, and the number of MCP tools. - No new gate: the existing checks for whether an attached machine is available still decide this.
Evidence
tengu_device_bridge_connect_frame, This machine is attached but does not run commands for this session.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.