{"version":"2.1.246","anchor":"attached-machines-can-advertise-themselves-as-idle","canonical_anchor":"attached-machines-can-advertise-themselves-as-idle","heading":"Attached machines can advertise themselves as idle","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/attached-machines-can-advertise-themselves-as-idle","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Attached machines can advertise themselves as idle\n\nA machine attached to a cloud session but running nothing now advertises itself as idle.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- The exact added sentence is \"This machine is attached but does not run commands for this session.\"\n- On connecting, the machine now logs the list of tool names it announces and emits a new `tengu_device_bridge_connect_frame` event carrying the tool count, whether a shell is served, and the number of MCP tools.\n- No new gate: the existing checks for whether an attached machine is available still decide this.\n\n**Evidence**\n\n`tengu_device_bridge_connect_frame`, `This machine is attached but does not run commands for this session.`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}