1Password vault integration: under consideration
We’re considering a 1Password source integration so approved agent connections could retrieve selected credentials while 1Password remains the source of truth. This connector is not available today. 1Password already offers its own programmatic secrets tooling; Gazebo would need to make client integration or access administration meaningfully easier. No provider selection or launch date has been committed.
What would a 1Password retrieval layer need to add?
A developer building agents for several clients may encounter a different secrets system at each client. A consistent retrieval interface could reduce repeated integration work, but a team already well served by 1Password’s native tools may not need another service. A potential Gazebo connector would also add a sensitive source-reader identity and another availability dependency. The important test is whether the client permits that trust model and whether connection, approval and troubleshooting become simpler than direct integration.
Integration considerations
- 1
1Password supports service accounts and SDK-based retrieval. A potential connector would need read permissions appropriate to its selected vaults, rather than a human account or unnecessary write access.
- 2
A dedicated vault could limit the source-reader’s reach. Selecting individual items or fields in a retrieval layer would not reduce what a stolen service-account token could read upstream.
- 3
Exact item and field references, account eligibility, runtime support and API limits would need validation before an onboarding flow could be offered.
- 4
Source access, agent retrieval and subsequent provider API use are different events. Any combined review would need the records available from each system rather than treating a retrieved key as proof of an action.
- 5
Offboarding would need to stop new reads and address retained copies separately. Replacing an exposed source token would not automatically invalidate every provider credential previously retrieved.
Workflows we’re evaluating
Client-owned credential storage
A possible workflow would leave selected credentials in the client’s 1Password vault while presenting a consistent retrieval interface to the agent developer. We would first need to establish who grants access, who owns the source identity and what happens when the engagement ends.
Agent-attributed retrieval review
A future connector could associate a named agent’s request with an approved item mapping. The question is whether that record adds useful context beyond the client’s existing 1Password and runtime records. It would not establish what the agent later did with the returned credential.
Discuss your 1Password workflow
Tell us about your vault, agent runtime and integration needs. Please don’t send credentials or sensitive client information. No connector or launch date is promised.
Discuss your 1Password workflow