The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.
TypeScript 3d-modelingagent-frameworkagent-harnessai-agentscadclaude-codecodexcoding-agentsdeveloper-toolsesp32game-developmentmcp-servermulti-agentopen-hardwareopencodeopenharnesspcbroboticsterminaltmux
docs(mobile): say the desktop's half of the notifier is cut, not skipped
deea9fc8b2e329a
diff --git a/mobile/README.md b/mobile/README.mdindex e2bbf8c11..8dfab72d7 100644--- a/mobile/README.md+++ b/mobile/README.md@@ -74,9 +74,10 @@ all.No harness CLI runs beside this app and no agent is ever hosted here. It holds its own SSO session andterminates the E2EE to each machine itself (`lib/viewer/`, `lib/e2ee/`) — where the desktop hands bothto the CLI on its own computer. `kViewerMode` (`lib/core/viewer_mode.dart`) is true on iOS and Android-unconditionally, and that one flag is what gates the paths a phone cannot take: first-run provisioning-and the self-updater are both skipped in `AppNotifier.bootstrap`, because an app the store updates-installs nothing.+unconditionally, so `AppNotifier` always has its `ViewerServices`, and the desktop's side of every+branch on that is gone from this package rather than skipped: first-run provisioning, the self-updater+(an app the store updates installs nothing), finding and supervising a local harness CLI, signing in+through it or a browser, and the grid's presets, splits and keyboard rail.## Keeping in step with `../desktop`@@ -105,3 +106,9 @@ The files expected to differ, and why:neither have the desktop screens a phone can never reach: the sign-in and boot screens (the phonehas `PhoneWelcome` and `PhoneBoot`), first-run provisioning, the update notice, the firmwareflasher, the layout palette and the shortcuts sheet.++Nor has the code only those screens and a local CLI reached: the provisioner, the updater, local CLI+discovery and its runner, the CLI and browser sign-in, pane presets and arrangements. So+`state/app_state.dart`, `state/swarm.dart`, `state/terminal_pane.dart`, `state/pane_layout_store.dart`+and `auth/` differ from the desktop's by that cut as well — a fix carried across from there lands in+what is left.diff --git a/mobile/lib/viewer/viewer_services.dart b/mobile/lib/viewer/viewer_services.dartindex 48c58f9d7..dfcc4d362 100644--- a/mobile/lib/viewer/viewer_services.dart+++ b/mobile/lib/viewer/viewer_services.dart@@ -19,8 +19,8 @@ TerminalTransportPluginFactory? harnessTransportPlugins;/// Everything a viewer build uses in place of the harness CLI, built once and handed to/// `AppNotifier`: the SSO session, signing in, the machines this device has linked and the E2EE-/// sessions to them. A desktop build has none — and where it is null, nothing in the app behaves-/// any differently than it did before viewers existed.+/// sessions to them. This app always has one — the desktop's CLI-backed half of `AppNotifier` is+/// not in this package.class ViewerServices {const ViewerServices._({required this.keys,