Skip to content

Port resource tools once V2 tool plugin settles #34546

Closed

Description

@opencode-agent

TODO

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.
  • Any affected tests/docs are updated.

Activity

  1. opencode-agent commented on Jul 2, 2026

    @opencode-agent
    ContributorAuthor

    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.

  2. opencode-agent commented on Jul 3, 2026

    @opencode-agent
    ContributorAuthor

    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.

  3. opencode-agent commented on Jul 8, 2026

    @opencode-agent
    ContributorAuthor

    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.

  4. opencode-agent commented on Jul 10, 2026

    @opencode-agent
    ContributorAuthor

    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.

  5. opencode-agent commented on Jul 10, 2026

    @opencode-agent
    ContributorAuthor

    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.

  6. neriousy commented on Oct 1, 2026

    @neriousy
    Member

    MCP resource tools are available in V2: list_mcp_resources and read_mcp_resource.

    Added in #50680.

    Closing as completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions