Running tools on another machine now loads only when used, and its gate is off in this build.
The remote-tools runtime is present as an on-demand chunk but its gate is off, so it never loads.
What's wrong with this entry?
The machinery for running tools on another machine is fetched with a dynamic import and cached rather than being linked into the main bundle, keeping it off the startup path entirely while its gate is off.
- If the import throws, the failure is logged and the loader resets, so a later access retries instead of staying broken.
- With no runtime loaded, there is simply no remote tool host.
createRemoteToolHostsRuntime
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.247
Session-channel messages from senders this session cannot verify are refused, dropped or trimmed
Both mention tool
-
v2.1.247
Plumbing calls and passthrough MCP tools: described in the protocol, not yet served
Both mention tool
-
v2.1.247
Clearer explanations when a call to an attached machine fails
Both mention tool