1Password CLI
Follow the official CLI get-started steps. Don't guess install commands.
References
- •
references/get-started.md(install + app integration + sign-in flow) - •
references/cli-examples.md(realopexamples)
Workflow
- •Check OS + shell.
- •Verify CLI present:
op --version. - •Confirm desktop app integration is enabled (per get-started) and the app is unlocked.
- •Sign in / authorize this terminal:
op signin(expect an app prompt). - •If multiple accounts: use
--accountorOP_ACCOUNT. - •Verify access:
op whoamiorop account list.
Avoid repeated auth prompts (tmux)
The bash tool uses a fresh TTY per command, so app integration may prompt every time. To reuse authorization, run multiple op commands inside a single tmux session.
Example (see tmux skill for socket conventions):
bash
SOCKET_DIR="${CLAWDBOT_TMUX_SOCKET_DIR:-${TMPDIR:-/tmp}/clawdbot-tmux-sockets}"
mkdir -p "$SOCKET_DIR"
SOCKET="$SOCKET_DIR/clawdbot.sock"
SESSION=op-auth
tmux -S "$SOCKET" new -d -s "$SESSION" -n shell
tmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op signin --account my.1password.com" Enter
tmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op vault list" Enter
tmux -S "$SOCKET" capture-pane -p -J -t "$SESSION":0.0 -S -200
Guardrails
- •Never paste secrets into logs, chat, or code.
- •Prefer
op run/op injectover writing secrets to disk. - •If sign-in without app integration is needed, use
op account add. - •If a command returns "account is not signed in", re-run
op signinand authorize in the app.