Support multiple 1Password vaults - #1829
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | 6e5a704 | Aug 28 2026, 08:24 PM |
Contributor
Cloudflare previewTorn down — the PR is closed. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | 6e5a704 | Commit Preview URL Branch Preview URL |
Aug 28 2026, 08:23 PM |
@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: |
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.
The 1Password credential provider was bound to exactly one vault. This makes the vault binding a set, with explicit per-vault addressing.
vaultsarray selected with checkboxes. The old single-vaultIdshape is still read and normalizes to a one-vault list; the next save writes the new shape.op://<vault>/<item>ref, so identically-titled items in different vaults can never collide. There is no precedence order.grouplabel on the generic provider-items surface.statusreportsvaultNamesand flags configured vaults the account can no longer see.Demo
All data below is synthetic (recorded against a stubbed
opCLI).Vault selection:
Item search with per-vault provenance — the same title in two vaults stays unambiguous:
Testing
Plugin unit suite: config round-trip, legacy-blob upgrade, explicit resolution (qualified refs, unique bare match, cross-vault and same-vault ambiguity, not-found). Verified live against a local 1Password with two vaults: connect, edit, picker search, and instant reopen after the stale-while-revalidate change.