Browser-based graphical shell and control plane for a Linux server you own — real terminal, file manager, live metrics and BYOK AI in one mobile-first workspace. Next.js 16 · React 19 · node-pty · Tailwind v4 · shadcn/ui. Public alpha, self-hosted.
TypeScript browser-shellcontrol-planefile-managerhomelabmobile-firstnextjsptyreactself-hostedserver-managementshadcn-uisysadmintailwindcssterminaltypescriptvpsweb-desktopweb-terminal
fix(oauth): keep registered consent within narrow viewports
Abdurrahman Fakhrul47938b8ca4cd
diff --git a/app/oauth/authorize/page.tsx b/app/oauth/authorize/page.tsxindex 7d0b9183..4809364e 100644--- a/app/oauth/authorize/page.tsx+++ b/app/oauth/authorize/page.tsx@@ -15,7 +15,7 @@ export const dynamic = "force-dynamic";function Shell({ children }: { children: React.ReactNode }) {return (<main id="main-content" className="grid min-h-dvh place-items-center bg-background p-4">- <div className="w-full max-w-md rounded-2xl border border-border bg-card p-6 shadow-xl">{children}</div>+ <div className="min-w-0 w-full max-w-md rounded-2xl border border-border bg-card p-6 shadow-xl">{children}</div></main>);}diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.mdindex 05ae95a2..4e59730a 100644--- a/docs/CHANGELOG.md+++ b/docs/CHANGELOG.md@@ -8,6 +8,7 @@ this is the *what*, and it is what Settings → Account → About shows as “Wh**Fixed**+- `oauth` keep registered consent within narrow viewports- `security` enforce live delegated grants and bound provider and OAuth state- `security` close remaining repository scan trust boundariesdiff --git a/docs/PROGRESS.md b/docs/PROGRESS.mdindex 1b74cc8e..ffef58e6 100644--- a/docs/PROGRESS.md+++ b/docs/PROGRESS.md@@ -1,6 +1,6 @@## 2026-10-09: Close the eight findings from the independent security rescan-The completed rescan of `dac56bdf` found six Medium and two Low issues, with no High findings. Named MCP integrations now reuse the private endpoint-bound transport and recursive credential redaction rather than embedding bearer headers in an unbound server. OAuth consent accepts only server-generated registered client identities and their exact callbacks, preventing manual/pruned client IDs from aliasing another principal. The obsolete manual Client ID guidance is removed; clients must register and reconnect for new consent.+The completed rescan of `dac56bdf` found six Medium and two Low issues, with no High findings. Named MCP integrations now reuse the private endpoint-bound transport and recursive credential redaction rather than embedding bearer headers in an unbound server. OAuth consent accepts only server-generated registered client identities and their exact callbacks, preventing manual/pruned client IDs from aliasing another principal. The obsolete manual Client ID guidance is removed; clients must register and reconnect for new consent. The browser proof also exposed the consent grid's minimum-content width overflowing a 390px viewport; its card now permits shrinking, retaining readable content and the desktop/mobile reflow assertion.Async subagents, on-demand local workers and flows retain the initiating durable grant, profile, tool allowlist and argument constraints. Shared execution authority revalidates that grant and the deployment ceiling before every model round/action; browser flows retain their signed device session so revocation, demotion, logout, expiry and cookie-epoch changes stop later steps. External A2A workers reload their durable profile, intersect live scope and abort active profile tasks on token removal. Fixed-workflow lifecycle controls use one filter for both model advertisement and invocation.