# LinkShell Web A browser client for the existing LinkShell host and gateway. The normal entry point uses real pairing, encrypted tunnels and `@linkshell/client-core` state. `?demo=1` is a separate, explicitly labeled UI demonstration with local fixtures. The workspace uses shadcn/ui (Radix): sidebar, tables, cards, tabs, forms, menus, dialogs, status badges and loading/empty/error states. Its desktop visual system takes cues from Linear: quiet neutral surfaces, spacious grouped navigation, subtle selection states and restrained indigo actions with white text. The sidebar uses a 264px desktop width and explicit 40px navigation rows, shared by its desktop and mobile presentations. `src/theme.ts` provides separate light/dark desktop tokens without changing the mobile palette. `components.json` and the `@/*` alias configure the component CLI; layout stays in the existing CSS layers. ```bash pnpm install pnpm dev:web pnpm --filter @linkshell/web build pnpm --filter @linkshell/web lint pnpm --filter @linkshell/web test ``` Output: `apps/web/dist`. The gateway Docker image and npm package bundle this client at `/`, alongside `/v2/connect` and `/healthz`. Run `pnpm --filter @linkshell/gateway build:web` when running the gateway from a checkout. Production uses `https://gateway.itool.tech`. No separate web deployment is required. The Screens page shows a searchable, aligned list of computers with connection status and quality/permission controls. The pencil beside a name lets users name each computer, edit that name or restore the original. Names persist in the current browser, keyed by gateway and device identity; they do not rename the system or sync to other browsers or phones. Opening a desktop navigates to its own detail URL and starts its viewer. Reloading preserves the target computer; the back control returns to the list. The detail page can stop or reconnect, select a display, resolution, frame-rate ceiling and codec preference, or enter focus/fullscreen. Focus mode retains the existing viewer connection, and fullscreen keeps settings available. The list and workspace share a tunnel per computer; leaving the detail page releases its viewer and unused connections. Offline computers remain visible without opening a tunnel. ## Functions - Official email/password and GitHub/Google sign-in, automatic account token refresh, account computer discovery and sign-out. OAuth opens a separate window and returns to the initiating workspace with PKCE. Allow the exact `https://gateway.itool.tech/?linkshell-auth-callback=1` URL in Supabase (or the same path/query on your account-enabled workspace origin); keep the existing iTool, CLI and mobile callbacks. Local `127.0.0.1` builds use the existing `/linkshell/callback` loopback entry. - Official or custom gateway pairing by code, pasted link, QR image or camera; persisted browser identity and paired computers; switching computers and revoking devices. - Session search/filter, archived sessions, projects, new sessions and worktrees, history pagination, streaming messages, draft persistence, attachments, queue editing/reordering, interrupt, steer, rename, archive, delete, fork, and supported handoff takeover/release. - Dynamic slash commands and Skills from the shared mobile command catalog and Host reports. Command palette and inline suggestions support keyboard navigation. MCP and connector commands go through the agent; their output uses the same rich timeline. Available commands and settings depend on the connected agent's capabilities. - Dynamic model/permission settings, permission approvals and structured questions, Markdown, images, links, tool output and diffs, plans, usage, goals, workflows, background tasks and subagent conversations. - Host files, text/image viewing, directory selection, upload and directory creation; worktree status/removal; xterm.js terminals with startup commands, rerun, file upload/paste, font sizing, input, resize and reconnect replay (including framed replay from the current host). - Remote screen viewer and input through the existing host screen service; port previews through an isolated browser origin, streaming HTTP/SSE and WebSocket forwarding over encrypted host streams; WebRTC data-channel transport when available. - Multi-tab ownership: one tab holds the browser device connection. Another tab can explicitly take it over. Browser UI does not independently reimplement authorization, agent execution or the session event model. Host actions remain authoritative. Unsupported agent capabilities are not advertised as available. ## Remote screen transport `src/live/Video.tsx` calls `screen.start`, fetches the host viewer HTML through `HostStreams` and mounts it in a sandboxed iframe. Its WebSocket shim only forwards the selected loopback port's `/stream`. It keeps the page's controls and input behavior. Only a small receive-statistics report crosses back to React every two seconds while visible; video frames stay in the browser media pipeline. On a Mac, that page receives a WebRTC video track directly from LinkShell.app into `