dirpush 0.1.5 → 0.1.7

package/.agents/skills/dirpush/SKILL.md

@@ -23,7 +23,7 @@ You are a **worker**, not the source of truth. SQLite (via the `dirpush` CLI) ow
    Something the human should do that doesn't stop the job (verify an email later, check a listing) → `dirpush todo add --job <job> --message "…" [--url …]`. It shows in the dashboard's Actions tab.
 10. **Hold your lease.** Checkpoints extend it; on long pages call `dirpush work heartbeat <job>` at least every 10 minutes. Stopping cleanly: `dirpush work release <job>`.
 11. **Browser = `dirpush ab <agent-browser command>`.** It drives the agents' own Chrome profile (logged into the human's Google account; Gmail, Drive and account pages blocked), never the human's everyday browser. Any agent that can run shell commands can use it. Never call `agent-browser` directly on that profile, never `network unroute`, never another browser tool or extension. Google sign-in rules in [authentication.md](references/authentication.md) are hard rules.
-   Habits: `dirpush ab open <url>`, `dirpush ab snapshot -i` (refs like `@e3`), `dirpush ab fill @e3 "text"`, `dirpush ab select`, `dirpush ab check`, `dirpush ab click`. Uploads: `dirpush ab upload '<input[type=file] selector>' <absolute path>`, never a button ref; sign in before uploading. Every call has a 90 s limit (`AB_TIMEOUT`); exit 142 = it hung: `dirpush ab close`, reopen, continue from your last checkpoint.
+   Habits: `dirpush ab open <url>`, `dirpush ab snapshot -i` (refs like `@e3`), `dirpush ab fill @e3 "text"`, `dirpush ab select`, `dirpush ab check`, `dirpush ab click`. Uploads: `dirpush ab upload '<input[type=file] selector>' <absolute path>`, never a button ref; sign in before uploading. Every call has a 90 s limit (`AB_TIMEOUT`); exit 142 = it hung: close that tab (`dirpush ab tab close`), reopen, continue from your last checkpoint. If every call hangs while one site is open (some pages freeze any automated browser on purpose), close that tab and `work block --type bot_protection` saying the human must submit it in their own browser; never close the whole browser for this.
 12. **Bot checks: wait, don't fight.** Cloudflare / Turnstile usually clears by itself in this Chrome: wait ~10 s and re-snapshot. Never click a CAPTCHA or Turnstile checkbox yourself and never use a solving service. Still there → `work block --type captcha` with the page left open. A plain arithmetic question in a form is part of the form: answer it.
 13. **Close your browser** (`dirpush ab close`) when you stop, unless a job of yours is blocked on the human in that window (CAPTCHA, login) — leave it for them. A throwaway profile (`AB_PROFILE`) loses the filled form when closed: in the block message, list exactly what to re-enter.
 

package/.agents/skills/dirpush/references/authentication.md

@@ -13,14 +13,14 @@ Always drive the browser through `dirpush ab` (agent-browser on the agents' own
 
 ## Creating a password without ever seeing it
 
-Generate, fill, and store in **one** shell command so the secret never appears in your context or in any file:
+With the sign-up (or reset) page open in `dirpush ab`, one command generates the password, types it into every field you name, checks the site got it, and saves it to the vault. It never appears in your context or any file:
 
 ```bash
-PW=$(openssl rand -base64 18) && dirpush ab fill @<password-ref> "$PW" && \
-  printf %s "$PW" | agent-browser auth save <directory-id>-<product-id> --url <login-url> --username <email> --password-stdin && unset PW
+dirpush browser password <directory-id>-<product-id> --url <this page's url> --username <email> \
+  [--login-url <the site's sign-in page>] '<password selector>' ['<confirm selector>']
 ```
 
-(Repeat the `fill` for a "confirm password" field inside the same command.) Before `auth save`, check the fields really hold it, e.g. `agent-browser eval '[...document.querySelectorAll("input[type=password]")].map(p=>p.value.length)'` → all 24. A `fill` can report success on a selector that matched nothing, leaving a vault entry for a password the site never got.
+Passwords always have upper, lower, digit and symbol (24 chars). Pass `--login-url` whenever the page isn't the sign-in page (a sign-up form, a reset link): the vault opens that URL for every later `browser login`. Never generate passwords yourself (`openssl rand -base64` can lack a symbol, and sites reject it).
 
 ## Continue with Google (`accounts.oauth_google`)
 

package/package.json

@@ -37,7 +37,7 @@
     "url": "https://github.com/baronunread/dirpush.git"
   },
   "homepage": "https://dirpush.com",
