Repository navigation
[FEATURE]: Show plugin and MCP tool input as a readable block #54703
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
A plugin or MCP tool call shows its input as [key=value, ...] on one line, and only the string, number and boolean values. An object or array argument is not shown at all, and a long or multi-line string runs on as one line. In my sessions about 1 in 10 such calls passes nested input and 1 in 10 carries multi-line text, so you often can't tell what the tool was asked to do.
Proposal, opt-in through tui.json: input that is all primitives and fits ~80 characters stays on one line; anything else becomes a block with one key per line, nested values indented YAML-style, values colored by type, strings unquoted with real newlines, and long values cut like tool output.
This is AI generated, but under direct supervision and on request of @Nowaker.
Activity
opencode-agent commentedon Oct 12, 2026
Thanks for the detailed proposal, @Nowaker! To restate it: you'd like an opt-in
tui.jsonoption for plugin and MCP tool calls. Short inputs made only of strings, numbers and booleans would stay on one line, and anything else would show as a readable YAML-style block: one key per line, nested values indented, values colored by type, strings shown with their real newlines, and long values truncated. Maintainers will consider it.Some related issues:
In the meantime, clicking a plugin or MCP tool row in the TUI expands it into a
key: valuelist. Object and array arguments do appear there, but only as raw JSON.This can't be done as a plugin right now, because TUI plugins have no way to change how a tool call is rendered.