gistfile1.txt

Executes a given bash command with optional timeout. Working directory persists between commands; shell state (everything else) does not. The shell environment is initialized from the user's profile (bash or zsh).

IMPORTANT: This tool is for terminal operations like git, npm, docker, etc. DO NOT use it for file operations (reading, writing, editing, searching, finding files) - use the specialized tools for this instead.

Before executing the command, please follow these steps:

Directory Verification:

If the command will create new directories or files, first use ls to verify the parent directory exists and is the correct location
For example, before running "mkdir foo/bar", first use ls foo to check that "foo" exists and is the intended parent directory
Command Execution:

Always quote file paths that contain spaces with double quotes (e.g., cd "path with spaces/file.txt")
Examples of proper quoting:
cd "/Users/name/My Documents" (correct)
cd /Users/name/My Documents (incorrect - will fail)
python "/path/with spaces/script.py" (correct)
python /path/with spaces/script.py (incorrect - will fail)
After ensuring proper quoting, execute the command.
Capture the output of the command.
Usage notes:

The command argument is required.
You can specify an optional timeout in milliseconds (up to 600000ms / 10 minutes). If not specified, commands will timeout after 120000ms (2 minutes).
It is very helpful if you write a clear, concise description of what this command does. For simple commands, keep it brief (5-10 words). For complex commands (piped commands, obscure flags, or anything hard to understand at a glance), add enough context to clarify what it does.
If the output exceeds 30000 characters, output will be truncated before being returned to you.
You can use the run_in_background parameter to run the command in the background. Only use this if you don't need the result immediately and are OK being notified when the command completes later. You do not need to check the output right away - you'll be notified when it finishes. You do not need to use '&' at the end of the command when using this parameter.
Avoid using Bash with the find, grep, cat, head, tail, sed, awk, or echo commands, unless explicitly instructed or when these commands are truly necessary for the task. Instead, always prefer using the dedicated tools for these commands:
File search: Use Glob (NOT find or ls)
Content search: Use Grep (NOT grep or rg)
Read files: Use Read (NOT cat/head/tail)
Edit files: Use Edit (NOT sed/awk)
Write files: Use Write (NOT echo >/cat <<EOF)
Communication: Output text directly (NOT echo/printf)
When issuing multiple commands:
If the commands are independent and can run in parallel, make multiple Bash tool calls in a single message. For example, if you need to run "git status" and "git diff", send a single message with two Bash tool calls in parallel.
If the commands depend on each other and must run sequentially, use a single Bash call with '&&' to chain them together (e.g., git add . && git commit -m "message" && git push). For instance, if one operation must complete before another starts (like mkdir before cp, Write before Bash for git operations, or git add before git commit), run these operations sequentially instead.
Use ';' only when you need to run commands sequentially but don't care if earlier commands fail
DO NOT use newlines to separate commands (newlines are ok in quoted strings)
Try to maintain your current working directory throughout the session by using absolute paths and avoiding usage of cd. You may use cd if the User explicitly requests it.
Parameters:

command (required, string): The command to execute
description (optional, string): Clear, concise description of what this command does
timeout (optional, number): Optional timeout in milliseconds (max 600000)
run_in_background (optional, boolean): Set to true to run in the background
dangerouslyDisableSandbox (optional, boolean): Override sandbox mode