Repository navigation
Conversation
Contributor
|
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
Fixes anomalyco#19549 Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
Fixes anomalyco#19549 Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
lu-zero
force-pushed
the
mcp-populate-metadata
branch
from
June 16, 2026 15:02
d40a6c3 to
68a9077
Compare
Contributor
|
This pull request has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window. Feel free to open a new pull request that follows our guidelines. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue for this PR
Fixes #19549
Type of change
What does this PR do?
The MCP tool wrapper in
packages/opencode/src/session/tools.tswas callingctx.askwith hardcoded wildcards:That caused three observable problems:
*instead of the actual MCP tool name (the original report on MCP tools show*instead of actual tool name in permission dialogs #19549).pattern: "*"instead of the tool name, so approving one MCP tool silently approved every MCP tool in the session.serveconsumers received an emptymetadataon thepermission.askedevent, so a host UI couldn't display the tool input or reason about it.The fix aligns the MCP wrapper with the convention used by every other tool (
bash,webfetch,task,read,edit, …): forward the action key as bothpermissionandpatterns/always, and pass the tool's input asmetadata.The
metadatafield is already typedSchema.Record(Schema.String, Schema.Unknown), so MCP tool args (alsoRecord<string, unknown>) fit the schema without any wire-format change.How did you verify your code works?
mcp tool ask publishes tool name and args (regression: #19549)inpackages/opencode/test/session/prompt.test.ts. It registers a fake one-tool MCP layer, subscribes toPermission.Event.AskedviaEventV2Bridge, drives the prompt loop to invoke the tool with{ greeting: "hi" }, and asserts:request.permission === "echo_say"request.patterns === ["echo_say"]request.always === ["echo_say"]request.metadata === { greeting: "hi" }oncereply.bun test test/session/prompt.test.tsfrompackages/opencode/— 55 pre-existing tests pass + the new one, 0 failures.bun typecheckclean.permission.askedevent payload carries the tool arguments.Screenshots / recordings
No UI changes — only the data the existing dock already renders.
Checklist