{"version":"2.1.260","anchor":"bashpowershell-telemetry-now-records-whether-shell-dispatch","canonical_anchor":"bashpowershell-telemetry-now-records-whether-shell-dispatch","heading":"Bash\/PowerShell telemetry now records whether shell dispatch was user-typed","tier":"internal","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/bashpowershell-telemetry-now-records-whether-shell-dispatch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Bash\/PowerShell telemetry now records whether shell dispatch was user-typed\n\nBash\/PowerShell telemetry and sandbox checks now track whether the user typed the command directly.\n\nThe `tengu_bash_tool_command_executed` and `tengu_powershell_tool_command_executed`\/`failed` telemetry events now include a `user_typed_shell_dispatch` field, and sandbox policy checks take a matching `userTypedShellDispatch` flag to distinguish commands the user typed directly from ones issued by a tool. When a command runs through bash-mode dispatch outside a recognized Claude Code session kind, its tool input now carries `userTypedShellDispatch: true`.\n\n- Area: Sandbox\n- Names: `userTypedShellDispatch`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}