Pup - the AI's own browser
Public Made by Adomby adom
pup gives your AI a real browser on your desktop that it drives completely, in the background, signed in as you: windows that never jump in front of your work, one shared profile that learns your logins, and every window labeled on the taskbar with its AI thread's name.
macOS: import the user's saved Chrome/Edge passwords (pup_import_browser_logins is Windows-only)
@kyle, a Mac feature request, for Drew in particular: he uses pup all day on his Mac and keeps hitting sign-in pages.
Today
On Windows, pup_import_browser_logins {} pulls every password saved in the user's Chrome, Edge or Brave into pup's vault. It goes through Adom Bridge's desktop_decrypt_browser_credentials: one consent plus one Windows prompt. From then on pup fills sign-in pages by itself.
On a Mac the verb answers unsupported_platform. The decrypt is Windows-only today (Chromium ABE/DPAPI).
What 2.0.732 does about it (insiders, pending gates)
- The tip. The extension lane now notices sign-in pages after every open and navigate. When pup has no saved login, the answer carries a
_loginTip. On Windows the tip tells the AI to offer the import. On a Mac it says what does work: the user signs in once in the pup window, pup saves it as they submit, and it fills that site from then on; orpup_vault_syncfrom a Windows desktop on the same account. - The skill. A new skill,
pup-import-logins, says the same.
The ask
A Mac import. On macOS, Chrome's saved passwords are AES-encrypted with a key stored in the login keychain ("Chrome Safe Storage", the same item --use-mock-keychain avoids for pup's own profiles). So a Mac import is:
- read that key (a single keychain approval)
- derive it with PBKDF2 (salt
saltysalt, 1003 iterations) - decrypt the
Login Datarows
That's one approval, like the Windows UAC. It probably belongs in Adom Bridge for macOS next to desktop_decrypt_browser_credentials, so pup's import.rs only has to drop its cfg!(windows) gate and call the same verb.