Constant BASH 

pub const BASH: &str = "Executes a given bash command in a persistent shell session with optional timeout, ensuring proper handling and security measures.\n\nAll commands run in the working directory shown in the Environment section above. Use the `workdir` parameter if you need to run a command in a different directory. AVOID using `cd <directory> && <command>` patterns - use `workdir` instead.\n\nIMPORTANT: 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.\n\nBefore executing the command, please follow these steps:\n\n#### Directory Verification\n- If the command will create new directories or files, first use `ls` to verify the parent directory exists and is the correct location\n- For example, before running \"mkdir foo/bar\", first use `ls foo` to check that \"foo\" exists and is the intended parent directory\n\n#### Command Execution\n- Always quote file paths that contain spaces with double quotes (e.g., rm \"path with spaces/file.txt\")\n- Examples of proper quoting:\n  - mkdir \"/Users/name/My Documents\" (correct)\n  - mkdir /Users/name/My Documents (incorrect - will fail)\n  - python \"/path/with spaces/script.py\" (correct)\n  - python /path/with spaces/script.py (incorrect - will fail)\n- After ensuring proper quoting, execute the command.\n- Capture the output of the command.\n\n##### Usage notes\n- The `command` argument is required.\n- You can specify an optional `timeout_ms` in milliseconds (up to 600000ms / 10 minutes). If not specified, commands will timeout after 120000ms (2 minutes).\n- It is very helpful if you write a clear, concise description of what this command does in 5-10 words.\n- If the output exceeds 30000 characters, output will be truncated before being returned to you.\n- 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:\n  - File search: Use Glob (NOT find or ls)\n  - Content search: Use Grep (NOT grep)\n  - Read files: Use Read (NOT cat/head/tail)\n  - Edit files: Use Edit (NOT sed/awk)\n  - Write files: Use Write (NOT echo >/cat <<EOF)\n  - Communication: Output text directly (NOT echo/printf)\n- When issuing multiple commands:\n  - 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.\n  - 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.\n  - Use \';\' only when you need to run commands sequentially but don\'t care if earlier commands fail\n  - DO NOT use newlines to separate commands (newlines are ok in quoted strings)\n- AVOID using `cd <directory> && <command>`. Use the `workdir` parameter to change directories instead.\n  <good-example>\n  Use workdir=\"/foo/bar\" with command: pytest tests\n  </good-example>\n  <bad-example>\n  cd /foo/bar && pytest tests\n  </bad-example>\n";

Bash tool context - shell command execution guidance.