Repository navigation
tool.execute.after hook receives raw MCP result instead of assembled output #21146
Description
The tool.execute.after hook fires for MCP tools before the output text is assembled from the raw CallToolResult.content[] array. Plugins hooking this event receive the raw MCP SDK result (which has a content array of {type, text} objects) instead of the {title, output, metadata} shape declared in the Hooks type definition.
This means any plugin that tries to read or transform output.output gets undefined, and even if the plugin mutates the raw result, the text assembly rebuilds the output from result.content independently. The hook is effectively a no-op for MCP tool output transformation.
The Hooks type in packages/plugin/src/index.ts declares the output parameter as:
"tool.execute.after": (
input: { tool: string; sessionID: string; callID: string; args: any },
output: { title: string; output: string; metadata: any; attachments?: ... }
) => Promise<void>But the actual call in packages/opencode/src/session/prompt.ts passes the raw MCP result object before text extraction.
Native tools (bash, read, etc.) are not affected — they have their own hook paths that pass the correct shape.
Activity
github-actions commentedon Apr 6, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
tool.execute.afterhook mutations not being reflected correctly in output.If you believe this was flagged incorrectly, please let a maintainer know.