You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
WorkflowsArea: what it touches
ImprovementsKind: in v2.1.292,
ImprovementsSection of the release
Unclear Which hook event a plugin must handle to refuse a workflow agent is not shown.
What
A workflow can start agents, separate Claude instances that each handle part of the job. Starting one now goes through a hook first. A hook is a script or plugin that runs at set points in Claude Code. If the hook refuses, the agent is not started and the workflow fails with an error that begins "Workflow agent spawn denied by a plugin".
For workflow agents, refusing is the only thing a hook can do. Any other fields the hook returns are ignored.
Why
Plugin authors can block workflow agents from launching, which gives them control over what a workflow is allowed to start.
Read from
Feature flag
tengu_workflow_schema_lint_enforceNot enough to say
Nothing 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.292: 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.
