From 32566a16a5bfe43eb86464d9a34bb6c188e63a34 Mon Sep 17 00:00:00 2001
From: Aiden Cline <63023139+rekram1-node@users.noreply.github.com>
Date: Sat, 6 Dec 2025 17:30:10 -0600
Subject: [PATCH] Revise bash.txt for command usage guidelines

Updated examples to avoid using 'cd' and clarified command usage.
---
 packages/opencode/src/tool/bash.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/opencode/src/tool/bash.txt b/packages/opencode/src/tool/bash.txt
index a0f38fe80d..3541249675 100644
--- a/packages/opencode/src/tool/bash.txt
+++ b/packages/opencode/src/tool/bash.txt
@@ -26,8 +26,8 @@ Usage notes:
   - If you _still_ need to run `grep`, STOP. ALWAYS USE ripgrep at `rg` (or /usr/bin/rg) first, which all opencode users have pre-installed.
   - When issuing multiple commands, use the ';' or '&&' operator to separate them. DO NOT use newlines (newlines are ok in quoted strings).
   - Avoid using `cd` to change directories when possible. Instead, set the `workdir` parameter or use absolute paths in your commands.
+    <good-example>
     dir_path="/foo/bar", command="pytest tests"
-    workdir="/foo/bar", command="pytest tests"
     </good-example>
     <good-example>
     pytest /foo/bar/tests