Desktop renderer experience
The desktop renderer is the user-facing workspace for projects, worktrees, terminals, browsers, files, reviews, automations, and coding agents. It combines shared session state with focused work areas and overlays, then uses typed preload capabilities for native work. See Desktop application platform, Relay protocol and transport, Desktop persistence and lifecycle, Command-line and headless runtime, and Browser automation and embedded web for the surrounding systems.
Renderer shell and views
Application shell
The application shell joins the title bar, app navigation, workspace list, active page, workbench, right sidebar, status bar, and global overlays. The active view chooses the page and chrome that the user sees. Shared services keep workspace resources active across navigation. Recovery boundaries let one failed surface remount without blanking the whole app.
The shell adapts to the host window. Custom title bars reserve space for native window controls and macOS traffic lights. Workspace pages can place tabs at the top, while full pages keep a title bar. Root surfaces host prompts, dialogs, notices, onboarding, updates, and other cross-page actions only when their state allows them to appear.
References: src/…/App.tsx• L48-88 src/…/App.tsx• L101-140 src/…/AppWorkspaceShell.tsx• L169-230 src/…/AppWorkspaceShell.tsx• L246-310 src/…/AppRootSurfaces.tsx• L113-180
Application navigation
The left side provides two linked navigation areas: an optional app rail and the workspace list. The rail gives fast access to Workspaces, Help, and Settings. It folds Help and Settings into More when space is tight, keeps one keyboard tab stop, and returns focus when its layout changes.
Workspaces navigation groups and filters project work by host, source, lineage, sleep state, and visibility. It can switch between workspace rows and agent activity. Leaving Settings uses the page discard guard, while choosing Workspaces returns to a live workspace and opens the list when needed.
References: src/…/AppShellLeftColumn.tsx• L5-17 src/…/AppShellLeftColumn.tsx• L18-105 src/…/AppRail.tsx• L31-55 src/…/AppRail.tsx• L71-123 src/…/AppRail.tsx• L181-256 src/…/app-rail-navigation.ts• L47-99 src/…/index.tsx• L61-169
Workspace workbench
The workspace workbench presents terminal, browser, editor, simulator, and agent-session tabs in the selected worktree. Tabs select resources and pane groups select their layout. Users can open, close, pin, name, move, and split tabs without losing the surrounding workspace.
The workbench separates visibility from ownership. A hidden terminal, browser, or agent surface can remain available while it has live work. A resource retires only when no pane or tab owns it. This lets tab activation change what is shown without creating a second live surface.
This diagram shows how shared state becomes an interactive surface and how user actions return to that state.
flowchart LR
S[Shared session state] --> W[Workspace view]
W --> T[Tabs and pane groups]
T --> P[Terminal, browser, editor, simulator, or agent pane]
P --> A[User action or host event]
A --> S
References: src/…/TabGroupPanel.tsx• L40-80 src/…/TabGroupPanel.tsx• L147-250 src/…/TabGroupPanel.tsx• L258-415 src/…/tabs-slice-contract.ts• L27-66 src/…/tabs-slice-contract.ts• L145-198
Product pages
Full-page views extend the workbench with project and account work. Main routes cover tasks, automations, activity, settings, skills, artifacts, workspace space, and mobile controls. They share the shell and store but own their page-level selection and recovery state.
These pages connect outside work to a local workspace. Automation views move between automation lists, details, run history, run details, and recovery notices. Artifact views handle account state, paging, detail drawers, deletion, and public-link sharing. Onboarding and feature tips wait for the state that makes them useful.
References: src/…/AppWorkspaceShell.tsx• L27-58 src/…/AppWorkspaceShell.tsx• L138-166 src/…/AutomationsPageSurface.tsx• L160-199 src/…/AutomationsPageSurface.tsx• L236-372 src/…/ArtifactsPage.tsx• L23-54 src/…/ArtifactsPage.tsx• L170-232
Agent conversation workspace
The agent conversation workspace places a native conversation beside terminal and other worktree surfaces. It shows transcript history, live tool work, approvals, questions, attachments, session choices, background tasks, goals, and launch or recovery state.
The conversation keeps confirmed history separate from delivery state. Unsent text, queued follow-up text, prompts, and drafts remain distinct from confirmed transcript messages. Host availability and delivery notices stay in the conversation so a failed launch or send has a clear next action. A missing host, failed read, blocked send, or unavailable agent can replace only the affected part of the surface.
References: src/…/NativeChatStructuredSession.tsx• L82-154 src/…/NativeChatStructuredSession.tsx• L171-210 src/…/NativeChatStructuredSession.tsx• L259-333 src/…/NativeChatStructuredSession.tsx• L334-407
Agent activity view
The activity view turns agent work into a page that can be scanned across workspaces. Its shared projection builds all threads and live threads from the same activity data. The page adds search, read filters, grouping, compact mode, child-agent visibility, multi-select actions, and jumps to the owning workspace.
Selecting a thread shows its identity and either the existing live terminal or a clear unavailable state. During a selection change, the page stages the next terminal in a second portal slot before swapping it into view. The portal moves the existing terminal surface. It does not create a second PTY or terminal owner.
References: src/…/ActivityPrototypePage.tsx• L31-137 src/…/ActivityPrototypePage.tsx• L146-221 src/…/ActivityPrototypePage.tsx• L244-315 src/…/ActivityPrototypePage.tsx• L317-367 src/…/activity-thread-projection.ts• L30-45 src/…/activity-thread-projection.ts• L70-149 src/…/activity-thread-list-pane.tsx• L294-405 src/…/activity-thread-detail-pane.tsx• L67-139
Agent launch controls
Agent launch controls turn an agent choice into a launch or chat setup surface. The picker supports search, agent and model choices, a blank terminal choice, saved defaults, surface selection, permissions, arguments, and effort or speed options.
The same picker serves a new tab, a form, an automation, or a bot setup flow. It keeps the draft separate from the host action until the user chooses to launch. Catalog loading and installation gaps stay visible so a missing agent does not look like a failed launch. Settings can also show an update action for a supported user-owned CLI, with retry and failure details when the update fails.
References: src/…/AgentLaunchPicker.tsx• L65-134 src/…/AgentLaunchPicker.tsx• L171-205 src/…/AgentLaunchPicker.tsx• L275-411 src/…/AgentCliUpdateButton.tsx• L21-79 src/…/use-agent-cli-update.ts• L15-53
Editor and review surfaces
Editor surfaces support file editing, document preview, diffs, checks, diagrams, notebooks, and conflict repair. A tab chooses the surface that fits the file and its current state, so the user can move from discovery to editing, review, save, or handoff within the worktree.
The editor makes outside changes explicit. It can compare disk content with the local buffer, reload from disk, keep local edits, or explicitly overwrite newer disk content. Conflict review shows unresolved files as a group and opens one file for focused repair.
References: src/…/EditorContent.tsx• L49-109 src/…/EditorContent.tsx• L141-200 src/…/EditorContent.tsx• L203-317 src/…/TabGroupPanel.tsx• L382-402
Embedded browser surfaces
Browser panes embed local, remote, streamed, and workspace-owned web content inside the workbench. The renderer ties each page to its workspace and runtime owner, then selects a local, client-hosted, or streamed surface.
Local pages wait for the correct profile and SSH route before they load. Remote pages use a host-owned surface. Pages can remain mounted when automation, mobile control, or remote viewing needs them. Mobile control locks input until the user takes the page back. Load stalls, unavailable hosts, and failed routes remain visible as page feedback.
References: src/…/browser-workspace-pane.tsx• L33-96 src/…/browser-workspace-pane.tsx• L98-167 src/…/browser-workspace-pane.tsx• L170-229
Root overlays
Root overlays provide actions that remain available while the user changes pages. They include the floating workspace, status bar, quick-open and worktree palettes, onboarding, update notices, notification cards, dictation, crash reporting, recent-tab switching, browser prompts, feature prompts, and agent resume reports.
The root keeps these surfaces in a stable sibling order and mounts them only when their state allows them to appear. Lazy surfaces load on demand. Each overlay or modal has its own recovery boundary so one failure does not remove unrelated controls. Restart resume reports stay open when they need user action. They show progress, failures, retry or dismiss actions, and links to the related chat or setting.
References: src/…/App.tsx• L101-140 src/…/AppRootSurfaces.tsx• L113-180 src/…/AppRootSurfaces.tsx• L181-235 src/…/AppRootSurfaces.tsx• L296-401 src/…/NativeChatResumeToastHost.tsx• L22-81 src/…/NativeChatResumeToastHost.tsx• L106-234 src/…/NativeChatResumeToast.tsx• L133-291
Renderer state and lifecycle
Shared renderer state
The renderer uses one application store as the coordination point for product state and view state. It combines repository and worktree data with tabs, terminals, editors, browsers, tasks, agents, runtimes, reviews, settings, drafts, usage, and attention state. Views read this state and send actions back through it so navigation, panes, sidebars, and overlays remain aligned.
The store is the renderer's current projection of local work, host events, persisted session data, and user choices. It is not a native service. Host-owned layout data can update workspace placement, while the renderer keeps window-owned pane and surface state.
References: src/…/index.ts• L98-171 src/…/tabs-slice-contract.ts• L27-66 src/…/workspace-layout-frame-store-patch.ts• L127-194
Active workspace services
Active workspace services keep workspace data current even when the component that displays it is not mounted. They sync tabs, refresh visible reviews, watch files, poll Git status, scan ports, retain agent state, and publish attention updates.
The app keeps these services above page surfaces and gates workspace-specific work on session readiness. This prevents a page switch or hidden pane from stopping work that belongs to the workspace. Optional dashboard and paired-device publication run only when the desktop exposes the capability and the feature needs it. Background chat status and attention also stay active when no chat pane is mounted.
References: src/…/AppBackgroundServices.tsx• L24-60 src/…/use-app-shell-services.ts• L31-64 src/…/ActiveWorkspaceSyncGate.tsx• L8-19
Startup hydration
Startup hydration turns saved desktop data into the first usable session. It loads settings and UI choices, restores local catalogs and workspace session data, waits for native-chat drafts, reconciles tab, editor, and browser models, discovers runtime session hosts, reconnects eligible hosts, and restores terminal sessions. Remote refresh can continue after the critical path so network delay does not block the first useful window.
Hydration changes the source of layout truth at a defined handoff. The restored session supplies the initial view, then host-owned layout frames replace it where those hosts own the layout. Normal session writes remain locked until hydration and terminal restoration succeed. If a step fails, degraded recovery protects the last good disk state.
This diagram shows the startup order and the point at which durable writes become safe.
flowchart LR
A[Settings and UI] --> B[Local catalogs]
B --> C[Workspace session and drafts]
C --> D[Tabs, editors, and browsers]
D --> E[Runtime host discovery and reconnect]
E --> F[Terminal restore]
F --> G[Host-owned layout handoff]
G --> H[Unlock session writes]
E --> I[Deferred remote refresh]
References: src/…/use-app-startup-hydration.ts• L51-69 src/…/use-app-startup-hydration.ts• L95-139 src/…/use-app-startup-hydration.ts• L200-219 src/…/use-app-startup-hydration.ts• L274-297
Session persistence
Session persistence saves the durable workspace view by host. Debounced writes capture normal changes. A shutdown checkpoint captures the view before close while terminal buffers and sleeping agent records are still available. The close path is guarded because one close can produce more than one unload event, while a hard kill can skip unload.
The renderer listens for close requests at the app root. This keeps close handling active on Landing and full-page views where the workbench is not mounted. Periodic capture narrows the loss window for agent resume records without serializing terminal scrollback during normal use.
References: src/…/use-app-session-persistence.ts• L41-65 src/…/use-app-session-persistence.ts• L67-139 src/…/use-app-session-persistence.ts• L141-155
Tab and resource lifecycle
Unified tabs give terminals, browsers, editors, simulators, and agent sessions one lifecycle model. A worktree owns tab groups and layout, while activation, split, move, pin, close, and recent-focus actions update the selected surface together.
Tab placement resolves the requested group, anchor, active group, or workspace root. A split request creates a new group beside its source. Resource retirement follows ownership rather than visibility, so a hidden live surface can continue work until its last owner closes.
References: src/…/tabs-slice-contract.ts• L27-66 src/…/tabs-slice-contract.ts• L145-198 src/…/TabGroupPanel.tsx• L147-250 src/…/TabGroupPanel.tsx• L382-415
View commands and appearance
View commands provide one action path for menus, keybindings, plug-ins, and host events. The renderer checks the active surface before it changes sidebars, tabs, workspaces, or pages. A focused terminal, editor, browser, or plug-in can keep control when that surface owns the shortcut.
Appearance state follows the same shared model. Theme mode, terminal and editor palettes, fonts, effects, plug-in themes, and background surfaces are applied from settings so the shell and retained panes stay visually aligned. Every renderer window paints its own document, including popout windows, and can fall back to built-in colors while plug-in themes load.
References: src/…/app-command-handlers.ts• L70-127 src/…/use-global-keybindings.ts• L41-89 src/…/use-document-appearance.ts• L35-81 src/…/use-document-appearance.ts• L118-173 src/…/use-app-theme-paint.ts• L66-100 src/…/use-app-theme-paint.ts• L115-130
Popout experiences
Floating workspace
The floating workspace is an in-window work area independent of the selected worktree. It can hold terminal, browser, simulator, and Markdown tabs. Closing it hides the surface without losing its tabs or pane state, so reopening returns to the same context.
Its launcher can be moved and saved around areas that need to remain clear. An unread marker makes hidden activity visible without opening the panel.
References: src/…/AppRootSurfaces.tsx• L146-164 src/…/FloatingTerminalToggleButton.tsx• L62-90 src/…/FloatingTerminalToggleButton.tsx• L102-119 src/…/FloatingTerminalToggleButton.tsx• L204-262 src/…/FloatingTerminalPanel.tsx• L1-10
Agent dashboard surfaces
The Agent Dashboard gives users a cross-worktree view of agent activity. It groups work by attention and outcome, supports search and filters, and lets users acknowledge, reveal, launch, sleep, or inspect the owning worktree. It can appear as a non-modal companion sheet beside the sidebar or as a separate popout window.
The in-window sheet reads the live store directly and leaves the rest of the app interactive. The popout receives a bounded snapshot and sends actions back to the main renderer. The main renderer publishes a fresh snapshot when the popout opens, throttles bursts, and can reuse unchanged workspace and card data. Live status events can patch a matching popout card until the next full snapshot arrives. Its terminal preview is a view of a live PTY, not a second terminal owner.
This diagram shows the ownership boundary between the main renderer, host, and dashboard window.
sequenceDiagram
participant M as Main renderer
participant H as Desktop host
participant P as Dashboard popout
M->>H: Publish bounded dashboard snapshot
H->>P: Relay snapshot and live status
P->>H: Request reveal or acknowledgement
H->>M: Forward mutation
M->>M: Update shared state
M->>H: Publish new snapshot
References: src/…/AgentDashboardDrawer.tsx• L36-85 src/…/AgentDashboardDrawer.tsx• L94-183 src/…/AgentDashboardDrawer.tsx• L216-260 src/…/useDashboardPopoutBridge.ts• L17-33 src/…/useDashboardPopoutBridge.ts• L92-227 src/…/useLiveDashboardSnapshot.ts• L14-99 src/…/build-dashboard-snapshot.ts• L65-75 src/…/build-dashboard-snapshot.ts• L104-120 src/…/dashboard-agent-status-patch.ts• L34-101
Desktop API boundary
Preload capability model
The renderer reaches native services through window.api, the typed capability boundary provided by preload. A capability is a named operation or event stream for a product area. It gives renderer code requests and cleanup functions without exposing direct Electron or Node access.
The contract groups desktop capabilities for workspace resources, agent accounts and sessions, browsers, files, Git, reviews, task providers, automations, runtimes, settings, permissions, paired devices, dashboards, terminal previews, telemetry, and recovery. Results and events become store changes or local surface state. Optional desktop bridges can be absent, so a view uses a capability only when the host exposes it.
The fully qualified contract path is src/…/api-types.ts. The preload entry assembles these domain bridges into window.api, while the renderer chooses the capability that matches the current host and surface.
References: src/…/api-types.ts• L97-202 src/…/index.ts• L113-212 src/…/native-chat-api.ts• L58-77 src/…/dashboard-api.ts• L10-36
Request and event flow
Renderer actions use request methods. Host-originated changes use event subscriptions. A subscription returns a cleanup function, so a closed surface stops receiving updates. One-shot intents use a consume operation when an operating-system or menu event can arrive before the target view mounts. Interactive page prompts use a request, a cancellable renderer dialog, and a response sent back to the host.
This diagram shows the normal direction of a renderer action and the reverse direction of a host event.
sequenceDiagram
participant R as Renderer surface
participant P as Preload API
participant H as Host service
R->>P: Call typed capability
P->>H: Invoke named IPC channel
H-->>P: Return result or publish event
P-->>R: Resolve result or call subscription
R->>R: Update store or local surface
The UI bridge also carries commands for page changes, sidebar changes, tab creation, terminal focus, browser control, editor reveal, and close requests. These events enter the same store-backed view model as local user actions.
References: src/…/ui-command-event-api.ts• L80-134 src/…/ui-command-event-api.ts• L144-217 src/…/ui-command-event-api.ts• L262-312 src/…/native-chat-api.ts• L45-74
Renderer recovery
Renderer recovery protects users from a repeated blank-window failure. Recoverable boundaries let the root, page, workbench, sidebar, or overlay remount without taking down the rest of the shell. If the React tree cannot provide a usable prompt, the desktop host shows a native recovery prompt with reload and quit choices and can offer a repair command when it detects an installation problem.
References: src/…/main.tsx• L65-97 src/…/RecoverableRenderErrorBoundary.tsx• L33-115 src/…/renderer-recovery-prompt.ts• L24-73
Change checklist
When these files or sections are changed, remember to consider these:
- A new view must align the shared view value, page selection, persisted active view, title-bar rules, rail and sidebar behavior, and paired-client behavior.
- A shell or overlay change must preserve stable root sibling order, recovery boundaries, lazy mounting, focus return, notification-card placement, prompt ownership, and host-specific window chrome.
- A worktree visibility change must use the same host, source, lineage, sleep, browser, structured-chat, and agent activity rules in the sidebar and dashboard.
- A tab or terminal-surface change must preserve resource ownership, hidden-surface retention, split layout, recent focus, layout-owner handoff, and close-time retirement.
- An active-workspace service change must preserve its session-readiness gate and keep refresh, file-watch, review, port, agent, and structured-chat updates alive when their display surface unmounts.
- A startup change must preserve the hydration write gate, runtime host discovery, local-first first paint, draft readiness, terminal restoration barrier, layout-frame handoff, and deferred remote refresh.
- A persistence change must preserve per-host routing, duplicate-close protection, terminal-buffer timing, sleeping-agent capture, and app-root close requests.
- A native-chat change must keep transcript projection, outbox state, queued text, goals, tasks, prompts, attachments, usage notices, restart offers, and resume records distinct.
- An editor or review change must preserve file ownership, external-change choices, model lifetime, check detail state, and conflict-review freshness.
- A browser change must preserve exact page and host identity, paint-retention signals, route preparation, prompt cancellation, toolbar behavior, capture scope, and recovery states.
- An activity change must preserve shared projection inputs, thread selection, read state, workspace jumps, portal staging, terminal ownership, and unavailable states.
- An agent picker or update change must keep draft setup, catalog readiness, selected surface, host readiness, update scope, and retry or failure states aligned.
- A popout change must keep snapshots bounded and route every mutation to the main renderer rather than creating a second authority.
- A preload capability change must align its type, exposed bridge, host handler, renderer call site, event cleanup, and one-shot intent behavior.
Important failure modes
| Trigger | Consequence | Guard |
|---|---|---|
| Session writes unlock before hydration and terminal restoration finish | Partial state can replace the last good session | Keep the write gate closed and use degraded recovery on failure |
| A hidden live browser or terminal is unmounted | The page stops painting or the session must rebuild | Separate visibility from ownership and retain live surfaces |
| A stale runtime or paired-host layout frame is accepted | Tabs and panes roll back to an older host state | Fence frames by host identity, generation, freshness, and removal state |
| An active-workspace watcher starts before session readiness or stops with its page | Git, review, file, or tab state becomes stale after a workspace switch | Keep the watcher in the app-level service gate and use the readiness guard |
| A structured send clears before delivery is known | User input disappears or cannot be retried | Keep it in the outbox until the host confirms or reports failure |
| An activity selection swaps before its next terminal is ready | The prior terminal appears under the new agent or the page flashes blank | Stage the next portal and swap only after readiness or an explicit unavailable result |
| An agent catalog is treated as ready before its host or install state is known | A launch choice looks valid but cannot run | Keep catalog, installation, and host readiness visible in the picker |
| A browser route mounts a local profile before remote ownership is ready | The user browses from the wrong machine | Wait for route preparation and host validation |
| A preload listener outlives its surface | A closed view applies events to a new view | Make cleanup part of every subscription contract |
| A root overlay loses its boundary or mounts before its required state is ready | One failed or premature surface can disrupt other global controls | Keep conditional mounting and per-surface recovery boundaries |
| A restart offer is treated as empty during a host startup race | A durable chat resume offer is stranded | Retry failed reads only and keep confirmed empty results final |
| A popout changes its local snapshot directly | The main window and popout diverge | Route mutations to the main renderer and publish the result |
| A dashboard preview loses its PTY | The preview shows a blank or misleading terminal | Use the resolved PTY owner and fail closed when it is absent |
| An agent CLI update is shown for an unsupported host | The user starts an action the host cannot perform | Limit the action to supported local and runtime targets |
| The renderer exhausts in-tree recovery | The window is blank with no usable controls | Use the host-owned native recovery prompt |
Key files
| File | Why to read it |
|---|---|
| src/…/App.tsx | Shows the renderer root, shared providers, background services, startup hooks, shell, root surfaces, global dialogs, and host-specific auxiliary surfaces. |
| src/…/AppWorkspaceShell.tsx | Shows navigation, page selection, workbench placement, title-bar composition, and recovery boundaries. |
| src/…/AppShellLeftColumn.tsx | Shows the stable relationship between the titlebar, app rail, and workspace list. |
| src/…/AppRail.tsx | Shows the compact app navigation model and its keyboard focus behavior. |
| src/…/AppRootSurfaces.tsx | Shows stable root overlay order, conditional mounting, lazy loading, prompt hosting, and modal ownership. |
| src/…/AppBackgroundServices.tsx | Shows services that outlive their consuming surfaces and optional dashboard or paired-device publication. |
| src/…/use-app-startup-hydration.ts | Shows how saved data, runtime hosts, drafts, and live resources become the first usable session. |
| src/…/use-app-session-persistence.ts | Shows normal writes, shutdown checkpoints, and close-request handling. |
| src/…/use-app-chrome-layout.ts | Shows how view state decides title-bar ownership, sidebar visibility, rail visibility, and workbench mounting. |
| src/…/use-document-appearance.ts | Shows how settings drive shell, terminal, editor, plug-in, and background appearance. |
| src/…/index.ts | Shows the shared renderer state model and its product state slices. |
| src/…/tabs-slice-contract.ts | Defines unified tabs, group layout, and resource actions. |
| src/…/TabGroupPanel.tsx | Shows tab composition, split groups, editor ownership, and retained pane behavior. |
| src/…/ActivityPrototypePage.tsx | Shows activity filters, thread selection, terminal portal staging, and workspace jumps. |
| src/…/activity-thread-projection.ts | Shows the shared activity projection used by the activity page and attention surfaces. |
| src/…/NativeChatStructuredSession.tsx | Shows the conversation surface, transcript state, prompts, goals, notices, recovery, and composer placement. |
| src/…/NativeChatResumeToastHost.tsx | Shows restart resume offers, progress reports, failure actions, and settings links. |
| src/…/AgentLaunchPicker.tsx | Shows the shared agent, model, surface, and launch-default selection flow. |
| src/…/EditorContent.tsx | Shows editor modes for files, diffs, previews, checks, and conflicts. |
| src/…/browser-workspace-pane.tsx | Shows local, client-hosted, and streamed browser surface selection. |
| src/…/ArtifactsPage.tsx | Shows account state, artifact listing, selection, deletion, and detail presentation. |
| src/…/AutomationsPageSurface.tsx | Shows automation list, detail, run history, run detail, and recovery navigation. |
| src/…/AgentDashboardDrawer.tsx | Shows the in-window agent dashboard companion surface. |
| src/…/useDashboardPopoutBridge.ts | Shows snapshot publication, popout actions, throttling, and reload recovery. |
| src/…/build-dashboard-snapshot.ts | Shows the bounded cross-worktree dashboard model shared by the drawer and popout. |
| src/…/dashboard-agent-status-patch.ts | Shows how live status updates patch a popout snapshot without changing ownership. |
| src/…/api-types.ts | Defines the typed desktop capability surface and its optional desktop-only bridges. |
| src/…/index.ts | Exposes the capability groups as window.api. |
| src/…/native-chat-api.ts | Defines transcript reads and live native-chat frames. |
| src/…/dashboard-api.ts | Defines dashboard snapshots, actions, and terminal preview events. |
| src/…/ui-command-event-api.ts | Defines host commands, one-shot intents, and UI event streams. |
| src/…/main.tsx | Shows renderer bootstrap and root recovery. |
| src/…/renderer-recovery-prompt.ts | Shows recovery when the renderer cannot display its own UI. |