/login works in the chat window

Officer authenticates claude with a Claude SUBSCRIPTION over OAuth, and that is a browser round trip: open
a URL, authorise, paste a code back. It was the one part of running an agent a browser-only user could not
do from the browser — the answer was "open a terminal panel and drive the CLI by hand", which works, and is
a strange thing to ask of somebody whose entire session is a web page.

It needs no pty. `claude auth login` behaves identically through plain pipes, verified by capturing its raw
bytes, so this is an ordinary subprocess with two reads and one write: spawn, read until the URL, wait for
the person, write the code to stdin.

The parsing is the only non-obvious part. The CLI wraps the URL in an OSC-8 hyperlink escape AND prints it
again as visible text, so `https://\S+` returns two URLs concatenated with no separator between them.
Stripping the escape wrappers first leaves exactly one. Written against captured bytes rather than against
what the terminal appeared to show.

Three decisions worth keeping:

NOT under /auth. totality.ts exempts that prefix from the permission gate entirely, and correctly — it is
where a caller goes to BECOME authenticated. Mounted there, an unauthenticated POST could have started a
login as the owner. Verified after moving it: unauthenticated POST /api/claude-auth is 401.

On the `chat` grant rather than its own. The pairing is exact: an account that may use the agent must be
able to authenticate the agent, and an account that may not has nothing to authenticate. `confined` then
carries the rest for free — authorize.ts drops a confined grant for an account with no osUser, which is
precisely the account that cannot hold credentials of its own.

Nothing Anthropic-shaped is inherited by the child. For the owner those variables point at the local proxy,
whose whole job is swapping a shared secret for the owner's bearer token — handing them to a login is how
you get a success that authenticates nothing. A member's login runs through setpriv --reset-env as their own
Linux user, into their own home, because their turns bill their own subscription and that only holds if the
credential is theirs.

Pending logins are in memory on purpose: one is worthless once the process holding its PKCE verifier dies,
so persisting it would store a row that can only ever be stale. Ten-minute reaper, one per account, and the
dialog abandons its own on close so a dismissed dialog does not leave claude parked on a read of stdin.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

This commit is contained in:

pastilhas

2026-08-21 20:47:10 +00:00

co-authored by

Claude Opus 5

parent 530e5880e1

commit 8917f36be5

5 changed files with 417 additions and 3 deletions

									
										src/servers/hono.ts
									
		+2
		
												View File
												
				@@ -41,6 +41,7 @@ import { queueRouter } from './api/queue/queue';

				// registry's claim on '/browser' in the same commit, or assertPermissionTotality refuses to boot.

				import { bugReportRouter } from './api/bug-report/bug-report';

				import { agentStatusRouter } from './api/agent-status/router';

				import { claudeLoginRouter } from './api/auth/claude-login';

				import { chatRouter } from './api/chat/chat';

				import { commandHqRouter } from './api/command-hq/router';

				import { pipelineJobsRouter } from './api/tasks/pipeline-jobs-routes';

				@@ -149,6 +150,7 @@ const PROTECTED_MOUNTS: [prefix: string, router: ReturnType<typeof createRouter>

				  ['/queue', queueRouter],

				  ['/bug-report', bugReportRouter],

				  ['/agent-status', agentStatusRouter],

				  ['/claude-auth', claudeLoginRouter],

				  ['/chat', chatRouter],

				  ['/command-hq', commandHqRouter],

				  ['/pipeline-jobs', pipelineJobsRouter],