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.
This commit is contained in:
parent
66057a97f7
commit
cea2f2faff
1 changed files with 6 additions and 4 deletions
|
|
@ -121,10 +121,12 @@ suffix, so the terminal degrades cleanly against older event shapes.
|
||||||
`renderRichToolUse` (Write/Edit/send/ask/answer get
|
`renderRichToolUse` (Write/Edit/send/ask/answer get
|
||||||
custom renderings); on miss fall through to a flat
|
custom renderings); on miss fall through to a flat
|
||||||
`.tool-use` row with `fmtToolUse → fmtArgsGeneric`.
|
`.tool-use` row with `fmtToolUse → fmtArgsGeneric`.
|
||||||
`fmtToolUse` surfaces the salient arg per built-in tool —
|
`fmtToolUse` surfaces the salient arg per built-in tool:
|
||||||
e.g. `recv` shows `wait <N>s` / `max <N>` when set (bare
|
`recv` shows `wait <N>s` / `max <N>` when set; `Bash`
|
||||||
`recv()` otherwise), `Bash` flags `[bg]` for
|
flags `[bg]`; `remind` shows `+Xm "preview"`; matrix
|
||||||
`run_in_background` commands.
|
tools show `→ <room>/<user>: "body"` or `<room> [limit]`;
|
||||||
|
scheduling tools show `#id · fields`; `fmtArgsGeneric`
|
||||||
|
handles anything else.
|
||||||
4. `type == "user"` → walk `message.content[]` for
|
4. `type == "user"` → walk `message.content[]` for
|
||||||
`tool_result`; `renderToolResult` correlates via
|
`tool_result`; `renderToolResult` correlates via
|
||||||
`tool_use_id → toolNameById` to default-open `recv`
|
`tool_use_id → toolNameById` to default-open `recv`
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue