Search and manage your Proton Pass items directly from Raycast.
proton-pass implementation.pass-cli execution, local caching, and command-specific flows implemented in this repository.This extension requires the Proton Pass CLI (pass-cli) to be authenticated.
The extension automatically downloads and installs the Proton Pass CLI on first use. No manual installation required!
If you prefer to install manually on macOS, you can use Homebrew:
brew install protonmail/proton/pass-cli
Or download from Proton Pass CLI Documentation.
Run the login command in your terminal:
pass-cli login
This uses web login by default: pass-cli prints a URL, you complete authentication in your browser, and the session is saved locally.
Optional: use terminal prompts with interactive login:
pass-cli login --interactive user@proton.me
Test that the CLI is working:
pass-cli vault list
pass-cli executable (defaults to pass-cli in PATH)Fill Login closes Raycast and fills the login of the app you were using: it pastes the email (or the username when the item has no email), presses Tab and pastes the password. Put the cursor in the first field of the login form before opening Raycast. If the item has a 2FA code, the code is then left in the clipboard, ready to paste on the next screen.
For logins split over several screens, use Paste Email, Paste Username, Paste Password and Paste 2FA Code instead.
Filling only types into the app Raycast was opened from: if another app comes in front, it stops before the next key.
Values go through the clipboard marked as concealed, so clipboard history skips them. Afterwards, the previous clipboard is restored as far as Raycast can read it (text, HTML or a file), and otherwise cleared. The first time, macOS asks to allow Raycast to control System Events, and Raycast needs Accessibility access (System Settings › Privacy & Security).
To fill with Enter, set Primary Action to Fill Login (macOS).
If you see keyring-related errors, try:
pass-cli logout --force
export PROTON_PASS_KEY_PROVIDER=fs
pass-cli login
On Windows, if session persistence through Windows Credential Manager reports a keyring_error, retry from PowerShell:
pass-cli logout --force
$env:PROTON_PASS_KEY_PROVIDER = "fs"
pass-cli login
If the CLI is installed but not detected, set the full path in extension preferences:
/opt/homebrew/bin/pass-cli
If the auto-installed CLI becomes corrupted or you want to force a re-download, use the "Clear CLI Cache" action available in the error screens.
Run on Windows x86_64 from this extension directory:
npm ci; if ($LASTEXITCODE) { exit $LASTEXITCODE }; npm test; if ($LASTEXITCODE) { exit $LASTEXITCODE }; npx tsc --noEmit
Then verify a fresh automatic install keeps pass-cli.exe beside libcrypto-3-x64.dll, browser login persists through Windows Credential Manager (or shows the documented keyring_error guidance), search/copy/TOTP work, shortcuts display Ctrl-based keys, and Browser Extension plus Terminal fallback actions stay absent.
Run on macOS:
npm ci && npm test && npm run lint && npm run build
Then verify a fresh install passes Gatekeeper after chmod/quarantine removal, browser re-login works with CLI 2.3.3, and all commands complete a smoke test. Sessions from CLI 1.4.1 may require login again.