Introducing a new way to review your PRs.

Read the announcement

stablyai / orca

Orca lets you run a fleet of bots with your own subscription (e.g. Claude Code, Grok, Agy, Codex). Available on desktop, mobile and remote runtime.

View on GitHub

34 documents · Updated Nov 20, 2026

docs / mobile-client

Mobile client

The mobile client is an Expo application that lets an engineer reach Orca hosts from a phone, tablet, foldable device, or supported web build. It pairs the device with a desktop, keeps host and workspace scope through navigation, and provides native or host-delivered surfaces for agent work, bots, terminals, files, reviews, tasks, automations, accounts, and alerts.

Product model

Home catalog

The home screen is the starting point for paired hosts and current work. It combines hosts, workspaces, agent activity, bots, usage, automations, and settings so an engineer can resume work or start new work without first opening a separate tool.

The home tabs are:

  • Feed: paired hosts, workspaces, recent activity, bots, tasks, and resume actions.
  • Bots: bot items, chats, activity, and groups that need attention.
  • Agents: active agent work and items that need attention.
  • Usage: host statistics and provider usage.
  • Automations: scheduled agent work and recent runs.

Home keeps visited tabs mounted so tab changes preserve the current view. It also keeps last-known workspace rows while a host reconnects, but marks connection and action failures instead of presenting stale data as current. A host row can be visible while its credential is temporarily unavailable; that state supports repair or re-pair rather than silently removing the host.

References: mobile/…/MobileHomeScreen.tsx• L49-81 mobile/…/MobileHomeScreen.tsx• L102-117 mobile/…/MobileHomeScreen.tsx• L151-166 mobile/…/home-tabs.ts• L3-5 mobile/…/use-mobile-home-data.ts• L69-109 mobile/…/use-mobile-home-data.ts• L177-224

Expo Router separates app routes from host-scoped routes. Host routes carry the host id, and workspace routes also carry the workspace id and optional execution-host id. This keeps resume actions, bot links, task handoffs, page navigation, and notification taps pointed at the same target.

Route familyUser purpose
/Choose a host, resume work, create a workspace, or pair a desktop
/pair-scan, /pair-confirm, /pairScan, paste, and confirm pairing data
/mobile-onboardingChoose a default session view and remote notification consent
/settings and surface settings routesChange appearance, terminal, chat, browser, voice, and notification preferences
/troubleshoot and /connection-logInspect device, host, network, relay, and page health
/h/[hostId]Open the host-scoped delivered page or its unavailable state
/h/[hostId]/accountsView provider accounts and usage, and change supported accounts
/h/[hostId]/tasks and /automationsOpen provider work and scheduled agent work
/h/[hostId]/session/[worktreeId]Work in chat, terminal, files, browser, and review views
/h/[hostId]/group/[groupId]Open a bot group room
/h/[hostId]/files, /source-control, /review, and /agent-historyInspect workspace files, source control, reviews, and agent history
/h/[hostId]/[...page]Open another supported host-delivered page

Phones use a stack. Wide layouts put the host catalog beside the detail view. Foldable layouts can place the catalog and detail view on separate sides of the fold. A delivered page can take ownership of the wide host area when its route declares that ability; otherwise the native catalog stays visible. The host root validates and encodes its host id before opening the page shell, and uses a named unavailable state when the route is not safe or supported.

Session and group routes normally keep the host list below them so Back returns to that list. A standalone session can replace the host list when it comes from a resume action. A pane or bot-item request updates the current session instead of remounting it, so the existing page keeps its stream and local state.

References: mobile/…/host-stack-navigation.ts• L53-103 mobile/…/host-stack-navigation.ts• L166-220 mobile/…/_layout.tsx• L212-247 mobile/…/_layout.tsx• L39-157 mobile/…/index.tsx• L9-45 mobile/…/[worktreeId].tsx• L18-84 mobile/…/[groupId].tsx• L1-2

Execution hosts

An execution host is the server that owns a workspace. The paired desktop remains the entry point for host access, but a workspace route sends workspace reads and actions to its execution host when one is present.

The execution-host identity travels with native routes, delivered-page routes, tasks, automations, bot groups, and notification targets. If the server cannot be reached through the paired desktop, the app shows an unavailable state instead of sending work to the wrong machine.

