Public: anyone can read this; the crew can change it.
A session's list on the account page shows each signed-in browser with when it last acted, and signs one out in one tap #14166
Check · Review · Land · Live done — Landed and live in production.
The account page (Settings › Tokens) now names each signed-in browser in plain words, such as "Firefox on Linux" or "Safari on iPhone". Each row says when that browser signed in and when it was last used.
shipped production is serving it deploy 4adf612
1 earlier comment · 1 event
The account page (Settings › Tokens) now names each signed-in browser in plain words, such as "Firefox on Linux" or "Safari on iPhone". Each row says when that browser signed in and when it was last used. The browser you are reading from is marked "this browser" and has no Sign out on its own row, so you cannot end it by mistake; the menu's Sign out is still there for that.
What was already on main: the session list, the confirm-then-POST sign-out at /settings/sessions/<id>/delete, and the opaque row id, which is not the cookie's secret. Cross-account sign-out was already refused as "not found" on the page, the API and the MCP. That refusal is tested by "nobody signs out a browser that is not theirs" and the non-owner test in test/signins.test.ts, which covers the issue's fourth item.
What changed:
- Browser name:
src/auth/browser_name.tsturns a User-Agent into a name from a short fixed list. Only that name is stored, never the raw header; a migration (with its pin) adds one nullablesession.browsercolumn. - When it's recorded:
sessionOffills the name on a session's first use, the same way it fills the address. Sessions not used since this change read "A browser". - Page:
src/web/pages/account.tsshows the name, "signed in … · last used …", and no Sign out on the current row. The other rows' Sign out buttons now have labels that tell them apart. - Other surfaces: the API and the MCP
sessionstool return the newbrowserfield without any tool change. The terminal sign-ins screen shows the name in place of "web browser". - Docs: a new
docs/features/signed-in-browsers.md, linked from the features index.
Tests:
test/browser-name.test.tschecks real User-Agent strings against their names.- A new test in
test/signins.test.tschecks that both browsers' names and "last used" appear, that the cookie secret never appears in the HTML, and that the row is gone after sign-out. - The existing assertion that counted two Sign out buttons now expects one. The old count described the behaviour this issue changes, so the test was updated rather than the code.
Not done: I didn't block a direct POST that ends your own current session. Only the button on its own row is gone, which is what stops the mistake the issue describes. I didn't add a look either: /settings/tokens isn't in app.looks.
Checks: bun x tsc --noEmit passes, and so do bun scripts/gate.ts and bun scripts/design-lint.ts. The change reaches src/http/server.ts, so scripts/fast.ts named 2,434 test files; I ran the 20 that cover it instead, including test/mcp-size.test.ts, and all 212 tests passed.
Try it: sign in on the preview in two browsers, open /settings/tokens, and sign the other one out.
🤖 Generated with Claude Code
One change needed, on the design system. The behaviour, migration, docs and tests are sound: the name comes from a fixed set, only that name is stored, output is escaped, and the cross-user revoke refusal is already tested on main.
Fix first: the current row says "this browser" twice (the badge in the title and a muted span in the trail). DESIGN.md principle 1 says nothing explains itself twice. Keep the badge and drop the trail text, or the reverse, and update the test's this browser assertion to match.
Each row in the account page's "Signed-in browsers" list now names the browser in plain words, for example "Firefox on Linux". It also says when the browser signed in, when it was last used, and where it signed in from. Every other browser has a one-tap Sign out. The row for the browser you are using has no Sign out, so a slip can't end your own session from this page; the menu's Sign out is still there for that.
Change from review: the current row said "this browser" twice, once as a badge in the title and again as muted text at the end of the row. The row now keeps only the badge and the end of the row is empty (src/web/pages/account.ts). The assertion in test/signins.test.ts now checks for the badge text "This browser" and fails if the old muted span comes back.
The gate, tsc --noEmit, bun scripts/design-lint.ts and bun test test/signins.test.ts (12 tests) all pass.
To try it: sign in from two browsers and open /settings/tokens. The browser you're using carries the "This browser" badge and has no button; the other has Sign out.
🤖 Generated with Claude Code
The earlier ask, that the current row said "this browser" twice, is met: only the badge remains and the trail is empty, and the test fails if the muted span returns. The earlier head is not in the clone, so I read the whole change as shown. The name comes from a fixed list and only that short name is stored. The migration has its pin. The secret never reaches the page. The terminal screen carries the name. The how-to is in docs/features, not README. Non-blocking: a direct POST can still end your own current session, as the description says.
The account page (Settings › Tokens) now names each signed-in browser in plain words, such as "Firefox on Linux" or "Safari on iPhone". Each row says when that browser signed in and when it was last used. The browser you are reading from is marked "this browser" and has no Sign out on its own row, so you cannot end it by mistake; the menu's Sign out is still there for that.
What was already on main: the session list, the confirm-then-POST sign-out at
/settings/sessions/<id>/delete, and the opaque row id, which is not the cookie's secret. Cross-account sign-out was already refused as "not found" on the page, the API and the MCP. That refusal is tested by "nobody signs out a browser that is not theirs" and the non-owner test intest/signins.test.ts, which covers the issue's fourth item.What changed:
src/auth/browser_name.tsturns a User-Agent into a name from a short fixed list. Only that name is stored, never the raw header; a migration (with its pin) adds one nullablesession.browsercolumn.sessionOffills the name on a session's first use, the same way it fills the address. Sessions not used since this change read "A browser".src/web/pages/account.tsshows the name, "signed in … · last used …", and no Sign out on the current row. The other rows' Sign out buttons now have labels that tell them apart.sessionstool return the newbrowserfield without any tool change. The terminal sign-ins screen shows the name in place of "web browser".docs/features/signed-in-browsers.md, linked from the features index.Tests:
test/browser-name.test.tschecks real User-Agent strings against their names.test/signins.test.tschecks that both browsers' names and "last used" appear, that the cookie secret never appears in the HTML, and that the row is gone after sign-out.Not done: I didn't block a direct POST that ends your own current session. Only the button on its own row is gone, which is what stops the mistake the issue describes. I didn't add a look either:
/settings/tokensisn't inapp.looks.Checks:
bun x tsc --noEmitpasses, and so dobun scripts/gate.tsandbun scripts/design-lint.ts. The change reachessrc/http/server.ts, soscripts/fast.tsnamed 2,434 test files; I ran the 20 that cover it instead, includingtest/mcp-size.test.ts, and all 212 tests passed.Try it: sign in on the preview in two browsers, open
/settings/tokens, and sign the other one out.🤖 Generated with Claude Code
Closes #14154