Extend the plugin seam for virtual-tool plugins#1361
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | a80af29 | Commit Preview URL Branch Preview URL |
Jul 08 2026, 10:49 PM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | a80af29 | Jul 08 2026, 10:50 PM |
Contributor
Cloudflare previewTorn down — the PR is closed. |
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/codemode-core
@executor-js/runtime-quickjs
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
executor
commit: |
RhysSullivan
force-pushed
the
apps-plugin-seam
branch
from
9842e2f to
1e956a5
Compare
This was referenced Jul 8, 2026
RhysSullivan
force-pushed
the
apps-plugin-seam
branch
from
1e956a5 to
946788b
Compare
Plugins that publish higher-level tools over existing integrations need three things the seam did not offer: a way to invoke another catalog tool inside the same request context (ctx.execute, keeping policy, approval, and credential resolution in the core path), opaque provider-item storage for values they own that are not connections, and hooks to project tool schemas at read time and clean up on integration removal. Binding failures (a caller naming an unknown or mismatched connection) now surface as a binding_error tool result naming the role and integration instead of an opaque internal tool error.
RhysSullivan
force-pushed
the
apps-plugin-seam
branch
from
946788b to
a80af29
Compare
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
1 participant
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.
Plugins that publish higher-level tools over existing integrations (custom tools, upcoming apps work) need a few things the plugin seam did not offer: invoking another catalog tool inside the same request context via ctx.execute, opaque provider-item storage, a schema projection hook, and an integration-removal hook.
Binding failures now surface as a binding_error tool result naming the role and integration instead of an opaque internal error.
Stack