Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.275 ·

New disableQuery flag and filterCommands hook wired through the session engine

A new disableQuery flag can short-circuit turns and resume behavior, alongside a new filterCommands hook for the command list

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaSlash Commandswhat it touches
KindInternal Changesin v2.1.275,
Group of 4 Under the hood No documentation found

A new disableQuery flag can short-circuit turns and resume behavior, alongside a new filterCommands hook for the command list

What

A new disableQuery flag and a new filterCommands hook were added and threaded through several parts of the session engine:

  • The main query-run loop now checks disableQuery right after session-start hooks; if set (alongside a new-turn or queued-input condition), it returns early without running the turn.
  • Session resume/adopt logic now checks disableQuery before auto-resuming orphaned agents or workflows, and before prompting about a stale resume, skipping both when it's set.
  • The command-registry gained a filterCommands option and a memoized helper to filter the command list by a predicate, for plugins or other consumers to narrow which commands are shown.
  • The main session component now accepts and passes through both disableQuery and filterCommands into the session engine, command-registry service, and turn controller.

Why

Together these let something embedding or driving a session suppress normal query/turn execution and restrict which commands are available, useful for building restricted or specialized session modes.

Read from
Names in the bundlefilterCommands
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding shows the filtering machinery added but not which plugin-facing feature or command actually uses it.

See this entry in the whole of v2.1.275 →

Feedback