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
disableQueryright 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
disableQuerybefore auto-resuming orphaned agents or workflows, and before prompting about a stale resume, skipping both when it's set. - The command-registry gained a
filterCommandsoption 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
disableQueryandfilterCommandsinto 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.
Names in the bundledisableQueryfilterCommands
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What disableQuery and filterCommands actually do or enable for a user isn't stated in the evidence.