Apassy

Fill, save, and create logins from the Apassy app on your Mac. Your Mac settings control how often routine fills ask for Touch ID.

Apassy is a credential manager for you and your AI agents, on your Mac. This extension fills your Apassy logins into websites in your browser. • Fill: open the extension on a login page and choose a login. Apassy uses your Mac owner-check settings for Touch ID or passphrase confirmation. • Save this login: type your username and password on a page, click Save this login, and authorize the save under your Mac owner-check settings. The login goes into your Apassy vault with the address of the site. • New password: on a sign-up page, Apassy makes a strong password, keeps it in your vault, and fills it into the form. It never goes to the clipboard. • Update login: choose an existing account and authorize the update under your Mac owner-check settings to replace its password with the one typed in the selected form. • Optional field suggestions: enable them for a site, then focus a login field to see matching account titles and usernames. Focusing never fills a secret; choosing an account requires approval under your Mac owner-check settings. • One-time codes and optional passkeys: use codes and passkeys kept in Apassy. Filling codes and creating or using passkeys follow your Mac owner-check settings. • Strict site match: a login fills only on its matching saved site, over https or local loopback http. How often to ask for Touch ID is a global setting on your Mac. Every time is the default. If you choose a window, one local owner check covers later manual actions within it, including fill, save, new password, update, codes and passkeys. The window ends on expiry, vault lock, Mac lock, system sleep, session changes or lifecycle-helper failure. Actions that need passphrase input, such as changing the passphrase or enabling Touch ID unlock, still need it. An AI agent can ask Apassy to fill a login into one matching focused tab. The bouncer gate applies your access rules and asks you when needed. A browser running with remote debugging or test-extension switches also needs your device-local trust for that exact browser instance, including its data folder and debugging port or pipe. Trust covers all profiles in that instance and can be removed in Apassy's Browser settings. The agent tool receives status and filled field names, not credentials. The page receives the filled values; an agent with page access can read them. Agent-filled passwords are cleared if a show-password control makes them visible. Passkeys and codes are normally refused in a browser running with remote debugging or test-extension switches. After a refusal, the extension's quick settings let you request permission for that use or for five minutes in that exact browser instance, confirmed in Apassy. The popup shows remaining time and End now. This permission does not authorize agent fills. The extension needs the Apassy app for macOS (https://apassy.wyderka.cc). Apassy keeps the logins in an encrypted vault on your Mac and talks to the extension through the browser's native messaging. A native-messaging long poll waits for agent fill requests. The extension has no servers, makes no network requests, and never uses the clipboard. It retains nonsecret feature settings and short-lived action/recovery metadata in the browser, never passwords, passkeys, or one-time codes. Site access is optional: field suggestions run on sites you enable, including supported same-origin frames; passkey scripts run in the top frame on granted sites. Toolbar actions remain available without permanent site access. Turning a feature off stops its scripts; browser extension settings let you revoke site access. Open source: https://github.com/wydrox/apassy