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
Port resource tools once V2 tool plugin settles #34546
Port resource tools once the V2 tool plugin API settles.
Context
Current v2 does not yet have the planned plugin tool surface (ctx.tool.transform(...) / transform-backed tool registry).
There is open architecture/prototype work around plugin/session/tool patterns (for example the plugin-patterns plan), but resource tools should wait until that API shape is stable.
Done when
The settled V2 plugin tool API is identified.
Resource tools are registered through that API instead of the current transitional path.
Update: #34956 migrates the remaining built-in tools to internal plugins. Resource tools are still a separate follow-up, but this reduces the blocker around built-in tools dogfooding the plugin registration surface.
Audit update (2026-07-08): the built-in tool-to-plugin migration is complete via #34956, so that is no longer the blocker. Remaining sequencing is primarily the external/public registration surface in #34489 and tool-result content API in #34709. James and Aiden are both assigned, but the issue does not state a DRI; ownership roles should be clarified before implementation starts.
Audit: resource prerequisites have landed in pieces (#35656 core MCP resources, #35773 resource catalog API), but this issue specifically waits for the settled V2 plugin tool API and resource-tool registration through it. Keeping open.
Additional audit context: MCP resource prerequisites have progressed via PR #35656 (core MCP resources) and PR #35773 (resource catalog API), and PR #35780 is open for attaching resources from the TUI. This issue should stay open for the final resource-tool registration through the settled V2 plugin tool API.
Activity
opencode-agent commentedon Jul 2, 2026
Tracker update from V2 TODO LIST audit (2026-07-02):
Still blocked on the V2 tool/plugin architecture settling.
Relevant current work:
Recommendation: do not start resource-tool porting until #34709/#34805 land and Aiden/Kit confirm the command/tool-plugin sequencing is stable.
opencode-agent commentedon Jul 3, 2026
Update: #34956 migrates the remaining built-in tools to internal plugins. Resource tools are still a separate follow-up, but this reduces the blocker around built-in tools dogfooding the plugin registration surface.
opencode-agent commentedon Jul 8, 2026
Audit update (2026-07-08): the built-in tool-to-plugin migration is complete via #34956, so that is no longer the blocker. Remaining sequencing is primarily the external/public registration surface in #34489 and tool-result content API in #34709. James and Aiden are both assigned, but the issue does not state a DRI; ownership roles should be clarified before implementation starts.
opencode-agent commentedon Jul 10, 2026
Audit: resource prerequisites have landed in pieces (#35656 core MCP resources, #35773 resource catalog API), but this issue specifically waits for the settled V2 plugin tool API and resource-tool registration through it. Keeping open.
opencode-agent commentedon Jul 10, 2026
Additional audit context: MCP resource prerequisites have progressed via PR #35656 (core MCP resources) and PR #35773 (resource catalog API), and PR #35780 is open for attaching resources from the TUI. This issue should stay open for the final resource-tool registration through the settled V2 plugin tool API.
neriousy commentedon Oct 1, 2026
MCP resource tools are available in V2:
list_mcp_resourcesandread_mcp_resource.Added in #50680.
Closing as completed.