|
@@ -3,8 +3,8 @@ Executes a given bash command in a persistent shell session with optional timeou
|
|
|
Before executing the command, please follow these steps:
|
|
Before executing the command, please follow these steps:
|
|
|
|
|
|
|
|
1. Directory Verification:
|
|
1. Directory Verification:
|
|
|
- - If the command will create new directories or files, first use the LS tool to verify the parent directory exists and is the correct location
|
|
|
|
|
- - For example, before running "mkdir foo/bar", first use LS to check that "foo" exists and is the intended parent directory
|
|
|
|
|
|
|
+ - If the command will create new directories or files, first use the List tool to verify the parent directory exists and is the correct location
|
|
|
|
|
+ - For example, before running "mkdir foo/bar", first use List to check that "foo" exists and is the intended parent directory
|
|
|
|
|
|
|
|
2. Command Execution:
|
|
2. Command Execution:
|
|
|
- Always quote file paths that contain spaces with double quotes (e.g., cd "path with spaces/file.txt")
|
|
- Always quote file paths that contain spaces with double quotes (e.g., cd "path with spaces/file.txt")
|
|
@@ -21,7 +21,7 @@ Usage notes:
|
|
|
- You can specify an optional timeout in milliseconds (up to 600000ms / 10 minutes). If not specified, commands will timeout after 120000ms (2 minutes).
|
|
- 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 in 5-10 words.
|
|
- It is very helpful if you write a clear, concise description of what this command does in 5-10 words.
|
|
|
- If the output exceeds 30000 characters, output will be truncated before being returned to you.
|
|
- If the output exceeds 30000 characters, output will be truncated before being returned to you.
|
|
|
- - VERY IMPORTANT: You MUST avoid using search commands like `find` and `grep`. Instead use Grep, Glob, or Task to search. You MUST avoid read tools like `cat`, `head`, `tail`, and `ls`, and use Read and LS to read files.
|
|
|
|
|
|
|
+ - VERY IMPORTANT: You MUST avoid using search commands like `find` and `grep`. Instead use Grep, Glob, or Task to search. You MUST avoid read tools like `cat`, `head`, `tail`, and `ls`, and use Read and List to read files.
|
|
|
- If you _still_ need to run `grep`, STOP. ALWAYS USE ripgrep at `rg` (or /usr/bin/rg) first, which all opencode users have pre-installed.
|
|
- If you _still_ need to run `grep`, STOP. ALWAYS USE ripgrep at `rg` (or /usr/bin/rg) first, which all opencode users have pre-installed.
|
|
|
- When issuing multiple commands, use the ';' or '&&' operator to separate them. DO NOT use newlines (newlines are ok in quoted strings).
|
|
- When issuing multiple commands, use the ';' or '&&' operator to separate them. DO NOT use newlines (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.
|
|
- 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.
|