{"version":"2.1.271","anchor":"powershell-tool-implementation-renamedreshuffled-with-no-ap","canonical_anchor":"powershell-tool-implementation-renamedreshuffled-with-no-ap","heading":"PowerShell tool implementation renamed\/reshuffled with no apparent logic change","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/powershell-tool-implementation-renamedreshuffled-with-no-ap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### PowerShell tool implementation renamed\/reshuffled with no apparent logic change\n\nThe PowerShell tool's internal code was renamed and reorganized with no behavior change found\n\n**What**\n\nThe code behind Claude Code's PowerShell command-execution tool was renamed internally (helper function names, error classes, and telemetry field names such as `tengu_powershell_tool_command_failed`), but the actual control flow, error handling, and telemetry fields it reports appear unchanged.\n\n**Why**\n\nThis is internal housekeeping. There is nothing for a user to notice or act on here.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}