Skip to content

feat(browser): point the owner to the window when a sign-in fails - #140

Merged
httpsphl merged 2 commits into
mainfrom
feat/browser-window-hints
Oct 3, 2026
Merged

httpsphl merged 2 commits into
mainfrom
feat/browser-window-hints

Conversation

@httpsphl

@httpsphl httpsphl commented Oct 3, 2026

Copy link
Copy Markdown
Owner

Follow-up to #139. In real use, some sites only let the owner sign in through Sign in in a window, but the app only mentioned that option under the live screen. That text disappears as soon as the owner takes control to sign in.

App (en, pt-BR, es)

  • New line under the bot's request for help and under the "You are in control" bar: "Site won't let you sign in here? Use Sign in in a window, and close the window when you're done."
  • The help card in the chat now adds: "If the site won't let you sign in there, use Sign in in a window in the browser panel."

Bot

  • New bullet in the bot rules (workspace/files.rs): when a site refuses to sign in to its browser ("this browser may not be secure", a sign-in that fails or loops), the bot asks with browser_ask_owner, tells the owner in their language to use the window button, then opens the page again.
  • The browser_ask_owner description says the same.

Docs

  • The README feature list mentions the window.
  • Spec 21.11 describes the hints and the bot rule.

Checks: cargo fmt, clippy, the full test suite and pnpm check pass. New test in window.test.tsx.

Manual check with real Claude Code: ask a bot to open a site that refuses its browser. It should ask for help and mention signing in in a window.

The window sign-in only showed under the live screen, which goes away
once the owner takes control to sign in. Now a line under the help
callout and the "in control" bar says to use Sign in in a window when
the site won't let them in, and the help card in the chat says the
same. The bot's rules and browser_ask_owner tell it to suggest the
window when a site refuses to sign in to its browser, and to open the
page again afterwards. README and spec 21.11 describe it.
@httpsphl
httpsphl enabled auto-merge October 3, 2026 21:01
On a busy CI runner chrome://version took over 2 s to load, the read
gave up, and the brands went empty again.
@httpsphl
httpsphl merged commit dd458a7 into main Oct 3, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant