2Secret 1.12.0: AI agents on other computers ask your 2Secret, you answer on your phone

Version 1.12.0 of 2Secret is out for Mac, Windows and Linux, the command line, the browser extension, the web vault and the sync server, with a TestFlight build for iPhone and iPad. It is the third part of Agent Access: an AI agent on another computer can ask your 2Secret for your items, and you answer on your computer or your phone.

Agents elsewhere

Until now an AI agent had to run on the same computer as 2Secret: it talked to the desktop app over a local socket. Claude Code in the cloud, an agent on a server or on a second machine could not. In 1.12 such an agent reaches your 2Secret through your sync server. Under Settings → Agents elsewhere you pair it with a code the app shows (as text and as a QR code of a link); on the other computer you run 2secret agent pair with that code. The dialog then names the agent and shows its fingerprint, the same one 2secret agent status prints there, and you confirm it. From then on 2secret mcp --remote gives the AI tool on that computer the same tools as a local agent.

Every request, a password, a one-time code, saving or changing an item, comes to your unlocked 2Secret as the same question as for a local agent, with the agent's name, its computer and its fingerprint. Every unlocked 2Secret of yours shows it, on the desktop and on the phone; the first answer counts and the question closes on the others. A request waits for you for ten minutes. Your permissions ("until 2Secret locks", "for 8 hours") and the log stay per device, as for local agents. Revoke an agent on any device, at any time.

What the server sees

The sync server passes envelopes along that it cannot open: a request is sealed to your account (X25519 and ML-KEM-768, like sharing) and signed by the agent, and your 2Secret checks that signature against the key it pinned when you confirmed the agent, so not even the server can forge or change a request. The answer travels back encrypted with a key that only that request held. The server learns which agent asked when and how large the question was, never what was asked, which item, or what the answer is. The pairing code carries a secret the server never sees, which the agent proves to your app, and a hash of your account's keys, which the agent checks against what the server hands it. The whole wire format is in the protocol documentation; the setup is in the Agent Access documentation.

Signing in from elsewhere

fill_login works from another computer too, for the browser on the agent's computer: start that browser with --remote-debugging-port (Chrome, Edge, Brave or Chromium) and 2Secret there with 2secret mcp --remote --cdp 127.0.0.1:9222. After you allow it, 2Secret on that computer puts the login into the tab that belongs to the item's website and submits it; the AI model only hears how it went.

Updating

• Mac, Windows and Linux: apps with automatic updates turned on offer 1.12.0 by themselves. Otherwise get it from the download page. The command line on the agent's computer has to be 1.12.0 as well.
• iPhone and iPad: answering agents elsewhere is in the TestFlight build; it reaches the App Store with the next review.
• Your own server: update it to 1.12.0 (the Docker image, or the binary); the new tables are made at the first start. With an older server the apps say so under Agents elsewhere, and everything else keeps working. Two new settings cap the agents per account and the open requests per agent (TWOSECRET_MAX_AGENTS, TWOSECRET_MAX_AGENT_REQUESTS, both 20). The 2Secret server sync.2secret.app installs new releases automatically at night, so it has 1.12.0 by tomorrow morning at the latest; until then the apps say under Agents elsewhere that the server is too old.

Everything that changed is in the changelog.