References: mobile/…/workspace-route.tsx• L19-84 mobile/…/notification-routing.ts• L32-72 mobile/…/MobileBotGroupChat.tsx• L17-37 mobile/…/MobileAutomationsScreen.tsx• L27-89

Paired-host experience

Pairing flow

Pairing creates a trusted relationship between the device and an Orca desktop. The app accepts a QR code, copied code, or pairing link, validates the offer scope, races usable direct and relay paths, exchanges a device credential, and then saves the host for later use.

The flow has two outcomes:

  • A direct pairing keeps the desktop endpoint as the host connection path.
  • A relay pairing also installs durable relay credentials so the device can recover when direct access is not available.

Runtime-scope links are not mobile pairing offers. The app refuses them instead of creating a phone pairing with the wrong client scope.

Relay pairing keeps a journal until the desktop proves that credential installation committed and the phone has saved the resulting credentials. App startup retries an unfinished journal before another scan can replace it. This prevents a lost reply from creating a second device identity or leaving an installed relay credential without a host row.

After pairing, onboarding asks for the default session view and remote notification consent only when those choices are not already known.

References: mobile/…/mobile-pairing-offer-scope.ts• L3-13 mobile/…/pre-profile-pairing-coordinator.ts• L87-167 mobile/…/pre-profile-pairing-coordinator.ts• L175-299 mobile/…/mobile-relay-pairing-recovery.ts• L71-180

Host lifecycle

The host catalog joins non-secret host metadata with a protected device credential and optional relay routing. A host row can therefore remain useful while the credential store is temporarily unreadable. The app treats removal as a durable lifecycle: it removes the catalog entry first, records credential cleanup intent, and retries native cleanup when needed.

Pairing preserves a host identity when the same desktop is paired again. Authenticated status replies can refresh the desktop name, platform, and machine details without making that bookkeeping a requirement for a live connection. The engineer can also edit the phone display name or endpoint without pairing again.

References: mobile/…/host-profile.ts• L12-70 mobile/…/host-store.ts• L55-103 mobile/…/host-store.ts• L173-318 mobile/…/host-removal-lifecycle.ts• L1-180 mobile/…/mobile-relay-credential-bundle.ts• L1-160

Work surfaces

Session surface

The session surface is the main workspace area. It combines agent chat, terminal panes, files, browser work, source control, review actions, bot chat, and session tabs while keeping one host, workspace, execution-host, and active-pane scope.

The native session can show:

  • Agent transcripts with live progress, tool activity, prompts, permissions, queued messages, background tasks, rewinds, and forks.
  • One or more terminal panes with mobile input controls, selection, links, image input, dictation, quick commands, and text-size choices.
  • Markdown and file readers with drafts, previews, and diff comments.
  • A remote browser view with navigation, touch input, dialogs, zoom, and recent-frame recovery.
  • Source-control and review views for local changes, history, diffs, comments, checks, and pull requests.
  • Bot item and chat entry points that open the relevant bot panel or session tab.

The session keeps local drafts and queued input distinct from host-confirmed transcript or tab state. It also keeps terminal streams and browser streams separate, so replacing one does not replace the other.

Detailed chat and terminal contracts belong in mobile sessions and terminal interaction.

References: mobile/…/MobileSessionSurface.tsx• L22-113 mobile/…/MobileSessionActiveContent.tsx• L41-121 mobile/…/MobileSessionActiveContent.tsx• L155-300 mobile/…/mobile-session-tabs.ts• L30-107 mobile/…/use-mobile-session-controller.ts• L38-145

Bot surfaces

Bot surfaces let an engineer monitor and act on bot work from the home screen, a host page, or a workspace session. They join bot items, chats, activity, automations, access requests, linked files, and group rooms to the host and execution-host model.

The home feed shows a small set of bots that need attention and the Bots tab provides the full list. A bot panel opens on items or a selected item and also exposes chats, files, activity, automations, settings, suggestions, and access requests. A group route opens a shared bot room only when the execution host is connected.

Bot links are resolved against paired hosts before opening. A link may name a bot session, a bot, or an access request. The router can ask the engineer to choose among hosts, redeem an access request on the host that owns it, or show an update or reachability result without opening an unrelated host.

