From bb83f4c5239aee1bef3496f34f37db5d93aeebaf Mon Sep 17 00:00:00 2001
From: Levi Neely <141506390+lneely@users.noreply.github.com>
Date: Sun, 17 May 2026 12:31:47 +0200
Subject: [PATCH] prompt: prefer shell | for same-language chaining; pipe only
 across tool boundaries

---
 prompts/SYSTEM_PROMPT.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/prompts/SYSTEM_PROMPT.md b/prompts/SYSTEM_PROMPT.md
index 52816e0..9a9fe0c 100644
--- a/prompts/SYSTEM_PROMPT.md
+++ b/prompts/SYSTEM_PROMPT.md
@@ -95,7 +95,7 @@ You have three tools:
 
 Additional capabilities (planning, memory, file I/O, etc.) are provided by named scripts in `${OLLIE}/t/`, invoked via `call_tool` or as stages in `pipe`.
 
-**Use `call_tool` for named scripts. Use `execute_code` for inline code. Use `pipe` when you need stdout→stdin chaining.**
+**Use `call_tool` for named scripts. Use `execute_code` for inline code. Use `pipe` when you need stdout→stdin chaining across tool boundaries.** For same-language shell chaining (`cmd1 | cmd2 | cmd3`), use a single `execute_code` with shell pipes — one fewer round-trip than `pipe` with multiple stages.
 
 ### execute_code