[FEATURE]: Code Mode execute should return images/attachments to the model #55072

Activity

1. opencode-agent commented on Oct 13, 2026

   

   opencode-agentBot

   on Oct 13, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the suggestion! You're asking for images and other attachments from tools called inside Code Mode execute to reach the model in the same call, plus a way for a script to return or pick specific images explicitly.

   On current v2 (e.g. 2.0.27), part of this already works. execute collects file attachments from nested tool calls and passes them to the model with its result. It only does this when the tool returns the attachment as a base64 data: URI, which is what MCP image content and read produce. Attachments given as https: or file: URIs are currently dropped (see #47458). If you're on v2 and a screenshot tool still only gives back text, could you tell us which tool it is (MCP server or plugin) and your opencode --version?

   There's no way yet for a script to return an image explicitly or choose which collected images are shown; every nested attachment is forwarded. As a partial workaround, a script can call tools.read({ path }) on a saved image to put it in the result. Maintainers will consider the explicit-return and selection part.

   Related issues:

   • v2: plugin tool URL attachments and cancellation signal #47458: Code Mode drops attachments given as https:/file: URIs (only base64 data URIs are kept)
   • V2: revisit tool plugin APIs and execute integration architecture #35364: broader review of how execute integrates with the tool APIs, including attachments
2. remorses commented on Oct 13, 2026

   

   remorses

   on Oct 13, 2026

   ContributorAuthor

   More actions

   My use case is to use a bash cli to screenshot and add that image into the context in one tool call. Now it requires two, adding support for a method read into the js context would allow this to be done faster