[codex] refactor plugin catalogs and registration#214
Draft
RhysSullivan wants to merge 1 commit intomainfrom
Draft
[codex] refactor plugin catalogs and registration#214RhysSullivan wants to merge 1 commit intomainfrom
RhysSullivan wants to merge 1 commit intomainfrom
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | 3f22368 | Commit Preview URL Branch Preview URL |
Apr 12 2026, 10:59 PM |
@executor/sdk
@executor/plugin-file-secrets
@executor/plugin-google-discovery
@executor/plugin-graphql
@executor/plugin-keychain
@executor/plugin-mcp
@executor/plugin-onepassword
@executor/plugin-openapi
commit: |
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.
What changed
This refactors plugin composition so hosts register first-party plugins in one place instead of repeating the same lists across runtime setup, API wiring, routes, and shell components.
It introduces a shared
@executor/host-pluginspackage for first-party source plugin metadata and server-side plugin wiring, plus a React-side plugin catalog provider so source and secret-provider plugins are registered once at the app root.Why this changed
The plugin system had good runtime primitives, but the host integration points were still hand-assembled in multiple files. That made it easy for runtime, API, and UI plugin registration to drift apart and added a lot of boilerplate whenever a plugin changed.
User and developer impact
Hosts now define plugin participation once at the root/provider and once in the server registry layer.
This reduces repeated wiring in local and cloud, removes plugin catalog prop plumbing from page and shell components, and makes the remaining plugin registration points much clearer.
Root cause
The architecture separated runtime plugins, API groups, and React source/secret-provider plugins, but the host apps were manually stitching those pieces together in parallel instead of consuming a shared manifest.
Validation
bun installbunx tsc --noEmit -p packages/hosts/plugins/tsconfig.jsonbunx tsc --noEmit -p apps/cloud/tsconfig.jsonbunx tsc --noEmit -p apps/local/tsconfig.jsonstill stops on the pre-existing warning inpackages/core/storage-file/src/tool-registry.ts:122