{"version":"2.1.284","anchor":"tengu-drifting-heron-gate-lets-a-remote-trigger-tool-be-defe","canonical_anchor":"tengu-drifting-heron-gate-lets-a-remote-trigger-tool-be-defe","heading":"A tool in remotely triggered sessions may no longer be loaded up front","tier":"soon","area":"Tool Loading","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/tengu-drifting-heron-gate-lets-a-remote-trigger-tool-be-defe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### A tool in remotely triggered sessions may no longer be loaded up front\n\nIn sessions started by a remote trigger, one tool is no longer always forced into the set of tools loaded at the start\n\n**Unclear.** Which tool this applies to, and whether it was always loaded up front before, is not settled.\n\n**What**\n\nClaude Code does not always load every tool at the start of a session. Some are deferred, meaning Claude finds and loads them only when needed, using `ToolSearch`. A new remote setting now decides whether one particular built-in tool stays forced into the always-loaded set in sessions started by a remote trigger, that is, when `CLAUDE_CODE_ENTRYPOINT` is `remote_trigger` or `remote_cowork_trigger`.\n\nWhen the server sends nothing, the setting falls back to on, and in that case the tool is no longer forced to load up front.\n\n**Why**\n\nIt changes which tools remotely triggered sessions have ready from the start and which Claude has to look up first.\n\n- Flag `tengu_drifting_heron`: Not enough to say (read for one account on one subscription tier against v2.1.284; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Tool Loading\n- Names: `CLAUDE_CODE_ENTRYPOINT`\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}