You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
TUI permission prompt for MCP tools doesn't show the call arguments #60350
The arguments (which issue, what the comment says) are not shown anywhere, so approving a write means approving it blind. The tool line in the transcript above the prompt leaves out object arguments too.
Since #51062 the MCP wrapper passes the call arguments as metadata.input, so the data reaches the prompt. The fallback branch in packages/tui/src/util/permission.ts just doesn't render it. #51519 is the same problem in the web/desktop dock, and #50234 the general version of it.
Thanks for the clear report and for pointing to the exact code, @rmcilraith!
You're asking for the TUI permission prompt (and the tool line in the transcript) to show the arguments of an MCP tool call, so that approving a write isn't done blind. I checked current dev. The MCP wrapper does pass the arguments as metadata.input (since #51062), but the generic branch in packages/tui/src/util/permission.ts was only ever built to show the tool name. Since the prompt is working as it was written, I've filed this as a feature request rather than a bug. Maintainers will consider it.
This can't be done as a plugin today: the TUI plugin API has no slot for the permission prompt and no hook for how a tool call's arguments are shown.
The fallback branch lists each argument under the tool name (issueId: ENG-1, body: Looks good), from the tool part input or metadata.input. Objects are shown as one line of JSON. It's about 10 lines plus a test, and tools with their own layout (edit, shell, webfetch, ...) are unchanged. Happy to open a PR or change the approach.
Activity
opencodejr commentedon Oct 29, 2026
Thanks for the clear report and for pointing to the exact code, @rmcilraith!
You're asking for the TUI permission prompt (and the tool line in the transcript) to show the arguments of an MCP tool call, so that approving a write isn't done blind. I checked current
dev. The MCP wrapper does pass the arguments asmetadata.input(since #51062), but the generic branch inpackages/tui/src/util/permission.tswas only ever built to show the tool name. Since the prompt is working as it was written, I've filed this as a feature request rather than a bug. Maintainers will consider it.This can't be done as a plugin today: the TUI plugin API has no slot for the permission prompt and no hook for how a tool call's arguments are shown.
Related issues:
*, not the tool name #51519: the web/desktop MCP permission prompt shows only*, not the tool namermcilraith commentedon Oct 29, 2026
I have a small fix ready if a maintainer wants it: dev...rmcilraith:opencode:fix/tui-mcp-permission-args
The fallback branch lists each argument under the tool name (
issueId: ENG-1,body: Looks good), from the tool part input ormetadata.input. Objects are shown as one line of JSON. It's about 10 lines plus a test, and tools with their own layout (edit, shell, webfetch, ...) are unchanged. Happy to open a PR or change the approach.