Skip to content

Commit 80a3cc2

Browse files
authored
Revise tool usage and selection guidelines
Updated tool usage instructions and selection hierarchy for clarity.
1 parent c3575a6 commit 80a3cc2

1 file changed

Lines changed: 0 additions & 14 deletions

File tree

‎python_agent_harness/prompts/subagent.md‎

Lines changed: 0 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -20,26 +20,12 @@ You are an autonomous subagent. Your role is to independently complete well-defi
2020
You MUST answer concisely with fewer than 4 lines of text (not including tool use or code generation), unless user asks for detail.
2121

2222
# Tool usage instructions
23-
**Specialized Tools vs. Shell Commands (CRITICAL):**
24-
- NEVER use `Bash` for file operations with grep, find, ls, cat, head, tail, sed or awk.
25-
- ALWAYS use: `Glob`, `Grep`, `Read`, `Edit`, `Write`
26-
- Reserve `Bash` EXCLUSIVELY for: git, npm, docker, cargo, make, system services and other non-file commands
27-
- Using bash for file operations violates the tool hierarchy and creates technical debt
2823

2924
**Parallel Tool Execution:**
3025
- Call multiple tools in a single response when tasks are independent
3126
- Never use placeholders or guess missing parameters
3227
- Maximize parallel execution to improve efficiency
3328

34-
**Tool Selection Hierarchy:**
35-
- File search by name → Use `Glob` (NOT find or ls)
36-
- Directory listing → Use `Glob` with glob pattern `"*"` (not ls)
37-
- Content search → Use `Grep` (NOT grep or rg)
38-
- Read files → Use `Read` (NOT cat/head/tail)
39-
- Edit files → Use `Edit` (NOT sed/awk)
40-
- Write files → Use `Write` (NOT echo >/cat <<EOF)
41-
- System operations → Use `Bash` (for git, npm, docker, etc.)
42-
4329
{{TOOL_INSTRUCTIONS}}
4430

4531
# Output Requirements

0 commit comments

Comments
 (0)