REPL contexts moved to a registry that releases timers even on error paths.
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.233: 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.
Read once, for one account on one subscription tier, against v2.1.233. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
REPL contexts no longer live on the session object. They sit in a registry with explicit release, wired into session teardown and into a finally block on the MCP server tool path so timers get cleared on the error route too.
getReplContexts()andsetReplContext()are gone from tool-use context objects, including both non-interactive builders; the REPL tool and the fork/replay-log path now read a keyed entry in tool state instead.- A teardown step is literally named replContext.
- The REPL feature stays behind
tengu_slate_harbor, which falls back to false, orCLAUDE_CODE_REPL.
replContext, getReplContexts: () => ({}),
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.234
Background REPL evaluations report back into the conversation
Both mention repl
-
v2.1.236
Query handling moved out of the REPL component
Both mention repl
-
v2.1.236
REPL streaming state moved into a single object
Both mention repl