From 15ae3f24babccf42f43be5028bf8c60c05a6beaf Mon Sep 17 00:00:00 2001
From: Fahad <fahad@2doapp.com>
Date: Sun, 5 Oct 2025 11:08:58 +0400
Subject: [PATCH] fix: --yolo needed for running shell commands, documentation
 added

---
 conf/cli_clients/gemini.json |  8 ++++++--
 docs/tools/clink.md          | 10 +++++-----
 2 files changed, 11 insertions(+), 7 deletions(-)

diff --git a/conf/cli_clients/gemini.json b/conf/cli_clients/gemini.json
index 093572e..d9d39e4 100644
--- a/conf/cli_clients/gemini.json
+++ b/conf/cli_clients/gemini.json
@@ -1,7 +1,11 @@
 {
   "name": "gemini",
   "command": "gemini",
-  "additional_args": ["--telemetry", "false"],
+  "additional_args": [
+    "--telemetry",
+    "false",
+    "--yolo"
+  ],
   "env": {},
   "roles": {
     "default": {
@@ -10,7 +14,7 @@
     },
     "planner": {
       "prompt_path": "systemprompts/clink/gemini_planner.txt",
-      "role_args": ["--experimental-acp"]
+      "role_args": []
     },
     "codereviewer": {
       "prompt_path": "systemprompts/clink/gemini_codereviewer.txt",
diff --git a/docs/tools/clink.md b/docs/tools/clink.md
index 7039476..bbf9355 100644
--- a/docs/tools/clink.md
+++ b/docs/tools/clink.md
@@ -114,16 +114,18 @@ Clink configurations live in `conf/cli_clients/`. The default `gemini.json` incl
 {
   "name": "gemini",
   "command": "gemini",
-  "additional_args": ["--telemetry", "false"],
+  "additional_args": ["--telemetry", "false", "--yolo"],
   "roles": {
     "planner": {
       "prompt_path": "systemprompts/clink/gemini_planner.txt",
-      "role_args": ["--experimental-acp"]
+      "role_args": []
     }
   }
 }
 ```
 
+> **Why `--yolo`?** The Gemini CLI currently requires automatic approvals to execute its own tools (for example `run_shell_command`). Without the flag it errors with `Tool "run_shell_command" not found in registry`. See [issue #5382](https://github.com/google-gemini/gemini-cli/issues/5382) for more details.
+
 **Adding new CLIs**: Drop a JSON config into `conf/cli_clients/` and create role prompts in `systemprompts/clink/`.
 
 ## When to Use Clink vs Other Tools
@@ -133,9 +135,7 @@ Clink configurations live in `conf/cli_clients/`. The default `gemini.json` incl
 - **Use `planner`** for: Zen's native planning workflows with step validation
 - **Use `codereview`** for: Zen's structured code review with severity levels
 
-**CAUTION**: `clink` opens additional doors but not without additional risk. Configuration arguments like `--approval-mode yolo` in `conf/cli_clients/gemini.json` bypass safety
-prompts and should only be used when you're certain the operations are safe.
-Review your role configurations carefully before enabling automated execution modes. You can add safeguards and guardrails within role-specific system prompts (in `systemprompts/clink/`) to restrict or guide the external CLI's behavior.
+**CAUTION**: `clink` opens additional doors but not without additional risk. Running Gemini with `--yolo` auto-approves CLI actions (needed for shell edits) and should only be used when you trust the target workspace. Review your role configuration and consider tightening prompts if you need additional guardrails.
 
 ## Setup Requirements