šŸ¦žOpenClaw Guide
← All Integrations
šŸ”

1Password

Mediumā±ļø 10-15 minutes

Secure credential management

OpenClaw 1Password Integration

Keep your AI workflows secure with 1Password. OpenClaw integrates with the 1Password CLI (op) to inject secrets at runtime — no hardcoded credentials, no environment variable sprawl.

Setup

Step 1: Install 1Password CLI

bash
# macOSbrew install 1password-cli# Verifyop --version

Step 2: Enable Desktop App Integration

  1. Open 1Password app
  2. Settings → Developer → "Integrate with 1Password CLI"
  3. Toggle on

This allows op to authenticate through the desktop app — no separate auth needed.

Step 3: Configure OpenClaw

yaml
integrations:  onePassword:    enabled: true    # Uses system auth (desktop app integration)    vault: "Personal"  # default vault    # Optional: multiple vaults    vaults:      - "Personal"      - "Work"      - "Shared Secrets"

Step 4: Test

bash
op item list

Should list your vault items.

Secret Injection

The core use case: inject 1Password secrets into OpenClaw skills without hardcoding.

In Skills

yaml
skills:  deploy:    env:      AWS_ACCESS_KEY: "op://Work/AWS Production/access-key-id"      AWS_SECRET: "op://Work/AWS Production/secret-access-key"      DB_PASSWORD: "op://Work/Database/password"

When the skill runs, OpenClaw fetches secrets from 1Password and injects them as environment variables. Secrets never touch disk.

In Config

Reference 1Password items directly in your OpenClaw config:

yaml
channels:  telegram:    token: "op://Personal/OpenClaw Bot/token"

Natural Language Access

bash
What's in my Work vault?→ 47 items: AWS credentials, Database passwords, API keys...Get the staging database password→ [copied to clipboard, not shown in chat]Create a new password for: ProjectX API Key→ Generated 32-char password, saved to Work vault āœ“

Use Cases

  • Deployment secrets: Inject credentials at deploy time
  • API key management: Reference keys by name, not value
  • Team sharing: Share secrets via 1Password without exposing values
  • Rotation: Update secrets in one place, everywhere auto-refreshes

Troubleshooting

op not authenticated? Run op signin or enable Desktop App Integration in 1Password settings.

Secret not found? Check vault name and item name are exact (case-sensitive). Use op item list to verify.

Permission denied? Some vaults require separate authentication. Check vault permissions in 1Password admin.

Features

Secret injection

Inject 1Password secrets into skill environments at runtime

CLI integration

Uses official 1Password CLI with desktop app authentication

Multi-vault support

Access Personal, Work, and shared vaults simultaneously

Config references

Reference op:// URIs directly in OpenClaw configuration

Password generation

Create and store new credentials via natural language

Zero secrets on disk

Secrets fetched at runtime, never stored in files or logs

Use Cases

→

Deployment credentials

Inject AWS, GCP, and other keys at deploy time without hardcoding

→

API key management

Reference API keys by name — update in 1Password, auto-refreshes everywhere

→

Team secret sharing

Share credentials securely without exposing values in chat or config

→

Secret rotation

Update rotated credentials once, propagate everywhere automatically

Setup Guide

Requirements

  • āœ“1Password account
  • āœ“1Password CLI (op) installed
  • āœ“Desktop app integration enabled (recommended)
1

Install 1Password CLI

Download and install the op CLI from 1password.com/downloads/command-line

2

Enable desktop integration

In 1Password settings, enable 'Integrate with 1Password CLI' for seamless authentication.

3

Sign in

Run 'op signin' or let the desktop app handle authentication.

4

Test access

Run 'op vault list' to confirm you can access your vaults.

Limitations

  • āš ļøBiometric auth may interrupt automated workflows
  • āš ļøSome operations require manual approval

Frequently Asked Questions

Will my passwords be visible in chat?

No. Secrets are used behind the scenes. Your assistant can use them without displaying them in messages.

Do I need 1Password Teams or Business?

No, personal 1Password accounts work fine. Teams/Business add features like shared vaults.

How is this different from storing secrets in config?

1Password provides encryption, access control, audit logs, and easy rotation. Config files are just text.

Can it create or modify secrets?

Yes, the op CLI supports creating and editing items. Your assistant can manage secrets programmatically.

šŸ”„ Your AI should run your business, not just answer questions.

We'll show you how.Free to join.

Join Vibe Combinator →

šŸ™ Your AI should run your business.

Weekly live builds + template vault. We'll show you how to make AI actually work.Free to join.

Join Vibe Combinator →