From 33aaae6e204f0f79c73139359d94a7cd9b335d33 Mon Sep 17 00:00:00 2001
From: Levi Neely <141506390+lneely@users.noreply.github.com>
Date: Mon, 20 Apr 2026 22:07:53 +0200
Subject: [PATCH] prompts: tools-elevate explain before running

---
 prompts/tools-elevate.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/prompts/tools-elevate.md b/prompts/tools-elevate.md
index f293867..f7a436e 100644
--- a/prompts/tools-elevate.md
+++ b/prompts/tools-elevate.md
@@ -11,7 +11,8 @@ execute_code: steps=[{code: "systemctl restart nginx", elevated: true}]
 ```
 
 **Constraints**:
+- Before running an elevated step, briefly explain in your response what the command does and why it requires elevation. The user must approve the request — give them enough context to make that decision.
 - `elevated: true` is a per-step flag — apply it only to steps that actually need it; other steps in the same pipeline run normally inside the sandbox.
 - Only bash is supported for elevated steps.
 - Elevation may not be available on all systems; if absent, the step fails with "elevation not available". Do not assume it is always present.
-- Elevated steps block until the user approves or denies the request — this is expected, not an error. Use elevation whenever the task requires it; the prompt is the user's opportunity to review the action.
+- Elevated steps block until the user approves or denies the request — this is expected, not an error.