Pup - the AI's own browser

@@ -0,0 +1,58 @@+---+name: pup-doppelganger+description: "THE mission of pup, and the design rule that flows from it. Normal browsers are built for humans; pup is a browser built for the AI — the human's doppelganger on the web. Every design call defers to this: anything a human browser shows a HUMAN to click, pup handles SILENTLY for the AI. Read before adding any user-facing prompt, dialog, foreground, or gesture-dependent behavior."+---++# pup is the AI's browser — the human's doppelganger on the web++## The mission (John, 2026-08-13)++> "Normal browsers are for humans. pup is for the AI to drive a browser. We're making a+> new browser for the AI as a **doppelganger for the human**."++A normal browser (Chrome, Edge, Safari) is a product for a *person*: it asks the person+questions, pops dialogs for the person to click, shows the person banners, pulls its window+in front of the person. pup is not that. **pup is a browser built for the AI to drive on the+human's behalf** — a full, real browser the AI operates as the human's stand-in. The AI acts+*as* the human (it carries the human's shared `adom-you` identity, accumulates the human's+logins), but it is *not* the human sitting at the screen, so it never needs the human-facing+machinery a normal browser is made of.++## The design rule this dictates++**Anything a normal browser would show a HUMAN to read, click, confirm, or drag, pup handles+SILENTLY for the AI instead.** If a design choice puts a human-facing prompt, dialog,+foreground steal, gesture requirement, or desktop-clutter footprint in the path, it is wrong+for pup by definition — find the silent, background, AI-driven equivalent.++Concretely, every one of these decisions is the same principle applied:++| A normal (human) browser… | pup (the AI's doppelganger)… |+|---|---|+| shows a "Save password?" dialog to click | captures the login silently into the keychain vault (v2.0.121–122) |+| makes you pick a saved login from a dropdown (needs a real gesture) | fills it directly over CDP — background, no gesture, no foreground |+| pulls its window forward when it wants attention | stays in the background; signals with a taskbar flash, never a focus steal |+| pops a Windows Firewall / UAC prompt for mDNS/Cast | disables Cast so it never binds the network, no prompt (v2.0.120) |+| requires clicking "Developer mode" to load an extension | flips it on itself via the developerPrivate API (v2.0.114) |+| leaves a Start Menu shortcut / "managed by your org" banner | registry-only identity, no Start Menu footprint (v2.0.118) |+| rewrites tab titles / shows its own chrome over the page | leaves the page untouched (see [[pup-page-integrity]]) |++When a new question comes up ("should pup show X?"), the answer is almost always: **a human+browser shows a human X; the AI's doppelganger browser doesn't need to be shown — it already+knows, so do X silently.**++## The one boundary: doppelganger, not impostor++Acting *as* the human is the point (shared identity, real logins), but pup is still a+*sandbox the AI owns*, never the human's real signed-in browser — that is `nb`/`nbe`'s job.+And "handle it silently for the AI" never means "hide it from the human": the human can always+see what pup did (the dashboard, the taskbar identity, the caption, the vault listing). Silent+toward the *browser UI*, transparent toward the *person*.++## Why this is written down++pup accretes features fast, and each one faces the same fork: do the human-browser thing+(prompt/dialog/foreground) or the doppelganger thing (silent/background/AI-driven). Left+un-stated, the easy path is to inherit whatever Chrome does for humans. This mission is the+tie-breaker: **build for the AI driver, not the human reader.** The user-facing version of+this lives at the top of the wiki README so users understand what pup is *for*.

