Question

Feature Request: Remote approval for op CLI / desktop prompts to support Agentic Workflows

15 replies
475 views

Hey team,

Claude Code just release a new https://code.claude.com/docs/en/remote-control feature that lets you send prompts and commands to your desktop (or remote sandbox) directly from a mobile app. You might already be using it

I have a feeling a lot of devs are going to run into the same need for "remote 1Password auth" because of this.

I really love how smooth 1Password handles secret and env management. I keep all my dev keys in 1P, and a lot of my scripts are tightly coupled with the op CLI. For pure local development, this setup is flawless.

I tossed Claude Code into a local Docker sandbox for security reasons. Whenever it needed a 1Password key (like for git SSH), I just used SSH forwarding to my host machine for biometric auth. That worked fine since I was sitting right there.

But this new mobile remote control feature completely breaks that workflow. I'm not at my desk to scan my fingerprint. Sure, we could generate static tokens to let the agent grab what it needs, but that’s way too inflexible—agents need dynamic access to different resources.

If we could get a feature to approve desktop/CLI secret requests directly from the 1Password mobile app (maybe with some specific allow/deny rules and auth timeouts), it would be a massive help for agent-driven development. This applies to both local remote control and fully remote sandboxes.

Honestly, this would be a killer feature for me. Would love to know if this is something the team could consider.

CLI

Show previous replies

R

rmoll

Just adding my vote to the pile, recently started relying on remote Codex work to continue while I’m away, but 1password is essentially incompatible with it atm, need to return to laptop to approve use of this or that key.

P

prrtzt

+1 on this, that would be incredibly useful

W

Wabiloo

+1 - I’m almost surprised it doesn’t exist yet

H

hamiltont

+1. Use case same as OP - claude code via remote control

R

romangaina

Strong +1 for CFP-19201, and I strongly support @sastian’s points about meaningful authorization prompts.

I use Codex Remote from my phone to give tasks to Codex running on my Mac, including server administration over SSH. My SSH keys are stored in 1Password, but approval requests appear only on the Mac. When I’m away, the task is blocked—even though I have my phone and can authenticate with 1Password there.

Please let us approve or deny desktop SSH Agent and CLI requests from the 1Password mobile app, using biometric authentication.

I also fully agree that approval needs enough context to make an informed decision:

The requesting device and identifiable application or process.
The specific item or SSH key being requested.
The destination server and user, when available.
The actual scope and duration of the permission.
A choice between one-time approval and explicitly time-limited access.

Any explanation supplied by the agent should be clearly distinguished from information 1Password can verify.

I want to keep my keys protected in 1Password and approve access when needed. Remote workflows currently push users toward local key copies or broader standing access just to keep tasks moving.

Please prioritize this and share whether it’s planned. It would remove a significant obstacle to using 1Password securely with remotely controlled coding agents.

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO