Verbs that carry a password (credential_set, pup_type) drop the bridge on both boxes; read verbs keep working

by 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.

Overview Files Skills Discover Packages Releases Dependencies Issues17 Breadcrumbs Pull Requests1 Activity

Closed general

John Lauer · 1mo ago ·closed by John Lauer

Summary

On 2026-09-29, during a vendor sign-up, every call that carried a password dropped the pup bridge. credential_set (storing a new login) and pup_type (typing the password into a login field) both ended with an HTTP error to pup's local port. It happened on both AdomLapper and ConfRoomROG. Read verbs (pup_credentials, pup_eval, pup_screenshot) kept working throughout, and the bridge came back on its own.

This may be related to #122 (the full Windows vault on AdomLapper), but ConfRoomROG has a small vault and also dropped, and pup_type does not write to the vault at all.

Steps

pup_open_window on a vendor login page, focus the password field.
pup_type {"text": "<a 24-character random password>", ...} → HTTP error to the local port. Nothing is typed.
credential_set {"host": "<vendor host>", "username": "<email>", "password": "<same>"} → same error.
Any read verb straight afterwards → OK.

Expected

The password is typed or stored, or a structured error comes back (vault_full, secret_rejected, ...) without the bridge dropping.

Workaround used

Keep the password in a 0600 scratch file, type it with nbrowser_type in the user's own Chrome, and let the browser save it. pup_import_browser_logins then brings it into the vault. AI Flow's aiflow-credentials skill documents this until pup can take a secret safely.

Found by the adom-aiflow buck molecule run (gap 16 in its gap log).

1 Reply

John Lauer · 27d ago

Does not reproduce on 2.0.720. Tested on arav-rog (small vault):

credential_set: stored a 24-character letters-only password, a 23-character one with #!%&$^*, and a 23-character one with "\{}<>|;~@. All three returned success: true`. The test login was then deleted.
pup_type: typed both 23-character passwords into the password field on https://the-internet.herokuapp.com/login. The field's value length came back 23 each time.
Bridge: it stayed up through every call.

The drops on 2026-09-29 were on an earlier build. Since then the vault and the extension input lane have changed many times, and the full-vault case on AdomLapper (#122) was separate. Closing. Reopen with the exact pup version and the error text if it happens again.

John Lauer closed this · 27d ago