References: mobile/…/MobileHomeBots.tsx• L10-41 mobile/…/MobileHomeScreen.tsx• L151-173 mobile/…/MobileBotPanel.tsx• L1-4 mobile/…/MobileBotPanel.tsx• L58-81 mobile/…/MobileBotGroupChat.tsx• L9-37 mobile/…/BotLinkRouter.tsx• L34-79 mobile/…/BotLinkRouter.tsx• L135-173

Agent chat and terminal interaction

Agent chat is a conversation surface over the selected workspace. It separates live activity, authoritative transcript rows, prompts, permissions, and local pending input so an uncertain send does not become a duplicate turn.

The terminal is a live host stream fitted to the device viewport. The client sends the measured terminal size before it asks for scrollback, resumes output after a path change, and keeps output flow controlled by acknowledgements. A terminal that is covered by chat can keep its input lease without displaying output, then receives a fresh snapshot when it returns.

Mobile controls extend the host terminal with paste, dictation, accessory and held modifier keys, smart keys, quick commands, selection, file links, image input, text scale, and font choice. Wide screens can show terminal panes beside related session content or in a stacked layout.

See mobile sessions and terminal interaction for the detailed interaction model.

References: mobile/…/MobileNativeChatView.tsx• L137-216 mobile/…/MobileNativeChatView.tsx• L223-385 mobile/…/TerminalPaneView.tsx• L56-203 mobile/…/rpc-client-terminal-subscription.ts• L12-33 mobile/…/use-terminal-font-settings.ts• L11-67

Tasks, automations, and accounts

Task, automation, and account surfaces connect work outside a workspace to the same host and execution-host model. They use provider data from the host, expose supported actions, and show a clear offline or unsupported state when the selected target cannot serve the request.

SurfaceMain purpose
TasksBrowse GitHub, GitLab, Jira, and Linear work; inspect details; comment; review checks; change supported fields; and create linked workspaces
AutomationsCreate and edit scheduled agent work, inspect details, and review runs on the paired host or a reachable execution server
AccountsView provider accounts and rate-limit windows, select supported Claude or Codex accounts, and use a supported Codex reset credit

Workspace creation from a task checks repository access, source choice, setup trust, agent choice, and the selected execution scope. If delivery is uncertain, supported creates replay the same operation identity; otherwise the app keeps the result unknown rather than guessing that no work was created.

Account snapshots are live for usage values. Stored account rows may help the page open, but the app does not treat stored usage numbers as current.

References: mobile/…/MobileTasksLegacySurface.tsx• L85-116 mobile/…/worktree-create-retry.ts• L60-153 mobile/…/MobileAutomationsScreen.tsx• L24-137 mobile/…/MobileAccountsScreen.tsx• L66-171 mobile/…/UsageStatusNote.tsx• L1-120 mobile/…/usage-percentage-display-preference.ts• L1-80

Mobile web delivery

Delivered page lifecycle

The mobile web shell is an optional host-delivered page system. A host can serve a page for a route known by the app, while the native route remains the fallback when the host, bundle, route, or device cannot safely support it.

The shell follows this flow:

flowchart LR
    A[Open host route] --> B[Check host status and route grants]
    B --> C{Usable cached page?}
    C -- Yes --> D[Open cached generation]
    C -- No --> E[Read manifest and fetch assets]
    E --> F[Verify and stage bundle]
    F --> G[Activate page generation]
    D --> H[Start private page session]
    G --> H
    H --> I[Exchange scoped host and device requests]
    B --> J{Route unavailable or blocked?}
    J --> K[Use native fallback or named failure state]

The shell checks host reachability, status readability, bundle compatibility, route availability, and grants before it starts a page. It reuses a working generation when an update fails, stages a newer generation behind a running page, and activates it only when the old page no longer reads its files. A failed page gets bounded recovery and a visible state rather than an endless reload.

The host root route reads one host id, encodes it into the page path, and lets the shell decide if the route can run. A host change remounts the page session so the old page cannot keep its grants. An invalid route returns a named unavailable state instead of opening a page with an unsafe target. Session pane and bot-item requests can be delivered into a running page without replacing its bridge.

