Sweep 22 Sep 2026 · 15:52Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Writing the changelog v2.1.280 merge candidates · 1/5 waiting for the next tick
Tool description

Bash, as sent

SDK-CLI Agent SDK, print mode, v2.1.270. One model string produces this prompt.

As described in the slash command: /security-review request, not the ordinary one.

This tool has no description in the capture before this one on this arm, so the left gutter is empty rather than marking every line as new.

Lines131,229 characters
Movednothing to compare against
Reach1model strings receive this description
Copies1distinct descriptions under this name
Parameters51 of them required Tools in captureall of themevery description on this arm
Plain text · sha256 52e234f4899e

The description, line by line

13 lines One line number, because there is no previous capture to number against.
1 Executes a bash command and returns its output.
2
3 - Working directory persists between calls, but prefer absolute paths — `cd` in a compound command can trigger a permission prompt. Shell state (env vars, functions) does not persist; the shell is initialized from the user's profile.
4 - IMPORTANT: Avoid using this tool to run `cat`, `head`, `tail`, `sed`, `awk`, or `echo` commands, unless explicitly instructed or after you have verified that a dedicated tool cannot accomplish your task. Instead, use the appropriate dedicated tool as this will provide a much better experience for the user.
5 - Command output is displayed to you, not reliably to the user.
6 - `timeout` is in milliseconds: default 120000, max 600000.
7 - `run_in_background` runs the command detached: it keeps running across turns and re-invokes you when it exits. No `&` needed.
8
9 # Git
10 - Interactive flags (`-i`, e.g. `git rebase -i`, `git add -i`) are not supported in this environment.
11 - Use the `gh` CLI for GitHub operations (PRs, issues, API).
12 - Commit or push only when the user asks. If on the default branch, branch first.
13 - End git commit messages and PR bodies with the attribution lines given in the conversation's system-reminder, when one is present.

What it accepts

5 parameters The JSON parameter schema sent beside this description, 1,702 characters of it. Name, type, then whether the client marked it required.
command string required The command to execute
dangerouslyDisableSandbox boolean optional Set this to true to dangerously override sandbox mode and run commands without sandboxing.
description string optional Clear, concise description of what this command does in active voice. Never use words like "complex" or "risk" in the description - just describe what it does. Say what the command does in plain words: do not echo the command's text, its flags, or file paths - the user reads this description, often without seeing the command. For simple commands (git, npm, standard CLI tools), keep it brief (5-10 words): - ls → "List files in current directory" - git status → "Show working tree status" - npm install → "Install package dependencies" For commands that are harder to parse at a glance (piped commands, obscure flags, etc.), add enough context to clarify what it does: - find . -name "*.tmp" -exec rm {} \; → "Find and delete all .tmp files recursively" - git reset --hard origin/main → "Discard all local changes and match remote main" - curl -s url | jq '.data[]' → "Fetch JSON from URL and extract data array elements"
run_in_background boolean optional Set to true to run this command in the background.
timeout number optional Optional timeout in milliseconds (max 600000)

sha256 fac705c1b3a9 · the schema as the client sent it:

{ "$schema": "https://json-schema.org/draft/2020-12/schema", "additionalProperties": false, "properties": { "command": { "description": "The command to execute", "type": "string" }, "dangerouslyDisableSandbox": { "description": "Set this to true to dangerously override sandbox mode and run commands without sandboxing.", "type": "boolean" }, "description": { "description": "Clear, concise description of what this command does in active voice. Never use words like \"complex\" or \"risk\" in the description - just describe what it does.\n\nSay what the command does in plain words: do not echo the command's text, its flags, or file paths - the user reads this description, often without seeing the command.\n\nFor simple commands (git, npm, standard CLI tools), keep it brief (5-10 words):\n- ls \u2192 \"List files in current directory\"\n- git status \u2192 \"Show working tree status\"\n- npm install \u2192 \"Install package dependencies\"\n\nFor commands that are harder to parse at a glance (piped commands, obscure flags, etc.), add enough context to clarify what it does:\n- find . -name \"*.tmp\" -exec rm {} \\; \u2192 \"Find and delete all .tmp files recursively\"\n- git reset --hard origin/main \u2192 \"Discard all local changes and match remote main\"\n- curl -s url | jq '.data[]' \u2192 \"Fetch JSON from URL and extract data array elements\"", "type": "string" }, "run_in_background": { "description": "Set to true to run this command in the background.", "type": "boolean" }, "timeout": { "description": "Optional timeout in milliseconds (max 600000)", "type": "number" } }, "required": [ "command" ], "type": "object" }