CoincideFeature
Passwords and saved logins
Coincide’s browser can fill sign-ins and one-time codes from logins it saves in your Keychain, from 1Password and from Bitwarden, without any browser extension. When an agent needs to sign in, Coincide types the login for it after you allow the site, and the agent never sees the password.
Where logins come from
Turn password managers on in Settings › Browser › Passwords. None is on until you choose one, and you can use several at once.
| Source | How Coincide reaches it | Set up |
|---|---|---|
| Coincide Saved Logins | Your login Keychain on this Mac | Nothing to install |
| 1Password | 1Password’s command-line tool, op | Install it, then turn on “Integrate with 1Password CLI” in 1Password › Settings › Developer |
| Bitwarden | Bitwarden’s command-line tool, bw | Install it, run bw login in Terminal once, then unlock it in Coincide |
Both tools install with Homebrew:
brew install --cask 1password-clibrew install bitwarden-cliBitwarden’s master password goes only to bw. Coincide keeps the unlocked session that bw returns in your Keychain until you choose Lock.
Fill a sign-in
- Open the sign-in page in a thread’s browser.
- Click the key button in the address bar. It lists the logins that match the site from every source you turned on.
- Pick one. Coincide types the username and password into the page itself. On a two-factor page, the same menu offers the login’s one-time code, for logins that have one.
After you sign in on a page by hand, Coincide offers to save the login in your Keychain (turn this off with “Offer to save logins”, or choose Never for This Site).
Import passwords from a CSV export
“Import CSV…” in Settings › Browser › Passwords reads password exports from Chrome, Safari and Apple Passwords, Firefox, 1Password and Bitwarden, and saves the logins in your Keychain as Coincide saved logins. Rows without a web address or a password are skipped. Delete the CSV file afterwards: it holds your passwords unencrypted.
When an agent needs to sign in
An agent driving the browser can ask Coincide to sign in on the page it’s on. Coincide shows a sign-in request in the thread naming the site and the login it would use, and you choose Allow Once, Always for This Site or Deny. If you allow it, Coincide fills the form; the agent gets the username at most, never the password or the one-time code, and submits the form itself. Sites you allowed always are listed under “Sites Agents Can Sign In To”, where you can revoke them.
If no saved login matches, the agent hands the step to you instead, with a note in the browser panel saying what to do.
Agents and your Bitwarden session. “Let agents use your unlocked password managers” in Settings › Browser › Passwords is on by default. While it’s on, agents Coincide starts receive Bitwarden’s unlocked session, so they can read any item in your vault with the bw command, such as API keys and tokens, without asking. Turn it off if you don’t want that; agents that are already running pick up the change when they start again.
How the secrets are handled
- Coincide talks to each password manager through its own command-line tool on your Mac. It doesn’t need or use their browser extensions.
- Logins you save in Coincide stay in your login Keychain, together with any one-time-code secrets. Coincide’s data folder keeps only the list of logins, without passwords.
- Agents can’t read password fields, cookies or site storage through the browser connection.
- Passkeys are a separate feature; see passkeys in Coincide’s browser.
The privacy policy lists what’s kept where, and where Coincide stores data shows how to remove it.
Limitations
- Some password tools can’t search by site; Coincide then matches their logins to the page itself. Settings shows which features each tool supports.
- Filling needs the password manager to be unlocked: Bitwarden in Coincide’s Settings, 1Password through its app.