The shell can warm a spare page on supported native devices so a later route opens faster. The web build uses the same route model but does not use the native device store or native WebView module.

See mobile web delivery for bundle, generation, bridge, and page details.

References: mobile/…/MobileWebShellScreen.tsx• L85-145 mobile/…/MobileWebShellScreen.tsx• L186-239 mobile/…/MobileWebShellScreen.tsx• L247-340 mobile/…/mobile-web-shell-session.ts• L46-197 mobile/…/generation-store.ts• L31-75 mobile/…/index.tsx• L9-45

Page and device boundary

The bridge is a controlled boundary between a downloaded page and the device. Each page session receives only the grants for its route and can reach only the host client, streams, storage keys, navigation actions, and native verbs allowed by that session.

Native verbs cover bounded device actions such as clipboard, media, audio, speech, storage, PDF viewing, image actions, and accessibility announcements. Desktop-bound actions, such as a workspace PDF request, still wait for the current host status. Pages cannot directly reach the device clipboard, Photos, or share sheet, and foreign links pass through the shell’s gesture and scheme policy.

The bridge also carries safe-area, keyboard, fold, language, appearance, terminal key-rail, and app-inactive state into the page. A host or workspace change creates a new grant-bearing session so the old page cannot retain access to the prior target. A page swap waits for the page to have no unsent request, draft, or open modal before it accepts newer bytes.

References: mobile/…/bridge-rpc-client.ts• L55-83 mobile/…/bridge-rpc-client.ts• L113-175 mobile/…/bridge-host.ts• L29-68 mobile/…/bridge-host.ts• L111-163 mobile/…/page-swap-safety.ts• L35-99 mobile/…/generation-store.ts• L104-153

Local state

Device preferences and query state

The app stores device choices separately from host trust. Preferences include appearance, remote push consent, terminal scale and font, link-open mode, sidebar and dock widths, pinned workspaces, split layout, and session-view choices. Host and workspace identity is included where a preference could otherwise leak across targets.

Host query state can restore a first useful screen between launches. Restored data is treated as old until a live host read replaces it, and sensitive live facts such as agent attention and account usage are removed before persistence. Native screens flush their host data when the app leaves the foreground; delivered pages flush their own route store when they become hidden.

The web build has no native device store, so it uses page-scoped storage when that boundary is available. Mirrored keys keep page writes and native reads ordered and make refused page writes visible instead of treating a requested value as proof of persistence.

References: mobile/…/preferences.ts• L9-105 mobile/…/preferences.ts• L169-245 mobile/…/session-view-preferences.ts• L5-59 mobile/…/session-view-preferences.ts• L120-166 mobile/…/host-query-persistence.ts• L14-77 mobile/…/native-query-persistence.ts• L21-69 mobile/…/page-query-persistence.ts• L11-41

Encrypted device store

The native device store keeps host-scoped cache data and durable drafts on disk. It protects values with a device key, hides host and workspace ids from file paths, limits cache growth with eviction, and keeps drafts through a safer temporary-file write path.

The store has two important lifetimes:

  • Cache: purgeable host data used to improve first paint and resume.
  • Draft: user work that must survive a host outage and is not removed when a host is merely revoked.

When a host is removed, its cache and drafts are wiped through the store lifecycle. When a host is revoked, cache writes are fenced and cached screens are wiped while drafts remain available until removal.

References: mobile/…/device-store-contract.ts• L6-39 mobile/…/device-store.ts• L41-85 mobile/…/device-store.ts• L132-303 mobile/…/device-store-files.ts• L13-107 mobile/…/host-logical-client.ts• L32-40

Language and appearance

Appearance and language are resolved before the first useful frame. The root holds the splash screen until the saved choice is applied, and native screens plus delivered pages receive the same theme and locale so switching surfaces does not change the user’s visual or language context.

Native builds use bundled locale catalogs. A page build can also obtain a catalog from the paired desktop and keep a verified copy per host. The latest language request wins if catalog loads finish out of order, and English is the fallback when a catalog cannot load.

