{"version":"2.1.271","anchor":"local-workflow-tool-call-path-renames-only-no-behavior-cha","canonical_anchor":"local-workflow-tool-call-path-renames-only-no-behavior-cha","heading":"Local workflow tool call path: renames only, no behavior change found","tier":"internal","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/local-workflow-tool-call-path-renames-only-no-behavior-cha","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Local workflow tool call path: renames only, no behavior change found\n\nInternal renaming of the local-workflow launch tool's code, no behavior change\n\n**What**\n\nThe code behind the local-workflow launch tool (the internal path that runs the `Workflow` tool and reports it back via `tengu_workflow_launched`) was renamed internally. The gating logic, error messages, and telemetry it sends all appear unchanged.\n\n**Why**\n\nThis is a housekeeping change with no visible effect for anyone using Claude Code.\n\n- Area: Workflows\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}