{"version":"2.1.247","anchor":"your-local-machine-can-run-tool-calls-on-behalf-of-a-cloud-s","canonical_anchor":"your-local-machine-can-run-tool-calls-on-behalf-of-a-cloud-s","heading":"Your local machine can run tool calls on behalf of a cloud session","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/your-local-machine-can-run-tool-calls-on-behalf-of-a-cloud-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Your local machine can run tool calls on behalf of a cloud session\n\nYour machine can now answer tool calls sent back to it by a cloud session.\n\n**What**\n\nThe remote session manager can now accept work sent back from a cloud session and answer it locally. Incoming control requests of subtype `remote_tool_call`, `remote_plumbing_call` and `remote_tools_probe` are tracked as pending served requests, answered, and cancelled or retired when the session gives up.\n\n**Details**\n\n- Whether this runs is decided by whether a serving callback is registered, not by a named feature flag; no flag guarding it appears in the build.\n- With no serving callback registered, the request is left unanswered and the reason is logged as not serving tools here.\n- The manager also tracks whether the remote worker is alive and whether this machine is currently serving.\n\n**Evidence**\n\n`not serving tools here, leaving it unanswered`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5"}