References: mobile/…/_layout.tsx• L47-59 mobile/…/_layout.tsx• L186-193 mobile/…/mobile-appearance.ts• L21-65 mobile/…/mobile-i18n.ts• L10-128 mobile/…/page-locale-catalog-source.ts• L25-54 mobile/…/page-locale-catalog-source.ts• L222-265

Notifications and diagnostics

Notification delivery

Notifications use the paired desktop stream while the app is connected and remote push while the app is closed or away from the desktop. The two paths share notification identity and dismissal state so one event does not remain visible twice.

Remote push is offered only after the host proves that it supports the capability. Consent is stored separately from desktop notification behavior, and a missing or unreadable consent value means push is disabled. Token changes, host reconnects, lease renewal, and offline unregisters are reconciled so a stale registration does not continue after the engineer disables or removes a host.

Push payloads identify a host through a fingerprint derived from its public key. The app resolves that fingerprint against paired hosts before it displays an alert or opens a route. A valid tap can open a host, workspace, execution host, pane, or bot group, including from a cold start. Alerts can be suppressed while the engineer is viewing the target workspace.

Android prepares the desktop notification channel during app boot. Foreground presentation, background dismissal, language changes, and notification tap handling are also installed at the root so cold and warm starts follow the same policy.

References: mobile/…/_layout.tsx• L54-65 mobile/…/_layout.tsx• L84-102 mobile/…/_layout.tsx• L104-184 mobile/…/notification-routing.ts• L16-72 mobile/…/notification-reply-schema.ts• L13-55 mobile/…/push-registration.ts• L97-291

Diagnostics and recovery views

Diagnostics help separate a device problem from an internet, host, relay, or delivered-page problem. Troubleshooting checks paired-host data, internet access, each saved host endpoint, and platform state. The connection log records bounded host events and can produce a redacted report with versions, active and pending paths, reconnect attempts, likely cause, and next step.

The diagnostics route keeps an explicit host selection and does not replace a requested or manually selected host with a different one during a refresh. A diagnostic run stops when its screen detaches, so an old run cannot overwrite a newer result.

References: mobile/…/use-troubleshoot-diagnostics.ts• L13-192 mobile/…/connection-diagnostics-screen-data.ts• L18-97 mobile/…/connection-diagnostics-report.ts• L16-71

Transport integration

Shared logical host clients

The app exposes one logical RPC client for each paired host. Screens acquire and release that client through the root provider, so home, host, session, bot, task, automation, account, notification, diagnostic, and page surfaces share one connection instead of opening competing sockets.

The logical client keeps request and subscription identity stable while its physical connection changes. It reports connection state, active and pending paths, reconnect progress, authentication failure, revocation, and connection history to the screens that need to explain recovery.

References: mobile/…/_layout.tsx• L195-256 mobile/…/client-context.tsx• L46-89 mobile/…/client-context.tsx• L131-324 mobile/…/host-logical-client.ts• L14-55 mobile/…/rpc-client-contract.ts• L11-44

Connection paths and recovery

The client can use a local network path, a Tailscale path, or an encrypted relay. Direct access is preferred when it works. Relay recovery can replace a failed direct session, and a direct probe can later return the same logical client to a direct path.

Foreground changes, app resume, network changes, liveness failures, relay lease changes, and credential rotation all feed the recovery supervisor. Recovery uses bounded retries and shared cooldowns so a network change does not create a reconnect storm. Relay migration confirms the replacement session before it closes the old one, and relay director pacing honors a server retry request.

The mobile channel uses paired end-to-end encryption. Native bindings can move encryption and compression work off the JavaScript thread, but the protocol falls back only when the bindings pass their compatibility checks. The client advertises its runtime capabilities so the host can select supported agent, session, stream, and frame behavior.

References: mobile/…/stable-logical-rpc-client.ts• L16-49 mobile/…/stable-logical-rpc-client.ts• L198-259 mobile/…/mobile-endpoint-supervisor.ts• L138-287 mobile/…/mobile-relay-resume-director.ts• L28-109 mobile/…/paired-e2ee-native-codec.ts• L1-135 mobile/…/mobile-runtime-client-capabilities.ts• L31-69

RPC contracts and delivery certainty

RPC operations define the method, accepted reply shape, and point at which the reply is interpreted. This keeps capability probes, required results, object results, stream openers, and deferred mutations from using different error rules by accident.

