diff options
| author | Olcan <[email protected]> | 2025-06-09 08:57:30 -0700 |
|---|---|---|
| committer | GitHub <[email protected]> | 2025-06-09 08:57:30 -0700 |
| commit | 87474e52d7e0f3abcaf74272b11c7b9244d98af5 (patch) | |
| tree | e8ead2ce030823fda16af21a3deafe17c7116afa /docs/cli | |
| parent | c55a1d90120ff8b567e9059466819c4920dc560e (diff) | |
rename shell tool more intuitively as run_shell_command (from historical name of execute_bash_command inherited from terminal tool) (#869)
Diffstat (limited to 'docs/cli')
| -rw-r--r-- | docs/cli/commands.md | 2 | ||||
| -rw-r--r-- | docs/cli/configuration.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/cli/commands.md b/docs/cli/commands.md index 859ebd3c..ad091afc 100644 --- a/docs/cli/commands.md +++ b/docs/cli/commands.md @@ -114,6 +114,6 @@ The `!` prefix provides a powerful way to interact with your system's shell dire - Type your shell commands (e.g., `cd my_project`, `npm run dev`, `cat file.txt`). - Type `!` and press Enter again to exit Shell Mode. -- **Caution for all `!` usage:** Be mindful of the commands you execute, as they have the same permissions and impact as if you ran them directly in your terminal. The Shell Mode feature does not inherently add extra sandboxing beyond what's already configured for the underlying `execute_bash_command` tool. +- **Caution for all `!` usage:** Be mindful of the commands you execute, as they have the same permissions and impact as if you ran them directly in your terminal. The Shell Mode feature does not inherently add extra sandboxing beyond what's already configured for the underlying `run_shell_command` tool. This integrated shell capability allows for seamless switching between AI-assisted tasks and direct system interaction. diff --git a/docs/cli/configuration.md b/docs/cli/configuration.md index 703cf2c4..7c8ff81e 100644 --- a/docs/cli/configuration.md +++ b/docs/cli/configuration.md @@ -70,7 +70,7 @@ When you create a `.gemini/settings.json` file for project-specific settings, or - **Default:** `false` (users will be prompted for most tool calls). - **Behavior:** - If set to `true`, the CLI will bypass the confirmation prompt for tools deemed safe. An indicator may be shown in the UI when auto-accept is active. - - Potentially destructive or system-modifying tools (like `execute_bash_command` or `write_file`) will likely still require confirmation regardless of this setting. + - Potentially destructive or system-modifying tools (like `run_shell_command` or `write_file`) will likely still require confirmation regardless of this setting. - **Example:** `"autoAccept": true` - **`theme`** (string): |