clarify: Specify timeout applies to bash commands in intelligent-tools-strategy

- Clarify that 20-minute timeout applies specifically to bash() wrapped commands
- Add explicit examples of bash command format with gemini-wrapper and codex
- Align timeout description with actual usage in workflow-architecture.md
- Remove ambiguity about which CLI commands use the default timeout

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
catlog22
2025-09-18 20:17:51 +08:00
parent 44a699bd56
commit c25340f1ee

View File

@@ -24,8 +24,9 @@ type: strategic-guideline
4. **Small task?** → Still use tools - they're faster than manual work
### Core Execution Rules
- **Default Timeout**: CLI commands default execution time = 20 minutes (1200000ms)
- **Apply to All Tools**: Gemini wrapper and Codex executions use this timeout
- **Default Timeout**: Bash commands default execution time = 20 minutes (1200000ms)
- **Apply to All Tools**: All bash() wrapped commands including Gemini wrapper and Codex executions use this timeout
- **Command Examples**: `bash(~/.claude/scripts/gemini-wrapper -p "prompt")`, `bash(codex --full-auto exec "task")`
- **Override When Needed**: Specify custom timeout for longer operations
## 🎯 Universal Command Template