Verified
Describe the enhancement you want to request
OpenCode's experimental resource endpoint already scans ~/.local/bin/*-axi and serves AXI CLI tool information alongside MCP servers. Currently this data only appears in the MCP status popover but not in the TUI sidebar.
Request: Wire AXI CLI tool data into the TUI sidebar so users can see which AXI tools are available (gh-axi, npm-axi, chrome-devtools-axi, cluster-ops-axi) alongside their MCP servers.
Proposed changes:
- TUI sidebar header changes from "MCP" to "MCP/AXI" when AXI tools are present
- AXI tools render as read-only info items below MCP servers (no toggle switches — AXI tools are filesystem-based, not server processes)
- Add
mcp_resource accessor to TUI plugin adapter
- Add
mcp_resource to TuiState type definition
Why this belongs in OpenCode: This completes the AXI tool visibility story — the backend already scans and serves this data, but the TUI (the primary interface) doesn't show it. Users who have AXI tools installed should see them in the sidebar to understand what tools are available to their agents.
Verified
Describe the enhancement you want to request
OpenCode's experimental resource endpoint already scans
~/.local/bin/*-axiand serves AXI CLI tool information alongside MCP servers. Currently this data only appears in the MCP status popover but not in the TUI sidebar.Request: Wire AXI CLI tool data into the TUI sidebar so users can see which AXI tools are available (gh-axi, npm-axi, chrome-devtools-axi, cluster-ops-axi) alongside their MCP servers.
Proposed changes:
mcp_resourceaccessor to TUI plugin adaptermcp_resourcetoTuiStatetype definitionWhy this belongs in OpenCode: This completes the AXI tool visibility story — the backend already scans and serves this data, but the TUI (the primary interface) doesn't show it. Users who have AXI tools installed should see them in the sidebar to understand what tools are available to their agents.