When a physical session changes, the logical client advances a generation. Late replies and stream frames from the old session cannot update the current screen, and active subscriptions attach to the authenticated replacement. A request that reached the wire before a disconnect remains delivery-unknown because the host may have applied it. Only operations with an explicit replay contract resend the same mutation or operation identity.

Runtime client events tell readers when a stream is ready, lost, or replayed. Terminal and session subscriptions also carry explicit unsubscribe identity so closing one surface does not close another surface for the same workspace.

References: mobile/…/rpc-operation-contract.ts• L5-101 mobile/…/rpc-operation.ts• L80-237 mobile/…/rpc-client-terminal-subscription.ts• L36-112 mobile/…/runtime-client-event-subscription.ts• L4-45 mobile/…/worktree-create-retry.ts• L88-151

Change checklist

When these files or sections are changed, remember to consider these:

  • Keep host, workspace, execution-host, pane, bot, and group identity aligned across native routes, delivered-page routes, resume targets, bot links, task and automation handoffs, and notification taps.
  • Keep native and web route siblings aligned so each build has the same host navigation model and the correct fallback.
  • When pairing or host identity changes, preserve offer scope checks, protected credentials, relay journal recovery, push registration ownership, host-scoped page storage, and cleanup intent.
  • When changing the device store, preserve the distinction between purgeable cache and durable drafts, revocation fencing, host removal wipes, encryption, and size limits.
  • When changing a delivered page, update route grants, host-area ownership, generation activation, bridge verbs, storage scope, navigation policy, page-swap safety, and native fallback states together.
  • When changing notifications, preserve capability probing, consent defaults, host fingerprint resolution, execution-host and group routing, token lease recovery, dismissal reconciliation, and cold-start handling.
  • When changing transport, preserve logical-client generations, subscription replay and unsubscribe identity, delivery-unknown outcomes, direct-versus-relay policy, credential rotation, runtime capability advertisement, and RPC acceptance barriers.
  • When changing bot surfaces, preserve host selection, execution-host reachability, shared seen state, access-request redemption, linked-file scope, and session-tab handoff.
  • When changing language or appearance, keep splash readiness, native locale declarations, page catalog loading, latest-request ordering, fallback behavior, terminal font settings, and delivered-page state aligned.
  • When changing home or host catalog data, preserve last-known rows, explicit error states, tab state, bot attention counts, credential recovery, and execution-host separation.
  • When changing account snapshots, preserve live usage semantics, invalid-snapshot rejection, refresh fallback, percentage display preference, and account selection scope.

Important failure modes

TriggerConsequenceGuard
Pairing data has runtime scope, is invalid, or every path failsThe host is not addedValidate offer scope, bound the attempt, race usable paths, and show the result
Relay pairing loses its reply after installationA second device identity or orphan credential can appearKeep the journal until committed state and local credential publication are confirmed
Host credential storage is unreadableA saved host cannot open a live clientKeep the catalog row and offer retry or re-pair
Workspace execution host is unavailableWork can be sent to the wrong machinePreserve execution-host scope and show an unavailable route
A host refresh fails during reconnectA real failure looks like an empty workspace or bot listKeep last-known rows and show the catalog error
A bot link resolves to no paired host or several hostsThe app can open the wrong bot or silently do nothingResolve against paired-host answers and ask the engineer to choose when needed
A bot group opens while its execution host is offlineThe room cannot show authoritative group stateRequire a connected execution host and show a clear refusal
A live account snapshot is invalid or its stream failsUsage can be stale or shown for the wrong accountReject the snapshot and use an explicit refresh or error state
A delivered route lacks grants or its bundle cannot runThe page cannot open safelyUse the native fallback or a named shell failure state
A page keeps grants after a host or workspace changeThe page can read or act on the prior targetKey the session by route identity and rebuild the bridge
A page swap starts with a draft, open modal, or unanswered requestUser work or an in-flight action can be lostRefuse the safe swap until the page is clear and require a fresh recovery path
A page bypasses navigation or native-verb policyUntrusted page content can escape the device boundaryEnforce route grants, verb schemas, origin checks, and gesture-based external links
A mutation times out after reaching the hostA retry can duplicate workKeep the result unknown and replay only with the same supported operation identity
A push names an unknown host fingerprintAn alert could open an unrelated hostResolve the fingerprint against paired hosts and fail closed
Push consent or token state is staleAlerts can continue after disable or stop after token rolloverPersist consent, reconcile tokens, and retain pending unregister intent
A connection changes while a reply or stream is activeOld data can update the current screenUse logical generations and replay active subscriptions
Android receives a desktop alert before its channel existsThe alert can be droppedCreate and relabel the channel during app boot
A device-store key or file is unavailableCached screens or drafts cannot be read or writtenReport unavailable, retry on foreground, and never treat unreadable data as absent
A language catalog load finishes after a newer choiceThe app can show the wrong languageApply only the latest activation request and fall back to English