-  "version": "0.1.5",
+  "version": "0.1.7",
   "keywords": [
     "directories",
     "startup",

package/scripts/ab

@@ -19,7 +19,14 @@ AB="agent-browser --headed --session ${AB_SESSION:-default} --profile ${AB_PROFI
 # `launch browser start` already runs this profile (Google services blocked by its PAC script): attach to it
 # instead of launching a second Chrome on the same profile.
 PORT="${LAUNCH_BROWSER_PORT:-9222}"
-if [ -z "$AB_PROFILE" ] && curl -s -m 1 "http://127.0.0.1:$PORT/json/version" >/dev/null 2>&1; then
+up() { curl -s -m 1 "http://127.0.0.1:$PORT/json/version" >/dev/null 2>&1; }
+# The real profile always runs as that dedicated Chrome. Launching it through agent-browser instead relaunches Chrome
+# on every call (losing tabs and filled forms), so start it here when it's down (e.g. after a Google sign-in).
+if [ -z "$AB_PROFILE" ] && ! up && [ "$1" != "close" ]; then
+  agent-browser --session "${AB_SESSION:-default}" close >/dev/null 2>&1 || true
+  bun "$PKG/src/cli.ts" browser start >/dev/null 2>&1 || { echo "couldn't start the agents' Chrome: run 'dirpush browser start' and read its error" >&2; exit 1; }
+fi
+if [ -z "$AB_PROFILE" ] && up; then
   exec perl -e 'alarm shift; exec @ARGV or die "cannot run $ARGV[0]: $!\n"' "${AB_TIMEOUT:-90}" agent-browser --session "${AB_SESSION:-default}" --cdp "$PORT" "$@"
 fi
 for host in mail.google.com gmail.com www.gmail.com inbox.google.com \

package/scripts/google-login

@@ -13,5 +13,5 @@ bun "$PKG/src/cli.ts" browser stop >/dev/null 2>&1
 # so `dirpush checks` can carry on. A separate --user-data-dir is its own Chrome process; the human's Chrome is untouched.
 for i in 1 2 3 4 5 6 7 8 9 10; do [ -L data/browser-profile/SingletonLock ] || break; sleep 0.5; done
 "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --user-data-dir="$PWD/data/browser-profile" \
-  --use-mock-keychain --password-store=basic --no-first-run --no-default-browser-check \
+  --use-mock-keychain --password-store=basic --no-first-run --no-default-browser-check --disable-extensions --disable-sync \
   "https://accounts.google.com/ServiceLogin?continue=https%3A%2F%2Fwww.google.com%2F" >/dev/null 2>&1

package/src/browser.ts

@@ -46,6 +46,9 @@ export async function browserStatus() {
   }
 }
 
