1Password
기준일: 2026-07-26
공식 기준: 1Password
1Password 문서는 OpenClaw 공식 문서(gateway/1password)를 한국어로 정리한 가이드입니다. Resolve Gateway secrets with the 1Password CLI and let agents use the bundled 1password skill 명령·설정 키·코드 예시는 공식 문서를 그대로 보존하며, 해석과 절차 안내는 한국어로 제공합니다. 최종 동작은 설치된 CLI 버전과 공식 원문을 확인하세요.
핵심 요약
Resolve Gateway secrets with the 1Password CLI and let agents use the bundled 1password skill
한국어 가이드 범위: gateway/1password 경로의 설정·명령·제약·예시를 학습용으로 재구성합니다.
문서 구성
공식 문서의 주요 섹션은 다음과 같습니다.
- 요구사항
- Resolve config secrets with op
- Service account setup for headless Gateways
- The 1password skill for agents
- Browser sign-in with 1Password for Claude
- Security notes
- 트러블슈팅
상세 내용
본문
OpenClaw pairs with 1Password in three independent ways:
위 내용은 공식 문서의 해당 섹션 요지입니다. 세부 플래그·기본값은 원문과
--help를 확인하세요.
주요 항목:
- Config secrets: any SecretRef field in
openclaw.jsoncan resolve through theopCLI at runtime, so API keys never live in the config file. - Agent workflows: the bundled
1passwordskill teaches agents to sign in and read or inject secrets withopfor their own tasks. - Browser sign-in: the
claude-clibackend can use Claude Code's Chrome integration with 1Password for Claude, letting the agent sign in to websites without the password ever reaching the model or OpenClaw.
요구사항
주요 항목:
- The 1Password CLI (
op) installed on the Gateway host (brew install 1password-clion macOS). - An auth mode for
op: - Service account (recommended for headless Gateways): export
OP_SERVICE_ACCOUNT_TOKENin the Gateway service environment. No desktop app, no interactive sign-in. - Desktop app integration: the 1Password app runs on the same machine with CLI integration enabled. First calls may trigger Touch ID or system auth.
- Standalone sign-in:
op signinprompts per session. Workable for agents through the skill, but not suited for config secret resolution on a headless Gateway.
Resolve config secrets with op
Declare an exec secret provider that runs op read with an op://vault/item/field reference, then point any SecretRef-capable field at it:
위 내용은 공식 문서의 해당 섹션 요지입니다. 세부 플래그·기본값은 원문과
--help를 확인하세요.
주요 항목:
commandmust be an absolute path;trustedDirsmarks its directory as trusted, andallowSymlinkCommandis needed because Homebrew installsopas a symlink.argscarries theop://vault/item/fieldreference verbatim. OpenClaw does not parse theop://scheme itself; theopbinary resolves it.passEnvforwards the listed variables from the Gateway environment. Desktop app integration needsHOME; service accounts also needOP_SERVICE_ACCOUNT_TOKENpresent in the Gateway service environment (add it topassEnv, or set it viaenvonly if you accept the token being readable in the config file).- For single-value output keep
id: "value". WithjsonOnly: trueand a JSON payload, address fields with a JSON pointer id instead. - One provider entry per secret keeps references auditable; name providers after their consumer (
onepassword_openai,onepassword_telegram).
{
secrets: {
providers: {
onepassword_openai: {
source: "exec",
command: "/opt/homebrew/bin/op",
allowSymlinkCommand: true, // required for Homebrew symlinked binaries
trustedDirs: ["/opt/homebrew"],
args: ["read", "op://Personal/OpenClaw QA API Key/password"],
passEnv: ["HOME"],
jsonOnly: false,
},
},
},
models: {
providers: {
openai: {
baseUrl: "https://api.openai.com/v1",
models: [{ id: "gpt-5", name: "gpt-5" }],
apiKey: { source: "exec", provider: "onepassword_openai", id: "value" },
},
},
},
}
Service account setup for headless Gateways
- Create a service account in your 1Password account and grant it read access to only the vault items the Gateway needs. 2. Provide
OP_SERVICE_ACCOUNT_TOKENto the Gateway service (launchd plist, systemd unit, or container env). 3. Add"OP_SERVICE_ACCOUNT_TOKEN"to the providerpassEnvlist. 4. Verify from the Gateway host environment:op whoamishould print the service account without prompting.
위 내용은 공식 문서의 해당 섹션 요지입니다. 세부 플래그·기본값은 원문과
--help를 확인하세요.
The 1password skill for agents
OpenClaw bundles a 1password skill that turns agents into competent op operators: it detects the available auth mode (service account, desktop app integration, or standalone sign-in), verifies access with op whoami before reading anything, and prefers op run / op inject over writing secret values to disk. The skill requires the op binary and offers a Homebrew install when it is missing.
위 내용은 공식 문서의 해당 섹션 요지입니다. 세부 플래그·기본값은 원문과
--help를 확인하세요.
Browser sign-in with 1Password for Claude
1Password for Claude lets Claude request a login while the 1Password browser extension fills the credential directly into the page over an encrypted channel. The secret never enters the model context, the transcript, or OpenClaw. When OpenClaw runs the claude-cli backend with Claude Code's Chrome integration enabled, agent tasks can use that flow for websites that need a real signed-in session.
위 내용은 공식 문서의 해당 섹션 요지입니다. 세부 플래그·기본값은 원문과
--help를 확인하세요.
주요 항목:
- A macOS gateway host with Chrome, the Claude in Chrome extension connected, the 1Password desktop app, and the 1Password browser extension (both 8.12.28 or later).
- Claude Code signed in to a direct Anthropic plan (Pro, Max, Team, or Enterprise). Chrome integration is not available through Amazon Bedrock, Google Cloud, or other third-party providers.
- The one-time 1Password connection on the Anthropic side: 1Password for Claude is set up through the Claude desktop app or extension flow described in 1Password's guide, and it is currently a macOS beta. On 1Password Business, an administrator must first enable "Allow AI agents to autofill for users" under Policies; Anthropic Team/Enterprise plans also ship with the integration off until an Owner enables it.
- A CLI backend plugin that adds
--chrometo the Claude launch args; the bundled backend does not enable Chrome. - A person at the gateway host: every credential use shows a 1Password prompt confirmed there (for example with Touch ID). Under a restrictive exec policy the browser tool calls themselves are also relayed to your channel as OpenClaw approvals first.
Security notes
주요 항목:
- Secret values resolved through exec providers stay in Gateway memory; config snapshots and
config.getresponses redact SecretRef fields. - Never place secret values in
openclaw.json, logs, or chat. Keep item names in config, values in 1Password. - The 1Password audit trail shows every service account read, which makes key rotation and incident review practical.
트러블슈팅
주요 항목:
command not foundor spawn errors: use the absoluteoppath and include its directory intrustedDirs.opresolves but reads fail with symlink errors: setallowSymlinkCommand: truefor Homebrew installs.account is not signed in: for service accounts, confirmOP_SERVICE_ACCOUNT_TOKENreaches the Gateway service and is listed inpassEnv; for desktop integration, confirm the app is running and unlocked.- Slow first reads: raise
timeoutMson the provider;opcold starts can exceed strict timeouts on busy hosts.
실습 체크리스트
- 공식 문서와 로컬 버전을 대조합니다:
https://docs.openclaw.ai/gateway/1password - 관련 CLI는
openclaw --help및 하위 명령--help로 옵션을 확인합니다. - 설정 변경 시
openclaw config/openclaw doctor로 유효성을 검사합니다. - Gateway·채널·플러그인 변경 후에는 필요 시 Gateway를 재시작합니다.
자주 쓰는 명령·설정 예시
{
secrets: {
providers: {
onepassword_openai: {
source: "exec",
command: "/opt/homebrew/bin/op",
allowSymlinkCommand: true, // required for Homebrew symlinked binaries
trustedDirs: ["/opt/homebrew"],
args: ["read", "op://Personal/OpenClaw QA API Key/password"],
passEnv: ["HOME"],
jsonOnly: false,
},
},
},
models: {
providers: {
openai: {
baseUrl: "https://api.openai.com/v1",
models: [{ id: "gpt-5", name: "gpt-5" }],
apiKey: { source: "exec", provider: "onepassword_openai", id: "value" },
},
},
},
}
관련 링크
- 공식 원문: gateway/1password
- OpenClaw 문서 홈
이 가이드는 공식 문서를 한국어 학습용으로 재구성한 것입니다. 옵션 기본값·플래그 이름은 설치 버전에 따라 달라질 수 있습니다.