{"version":"2.1.269","anchor":"tee-added-as-a-supportedsandboxed-bash-builtin","canonical_anchor":"tee-added-to-bash-command-summary-descriptions","heading":"'tee' is now a recognized, sandboxed shell command","tier":"notice","area":"Bash Tool","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/tee-added-as-a-supportedsandboxed-bash-builtin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### 'tee' is now a recognized, sandboxed shell command\n\nThe Bash tool now understands the 'tee' command: it's sandboxed, permission-checked, and described in summaries\n\n**What**\n\n- `tee` is now implemented as a supported shell builtin in the sandbox, piped through the existing `sha*sum`-style handler, and classified as a `write` permission; special device targets (`\/dev\/null`, `\/dev\/stdout`, `\/dev\/stderr`, `\/dev\/tty`) are filtered out of its arguments before permission checks run.\n\n- The command path-validator now special-cases `tee`: a `tee` call with no target paths passes immediately (\"Path validation passed for tee command\") instead of going through the usual working-directory restriction logic.\n\n- The basename-normalizing helper used to detect file-affecting shell commands (previously only `rm`\/`rmdir`) now also matches `tee`, case-insensitively and with a `.exe` suffix stripped.\n\n- `tee` was added to the bash-command-summary descriptions, described as \"write to files in\".\n\n**Why** Previously `tee` wasn't recognized as a file-writing command, so it could bypass the usual write-permission and working-directory checks or produce confusing summaries; now it's treated consistently with other file-writing commands.\n\n- Area: Bash Tool\n- Names: `tee`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}