@@ -0,0 +1,56 @@+# pup login recipes — how the AI signs you into any site++**pup is your AI's doppelganger on the web.** For most sites, pup logs you in automatically:+it fills your saved credential from the OS-keychain vault and submits, no dialog, no fuss. But+real login flows differ wildly, email-first steps, account pickers, custom-masked password+fields, 2FA, anti-bot defenses, and a generic approach fails on the tricky ones.++This folder is a **growing corpus of per-site login recipes**: one file per domain documenting+the exact sequence pup should drive to sign you in, and which steps need *you* (the human) for a+moment. Every Adom user's AI reads these, and **you can contribute the recipe for any site you+hit** so the next person's AI just works.++The goal is thousands of recipes so pup can truly log into anything, for all of us.++## The operating context: Auto mode++Adom users run their AI in Claude Code **Auto mode** (Hydrogen puts you there). Auto approves+safe actions and pauses on risky ones. So every recipe is written Auto-mode-aware:++- **Prefer structured pup verbs** (`pup_login`, `pup_type`, `pup_click`) over raw `pup_eval`,+  the safety check allows the former and pauses the latter. See the `pup-auto-mode` dev skill.+- **Mark which steps auto-approve vs. pause for the human.** Typing a *new* credential pauses+  (correct, you confirm the site); everything after the vault knows it flows silently.+- **Always on the durable `adom-you` profile**, so the session + 2FA-remember persist and you+  rarely re-authenticate. Never log in on an isolated throwaway.++## Recipe file format++Name the file by registrable domain: `login-recipes/<domain>.md` (e.g. `gusto.com.md`). Use:++```markdown+# <site name> (<domain>)++- **Login entry URL:** the URL that lands on the sign-in flow+- **Flow type:** single-page | email-first | account-picker | SSO-redirect | other+- **2FA:** none | TOTP authenticator | SMS | push  (and whether "remember device" is offered)+- **Anti-automation notes:** custom-masked fields, isTrusted requirements, etc.++## Steps+1. …each step: the action, the exact selector if non-obvious, the pup verb to use, and+   whether it AUTO-APPROVES or PAUSES for the human.++## Field selectors+- username: `<selector>`  (type: text/email)+- password: `<selector>`  (note if NOT type=password)+- submit:   `<selector or button text>`++## Gotchas+- anything that bit someone: React-controlled fields, reloads that clear values, redirects, etc.+```++## Contributing (any Adom user)++Hit a site whose login your AI fumbled? Tell your AI "add a pup login recipe for <site>" or open+a PR on the pup wiki page (Files tab → `login-recipes/`). Include the flow type, the field+selectors, and any gotcha. Keep secrets OUT, recipes describe the *flow*, never credentials.

@@ -0,0 +1,25 @@+# Gusto (gusto.com) — payroll++- **Login entry URL:** `https://app.gusto.com/login` (redirects to `login.gusto.com`, a Keycloak IdP)+- **Flow type:** email-first → account-picker → password → 2FA+- **2FA:** TOTP authenticator (6-digit code); "Remember device for 30 days" checkbox offered — check it on adom-you so future logins skip 2FA+- **Anti-automation notes:** the password field is a **React-controlled masked input** and is `type="text"` (not `type=password`), with `autocomplete="current-password"`. Setting `.value` does NOT register with React's state — you MUST use real keystrokes (`pup_type`) and then read the value back to confirm it landed before submitting.++## Steps+1. Open on **adom-you** (never isolated) — `pup_open_window {url:"https://app.gusto.com/login"}`. AUTO-APPROVES. If adom-you already has a Gusto session you land signed in; done.+2. **Email step** — fill the email field (benign, AI may enter it) and click **Continue**. `pup_type` or a fill; AUTO-APPROVES (username is not a secret).+3. **Account picker** — Gusto often shows "Select your email address" with your account as a row. Click the row for your email (a `<button>`). AUTO-APPROVES.+4. **Password step** ("Enter your password") — the field is `#password`, `type=text`, masked by React. Use `pup_login {username, password, submit:true, submitReason:"…confirm login.gusto.com is the intended site…"}` (structured verb → passes the safety check) OR `pup_type {selector:"#password", text, clear:true}` then verify `#password` value length, then click Continue. This is the step that **PAUSES for the human under Auto mode** (typing a credential) — surface it for one-tap approval, or the human types it. Real keystrokes are mandatory; `.value`-set silently fails.+5. **2FA** — "Enter the 6-digit code in your authenticator app." pup CANNOT generate this; the **human enters the 6-digit code** from their authenticator (PAUSES). Check "Remember device" so it is a one-time step on adom-you.+6. Redirects to `app.gusto.com/…` dashboard = signed in.++## Field selectors+- username/email: `input[type=email], input[name=username]` (type: email)+- password: `#password` — **NOTE: `type="text"`, `autocomplete="current-password"`, not `type=password`**+- submit: button with text "Continue"++## Gotchas+- `type=password` selectors miss the password field entirely (it is `type=text`). pup ≥2.0.123 also matches `autocomplete=current-password` / `name=password`.+- Setting `.value` on the password field passes React's display but submits EMPTY ("Password is required"). Use real keystrokes and verify the value landed.+- On the email step, the value can reset on reload — re-enter and submit via the form, then poll for the password field.+- It is a cross-origin SSO redirect (`login.gusto.com` → `app.gusto.com`); capture on password blur (pup ≥2.0.121) so the credential is vaulted before the redirect.