Key files

FileWhy to read it
mobile/…/_layout.tsxRoot startup, routes, splash readiness, notification setup, pairing links, and shared providers
mobile/…/index.tsxHost-root page routing, host-id validation, page-session remounts, and unavailable states
mobile/…/[worktreeId].tsxWorkspace route identity, execution-host scope, and in-page pane or bot-item requests
mobile/…/[groupId].tsxNative bot group route
mobile/…/MobileHomeScreen.tsxHome tabs, pairing entry, resume entry, host actions, bot entry, and new-workspace entry
mobile/…/use-mobile-home-data.tsHome reads, live-versus-stored data, host connections, and activity projection
mobile/…/MobileBotPanel.tsxBot items, chats, activity, files, automations, settings, and access actions
mobile/…/MobileBotGroupChat.tsxExecution-host gated group-room entry
mobile/…/BotLinkRouter.tsxSafe bot-link resolution, host choice, access redemption, and failure states
mobile/…/host-store.tsHost metadata, credentials, relay routing, pairing publication, and removal cleanup
mobile/…/pre-profile-pairing-coordinator.tsDirect and relay pairing lifecycle
mobile/…/host-stack-navigation.tsHost, session, group, standalone, and in-page navigation contract
mobile/…/workspace-route.tsxWorkspace execution-host selection and unavailable-server behavior
mobile/…/MobileSessionSurface.tsxMain workspace surface and pane composition
mobile/…/MobileNativeChatView.tsxNative agent chat behavior and input states
mobile/…/TerminalPaneView.tsxDevice terminal pane and interaction boundary
mobile/…/use-terminal-font-settings.tsTerminal text scale and font preference lifecycle
mobile/…/worktree-create-retry.tsWorkspace creation and safe ambiguous-delivery retry
mobile/…/MobileWebShellScreen.tsxDelivered-page lifecycle, bridge setup, native fallback, and page state
mobile/…/mobile-web-shell-session.tsBundle gates, cache reuse, download, activation, and recovery state
mobile/…/bridge-rpc-client.tsPage request, stream, lifecycle, and device boundary on the page side
mobile/…/bridge-host.tsRoute grants, host replies, streams, native verbs, and status gating
mobile/…/page-swap-safety.tsProtection for drafts, modals, and unanswered requests during page updates
mobile/…/generation-store.tsBundle cache, staging, activation, deferred updates, and host eviction
mobile/…/preferences.tsDevice preferences, terminal settings, link behavior, and mirrored writes
mobile/…/session-view-preferences.tsDefault and host/workspace-scoped session view choices
mobile/…/device-store.tsEncrypted cache and draft storage lifecycle
mobile/…/notification-routing.tsSafe notification-to-host, workspace, pane, and group navigation
mobile/…/push-registration.tsConsent, host capability checks, token registration, and unregister recovery
mobile/…/use-troubleshoot-diagnostics.tsUser-facing connectivity checks
mobile/…/host-logical-client.tsShared logical client and direct/relay lifecycle
mobile/…/host-status-gates.tsHost status, capabilities, compatibility, and route gates
mobile/…/rpc-operation.tsRPC acceptance, reply decoding, barriers, and delivery outcomes
mobile/…/rpc-client-terminal-subscription.tsTerminal viewport updates and stream cleanup identity
mobile/…/runtime-client-event-subscription.tsRuntime change-event readiness, loss, and replay handling