The selecting predicate returns false outright, so the alternative wording is unreachable.
Groundwork is present for a mode in which tools from connected MCP servers (external tool servers Claude Code connects to) are called from inside the REPL environment rather than advertised as top-level tools. The predicate that selects this mode is a function whose whole body returns false, so the filter never fires and the wait-for-servers tool always emits the existing wording, "The server's tools should now be available." and "its tools will be added to your tool list". The alternative phrasing describing REPL-callable tools is compiled in but unreachable.
- MCP authentication stub tools are now tagged
isAuthStub: !0in their server info, a field absent from 2.1.247. - Two new helpers read that tag: one narrows a tool list to non-MCP tools plus auth stubs, the other decides whether MCP tools stay deferrable and whether callers pass
keepMcp. - The REPL surface itself is gated on
tengu_slate_harbor, which falls back to false, and applies only to thecliandremoteentrypoints. - The wait tool still returns
ready=trueon the existing path, so no behaviour visible to users changes in this build.
rather than advertising them as top-level tools). Returns ready=true when, callable inside the REPL environment (this surface routes MCP tools through the REPL rather than advertising them as top-level tools), The server's tools should now be available., tengu_slate_harbor, isAuthStub, keepMcp
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_slate_harbor Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.248: off
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you