0xWheatyz/handler
1
0
Fork 0
mirror of https://github.com/0xWheatyz/handler.git synced 2026-08-30 03:31:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat(login): open the login URL in an OAuth-style popup, not an iframe

Browse Source 
claude.com refuses to be embedded in an iframe (X-Frame-Options), so the inline
frame just showed a blocked page. Replace it with a small popup window, like a
"Sign in with Google" flow: the "Log in to Claude" click opens a blank popup
(within the user gesture, so it isn't popup-blocked) and, once login_start
returns the URL, the popup is navigated to it. Buttons to reopen the window or
open the URL in a new tab remain as fallbacks, and the popup is closed on
success/error. README updated to match. Rebuilt static export.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YKVyBmKvWDVgrFC9WER2f2
This commit is contained in:
Claude
2026-07-15 16:09:30 +00:00
parent 1fe260ebe4
commit cd49dab5a3
8 changed files with 84 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+11 -7
View File
@@ -243,13 +243,17 @@ pane logs it in from the browser — the same command-queue handoff every other
action uses:
1. **Log in to Claude** enqueues a `login_start` command. The worker opens `claude` in a
dedicated tmux session in the control container, sends `/login`, selects the **Claude
account with subscription** option, and scrapes the pane for the `claude.com`
authorization URL — returned in the command result.
2. The UI opens that URL in an embedded frame (with a new-tab link as a fallback, since
claude.com may refuse to be framed). You authorize and Claude gives you a code.
3. **Finish login** enqueues a `login_submit` command carrying the code; the worker feeds
it into the still-open session, waits for claude to exchange it, and reports success.
dedicated (wide) tmux session in the control container, navigates whatever onboarding a
fresh `claude` shows (theme picker, folder-trust) to the **Claude account with
subscription** login, and scrapes the pane for the `claude.com` authorization URL —
returned in the command result.
2. The UI opens that URL in a small **OAuth-style popup window** (like "Sign in with …";
claude.com refuses to be embedded in an iframe, so a popup is the right surface), with
a new-tab link as a fallback. You authorize there and Claude gives you a code.
3. **Finish login** enqueues a `login_submit` command carrying the code; the worker pastes
it into the still-open session and presses Enter separately (a long code plus an
immediate Enter races the TUI and never submits), then confirms by watching claude write
its credentials.
The login session lives in the control container, and Claude's credentials land under the
`handler` user's home on the `/var/lib/handler` volume — so the login **persists** across