+/** Flags every Chrome on the agents' profile gets (scripts/google-login repeats them). */
+export const AGENT_CHROME_FLAGS = ["--use-mock-keychain", "--password-store=basic", "--no-first-run", "--no-default-browser-check", "--disable-extensions", "--disable-sync"];
+
 export async function startBrowser() {
   const now = await browserStatus();
   if (now.running) return { ...now, started: false };
@@ -53,8 +56,9 @@ export async function startBrowser() {
   const pac = `data:application/x-ns-proxy-autoconfig;base64,${Buffer.from(pacScript()).toString("base64")}`;
   // Plain Chrome, headed, no automation flags: Google sign-in and bot checks see a normal browser. The keychain
   // flags match agent-browser and scripts/google-login: the profile's cookies are encrypted with that key, so
-  // without them every saved session would be unreadable.
-  Bun.spawn([CHROME, `--user-data-dir=${PROFILE}`, `--remote-debugging-port=${BROWSER_PORT}`, `--proxy-pac-url=${pac}`, "--use-mock-keychain", "--password-store=basic", "--no-first-run", "--no-default-browser-check"], {
+  // without them every saved session would be unreadable. No extensions and no sync: signing into Google here turns on
+  // Chrome sync, which copies the human's own extensions in (one with debugger access hijacked every agent session).
+  Bun.spawn([CHROME, `--user-data-dir=${PROFILE}`, `--remote-debugging-port=${BROWSER_PORT}`, `--proxy-pac-url=${pac}`, ...AGENT_CHROME_FLAGS], {
     stdout: "ignore", stderr: "ignore", stdin: "ignore",
   }).unref();
   for (let i = 0; i < 40; i++) {
@@ -136,7 +140,7 @@ export function strongPassword() {
  * New account password: generated here, typed into every given field of the open tab on `url`'s site, checked,
  * then saved to the vault as `name`. Returns no secret.
  */
-export async function newPassword(name: string, url: string, username: string, selectors: string[]) {
+export async function newPassword(name: string, url: string, username: string, selectors: string[], loginUrl = url) {
   if (!selectors.length) throw new Error("pass the password field selector(s), e.g. 'input[type=password]'");
   const page = await pageOn(url);
   const pw = strongPassword();
@@ -145,6 +149,7 @@ export async function newPassword(name: string, url: string, username: string, s
   const lengths = JSON.parse(ab(["eval", `JSON.stringify(${JSON.stringify(selectors)}.map((s) => document.querySelector(s)?.value.length ?? -1))`]));
   const got = (typeof lengths === "string" ? JSON.parse(lengths) : lengths) as number[];
   if (got.some((n) => n !== pw.length)) throw new Error(`password fields not filled (lengths ${got.join(", ")}); nothing saved`);
-  ab(["auth", "save", name, "--url", url, "--username", username, "--password-stdin"], pw);
+  // The vault keeps the sign-in page: `browser login` opens on it later, so a reset or sign-up URL there breaks logins.
+  ab(["auth", "save", name, "--url", loginUrl, "--username", username, "--password-stdin"], pw);
   return { vault: name, username, fields: selectors.length, page: page.url.slice(0, 200), saved: true };
 }

package/src/cli.ts

@@ -79,6 +79,7 @@ const { values: flags, positionals } = parseArgs({
     source: { type: "string" },
     job: { type: "string" },
     url: { type: "string" },
+    "login-url": { type: "string" },
     username: { type: "string" },
     rel: { type: "string" }, // registry set-link
     samples: { type: "string" },
@@ -655,8 +656,8 @@ const commands: Record<string, (() => Promise<unknown> | unknown) | undefined> =
   "browser stop": () => stopBrowser(),
   "browser login": () => vaultLogin(arg(0, "vault-name")),
   "browser password": () => {
-    if (!flags.url || !flags.username) throw new Error("browser password <vault-name> --url <login-url> --username <email> <field-selector…>");
-    return newPassword(arg(0, "vault-name"), flags.url, flags.username, args.slice(1));
+    if (!flags.url || !flags.username) throw new Error("browser password <vault-name> --url <page-url> --username <email> [--login-url <sign-in page>] <field-selector…>");
+    return newPassword(arg(0, "vault-name"), flags.url, flags.username, args.slice(1), flags["login-url"]);
   },
   async "serve"() {
     const { serve } = await import("./server");
@@ -730,7 +731,7 @@ const HELP: [string, [string, string][]][] = [
     ["google-login", "the human signs into Google once in the agents' Chrome profile"],
     ["browser start | status | stop", "the dedicated Chrome (real profile, Google services blocked) agents drive"],
     ["browser login <vault-name>", "fill a saved login into the open tab on that site (password never shown)"],
-    ["browser password <vault-name> --url u --username e <selector…>", "new account: generate, fill, verify and save a password (never shown)"],
+    ["browser password <vault-name> --url u --username e [--login-url u] <selector…>", "new password (sign-up or reset): generate, fill, verify and save it (never shown); --login-url when the page isn't the sign-in page (e.g. a reset link)"],
   ]],
   ["Other", [
     ["dr show | dr refresh [--all]", "Domain Rating history (refresh needs AHREFS_API_KEY)"],