What it is
Internal renaming of the local-workflow launch tool's code, no behavior change
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.271.
Presence across releases
0The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.
First cited
1The earliest release whose published evidence quoted tengu_workflow_launched was v2.1.271, 14 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table above.
Gate readings
0No release here has a gate table behind it for this flag. Most published releases have none at all: the readings exist only for versions the pipeline captured flag state on.
Names beside it
Every feature flag in the inventory starting tengu_workflow, up to twelve of them.
tengu_workflow_authoring_skill_autoloadA bundled workflow-authoring skill loads itself when you mention workflows, and multi-agent runs need your ask. never mined
tengu_workflow_savedYour saved workflows can be listed and stored through a storage backend rather than plain files. never mined
tengu_workflow_schema_lint_enforceNo description from anybody. v2.1.260
tengu_workflows_enabledOne helper now decides whether workflows are off, covering the setting, env var and remote gate. v2.1.146
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.