From cea2f2faffbc306fb896e953c85a86258755557d Mon Sep 17 00:00:00 2001 From: iris Date: Sat, 4 Jul 2026 12:42:29 +0200 Subject: [PATCH] docs(terminal-rendering): expand fmtToolUse description to cover new cases The renderer dispatch section only mentioned recv and Bash as fmtToolUse examples. Update the description to cover the full range: matrix tools, remind, scheduling, and the fmtArgsGeneric fallback. --- docs/terminal-rendering.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/terminal-rendering.md b/docs/terminal-rendering.md index c77207ec..32da78cb 100644 --- a/docs/terminal-rendering.md +++ b/docs/terminal-rendering.md @@ -121,10 +121,12 @@ suffix, so the terminal degrades cleanly against older event shapes. `renderRichToolUse` (Write/Edit/send/ask/answer get custom renderings); on miss fall through to a flat `.tool-use` row with `fmtToolUse → fmtArgsGeneric`. - `fmtToolUse` surfaces the salient arg per built-in tool — - e.g. `recv` shows `wait s` / `max ` when set (bare - `recv()` otherwise), `Bash` flags `[bg]` for - `run_in_background` commands. + `fmtToolUse` surfaces the salient arg per built-in tool: + `recv` shows `wait s` / `max ` when set; `Bash` + flags `[bg]`; `remind` shows `+Xm "preview"`; matrix + tools show `→ /: "body"` or ` [limit]`; + scheduling tools show `#id · fields`; `fmtArgsGeneric` + handles anything else. 4. `type == "user"` → walk `message.content[]` for `tool_result`; `renderToolResult` correlates via `tool_use_id → toolNameById` to default-open `recv`