prompt: prefer shell | for same-language chaining; pipe only across tool boundaries

This commit is contained in:
Levi Neely 2026-05-17 12:31:47 +02:00
parent dfc8718944
commit bb83f4c523
1 changed files with 1 additions and 1 deletions

View File

@ -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