abbyswag/qwen-code
1
0
Fork 0
mirror of https://github.com/QwenLM/qwen-code.git synced 2025-12-22 01:37:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

rename shell tool more intuitively as run_shell_command (from historical name of execute_bash_command inherited from terminal tool) (#869)

Browse Source
This commit is contained in:
Olcan
2025-06-09 08:57:30 -07:00
committed by GitHub
parent c55a1d9012
commit 87474e52d7
11 changed files with 70 additions and 70 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/architecture.md
View File

@@ -44,7 +44,7 @@ A typical interaction with the Gemini CLI follows this general flow:
5. **Tool Execution (if applicable):**
- If the Gemini API requests a tool, the Core package prepares to execute it.
- **User Confirmation for Potentially Impactful Tools:** If the requested tool can modify the file system (e.g., file edits, writes) or execute shell commands, the CLI (`packages/cli`) displays a confirmation prompt to the user. This prompt details the tool and its arguments, and the user must approve the execution. Read-only operations (e.g., reading files, listing directories) may not always require this explicit confirmation step.
- If confirmed (or if confirmation is not required for the specific tool), the Core package identifies and executes the relevant tool (e.g., `read_file`, `execute_bash_command`).
- If confirmed (or if confirmation is not required for the specific tool), the Core package identifies and executes the relevant tool (e.g., `read_file`, `run_shell_command`).
- The tool performs its action (e.g., reads a file from the disk).
- The result of the tool execution is sent back to the Gemini API by the Core.
- The Gemini API processes the tool result and generates a final response.