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
task(mobile): record 1.0.8 (71) on sale, prepare 1.0.9+72
tony0c729ea3a132
diff --git a/docs/product-measurement.md b/docs/product-measurement.mdindex b8419bd21..9d58a518d 100644--- a/docs/product-measurement.md+++ b/docs/product-measurement.md@@ -20,7 +20,7 @@ automatically proven improvement. Changes still need review, tests and a deliber| Which features get tried and used again? | First measured installations and daily first/repeat feature reach | Locally deduplicated installation-days, not unique accounts. Reads the apps make on their own (history, history paging, Store list, model list; `PRODUCT_USAGE_AUTOMATIC_ACTIONS`) count reliability only. The Store and model lists get reach only from the request an app marks `userAction` when a person opens them (`<action>_user_*`, `PRODUCT_USAGE_USER_OPENED_ACTIONS`); history has none. || Where do app flows break? | Setup, Harness/tmux/clipboard steps, sign-in, workspace/remote connections, computer linking, viewer-pane opening and manual update checking/staging; a setup step whose tool was missing at a check (`setup_desktop_setup_<step>_missing`); the agents a new computer downloads beside setup (`setup_desktop_agent_download_<opencode\|codex\|claude>_started`, `_ok`, `_failed`, with under 1 min, 1–5 min and over 5 min) | Fixed started/ok/failed/cancelled/unknown counts and coarse duration buckets. Opening a viewer pane is not rendering its content; staging an update is not a successful relaunch. A setup step stays open from the first check until its tool is in place, so a tool that was missing and then installed is one ok step and one `_missing` mark; only a setup that ends failed fails its step. Earlier Desktop releases counted every check that found a tool missing as a failed step (on 2026-10-16 the Harness step read 72 failed of 221 while 0 setups failed): compare releases separately. `_missing` is any tool a check found absent or out of date (a Harness CLI older than this Desktop needs, on a computer already in use, counts too), not only new computers. A step left waiting (the review, a Linux Terminal handoff, manual mode, someone who walks away) now ends `unknown` at the 15-minute observation bound instead of `failed`, so expect `setup_*_unknown` to rise, mostly on Linux. `_missing` and the download counts are anonymous setup counts only. A download whose prerequisite (curl, Harness's Node) never arrived counts as started and failed; `ok` means the agent's program is in place, judged per engine. || Where does the phone's onboarding stall? | After sign-in: waiting for the first computer, opening its session, the first message, the notification prompt. A sign-in that went through, by button, counted again under the account's sharing. Waits past a minute split into 1–5 min, 5–15 min, 15 min–1 h and over 1 h for the computer and the first message. Once per step per sign-in: `resumed` (reopened in a run that did not sign in), "Not you? Sign out", the address sent from the share sheet, a joining computer that wants its password or is offline, `joined_after_leaving` (the computer turned up after the app left the wait), `new_account` (a sign-in that created the account). Once per install: `first_open` (signed out `setup_phone_first_open`, signed in `ui_phone_first_open`) | Stage totals per day, not a linked funnel. A wait's `ok` is a computer that turned up while its screen was open: add `joined_after_leaving` for the computers that came while the app was away (16–19 October 2026: 5 `ok` in 49 fresh waits, while 91% of the phone's people had a computer on the same account). `new_account` is an account minutes old at sign-in, its first Harness sign-in anywhere. `first_open` is set once per install by a local flag that is never sent: the step between a store's download and a sign-in. Subtract `resumed` from starts for fresh starts; an unmatched start is a closed app or a step still waiting. A resumed step's duration starts at the reopening. Signed-in sign-in counts are successes only; failures and cancels before an account remain the signed-out counts', but a success is marked `retried` (a failed or cancelled try came first in that app run) or `switched` (another button was tried first). Phone reports carry release and iOS/Android, so every phone count also splits by those two margins (above 20 collector days); debug builds are not kept. A chosen sign-out sends what is queued first (up to 2 s), so "Not you? Sign out" reaches the totals. The first message is the first line sent after the hand-over in any session, or a task typed into New Harness; before 2026-10-20 only the session the hand-over opened counted and leaving it cancelled the step (compare releases separately). Each step of a sign-in that created its account is marked `new_account` when counted and `new_account_ok` when it ends ok, so new people's funnel reads apart. The phone sends what it queued as it leaves the screen, since iOS can end a suspended app with its counts still in RAM. |-| How fast does the phone get back to work? | A launch that came back signed in, to its first computer answering (`app_start`); a dial the person asked for ("Try again", `connect_user`) apart from the app's own (`connect_auto`), beside the unchanged `remote_connect`; a stopped harness resumed from the phone, to its first live turn (`resume_recovery`) | A launch that signs in is the onboarding's and is not counted; one that leaves the screen before a computer answers is `unknown`, one whose computers never answer stays started. What a launch waited on is counted beside it, once each, until a computer answers or the app leaves the screen (`ui_phone_app_start_<why>`): `no_computer` and `list_failed` (the account's list had none, or could not be read), `offline` (it said every computer was offline), `locked` (a computer wanted the phone's password), `connect_failed` (a dial to a computer said to be online failed) and `waited_1m` (a minute on screen); a launch can name several. An asked-for dial fails at 12 s, as Desktop Connect does. A phone dial is `failed` only when the phone knows why (locked or offline), `unknown` otherwise; the reasons (`connect_error_*`) are Desktop health counters. The phone's `remote_connect` is one computer's socket dialling, from connecting or reconnecting until it connects (`ok`) or drops (`failed`). `cancelled` is a dial still going when the app went to the background (the pause, not the app switcher or a system sheet): a suspended app never hears the socket's answer, so the dial ends there rather than staying without an outcome, and a dial after the app is back is a new count. From 1.0.8 build 72 a dial still in progress when the app goes to the background ends `cancelled`; earlier builds left it without an outcome (79 of the 252 on 2026-10-20): compare releases separately. `connect_user` and `connect_auto` are not ended this way. |+| How fast does the phone get back to work? | A launch that came back signed in, to its first computer answering (`app_start`); a dial the person asked for ("Try again", `connect_user`) apart from the app's own (`connect_auto`), beside the unchanged `remote_connect`; a stopped harness resumed from the phone, to its first live turn (`resume_recovery`) | A launch that signs in is the onboarding's and is not counted; one that leaves the screen before a computer answers is `unknown`, one whose computers never answer stays started. What a launch waited on is counted beside it, once each, until a computer answers or the app leaves the screen (`ui_phone_app_start_<why>`): `no_computer` and `list_failed` (the account's list had none, or could not be read), `offline` (it said every computer was offline), `locked` (a computer wanted the phone's password), `connect_failed` (a dial to a computer said to be online failed) and `waited_1m` (a minute on screen); a launch can name several. An asked-for dial fails at 12 s, as Desktop Connect does. A phone dial is `failed` only when the phone knows why (locked or offline), `unknown` otherwise; the reasons (`connect_error_*`) are Desktop health counters. The phone's `remote_connect` is one computer's socket dialling, from connecting or reconnecting until it connects (`ok`) or drops (`failed`). `cancelled` is a dial still going when the app went to the background (the pause, not the app switcher or a system sheet): a suspended app never hears the socket's answer, so the dial ends there rather than staying without an outcome, and a dial after the app is back is a new count. From build 72, the release after 1.0.8 (71), a dial still in progress when the app goes to the background ends `cancelled`; earlier builds, 1.0.8 (71) included, left it without an outcome (79 of the 252 on 2026-10-20): compare releases separately. `connect_user` and `connect_auto` are not ended this way. || Are the phone's side pages used? | Find and Computers opens, by a sideways swipe on the terminal or by a button (Computers' row in Settings, its link on a long wait at home) | Which page and which way, nothing more. Find's key and screen-reader actions are not counted; a swipe that lets Find go back opened nothing. || Does Desktop's Add Phone card get used, and where else is Add Phone opened? | The card's flow (`ui_desktop_phone_offer_*`): started once it is on screen, `ok` by its Add Phone, `cancelled` by its ×, `unknown` when it went another way (Add Phone opened from elsewhere, a sign-out); every Add Phone opening by its way in (`ui_desktop_add_phone_<offer\|titlebar\|menu\|account\|machines\|command>`) | The card is offered once per computer, so its starts are computers, not people, and it has no 15-minute bound: started minus outcomes is an app closed with the card still up. An opening is the dialog shown, not a phone paired. `menu` includes a key bound to Harness ▸ Add Phone… on macOS; `command` is `> add phone` or a key bound to it elsewhere. A computer that opened signed in was marked offered without ever showing the card; from 2026-10-20 it shows the card once after one of its own harnesses finishes a turn, if the account has no phone or browser, counted apart as `ui_desktop_phone_offer_after_work_*` (vocabulary 4). The same card also shows to a person back after 5 minutes or more away to one of their harnesses that waited on them or finished meanwhile, counted as `ui_desktop_phone_offer_away_waited_*` / `ui_desktop_phone_offer_away_finished_*` (vocabulary 4): at most 3 cards a computer, every kind together, and none once a card's × or Add Phone was used there ([design](design/2026-10-20-desktop-phone-conversion.md)). The browser counts none. Vocabulary 3: counted from the start, but sent only once the local CLI has answered that it forwards them, so a Desktop on an older CLI sends none. || Is measurement losing coverage? | Updated collector installation-days, pruned queues, full observation maps, unmatched app starts | Loss signals warrant caution. No signal does not prove complete collection. |diff --git a/mobile/RELEASE.md b/mobile/RELEASE.mdindex 3568c9a27..9764a0635 100644--- a/mobile/RELEASE.md+++ b/mobile/RELEASE.md@@ -139,10 +139,10 @@ may lack symbolicated stacks until the matching symbols are supplied.| `1.0.6 (68)` | 2026-10-16 | TestFlight. Phone tracking: app_start, page opens, phone requests, connect (user/auto) and resume recovery counted; account sign-in sends `app=harness-mobile`; setup sharing on by default. ASC refused it as `1.0.5 (68)`: 1.0.5 had been approved, so it went up as 1.0.6. Built from `feat/mobile-ios-android` at `92152439` || `1.0.7 (69)` | 2026-10-19 | TestFlight. Desktop's harness actions on the phone: clone, fork, change agent, delete with its conversation, stop once its task is done; the New form attaches files, starts a Terminal and says what a held creation waits on; find in terminal; any file sent from the key bar; native-style key caps; hardware-keyboard paste; media previews in the app; remote panes recover after their stream dies; Settings ▸ About links the privacy policy. Went up as 1.0.7 straight away, since 1.0.6 had been submitted. Built from `feat/mobile-ios-android` at `1d2466de` || `1.0.7 (70)` | 2026-10-19 | TestFlight, then submitted for App Store review as 1.0.7. The first set-up step reads "Download and install Harness"; terminal menu rows lose their trailing …. Built from `feat/mobile-ios-android` at `1d4ca45c` |-| `1.0.8 (71)` | 2026-10-20 | TestFlight. A + after Find's tab chips opens a new harness in a tab of its own; a held New Harness stops asking once Cancel is pressed, and a launch back to work says what it waited on; a locked Harness OS computer set up on its hotspot in one stay; a spoken sign-in code for devices with no screen; parked machines rechecked less often and not in the background; counts flushed on background, first open, new accounts and testers measured. 1.0.7 had been approved, so it went up as 1.0.8. Built (by another session) from `feat/mobile-ios-android` at `7849fd00` |+| `1.0.8 (71)` | 2026-10-20 | TestFlight. A + after Find's tab chips opens a new harness in a tab of its own; a held New Harness stops asking once Cancel is pressed, and a launch back to work says what it waited on; a locked Harness OS computer set up on its hotspot in one stay; a spoken sign-in code for devices with no screen; parked machines rechecked less often and not in the background; counts flushed on background, first open, new accounts and testers measured. 1.0.7 had been approved, so it went up as 1.0.8. Built (by another session) from `feat/mobile-ios-android` at `7849fd00`. Approved and on sale on the App Store: released 2026-10-20 22:09 UTC (App Store Connect: 1.0.8 `READY_FOR_SALE`, build 71) |-`pubspec.yaml` is now at `1.0.8+72`, the next build number. Build 71 (1.0.8) is the last upload, to both-TestFlight and Play (54 went up outside this record, 53 went to Play only); do not upload any of them again. 1.0.1 to 1.0.7 are approved, so new builds go up as 1.0.8 until it is approved too. Check App Store Connect before uploading if another release has happened meanwhile.+`pubspec.yaml` is now at `1.0.9+72`, the next build number. Build 71 (1.0.8) is the last upload, to both+TestFlight and Play (54 went up outside this record, 53 went to Play only); do not upload any of them again. 1.0.1 to 1.0.8 are approved, so new builds go up as 1.0.9 until it is approved too. Check App Store Connect before uploading if another release has happened meanwhile.### Why the app is iPhone-only@@ -368,4 +368,4 @@ account (Autonomous Inc.) is exempt — check which kind the account is before p| `67` (1.0.5) | 2026-10-15 | Built, same code as iOS 1.0.5 (67), with the pubspec briefly set back to `+67`; uploaded by hand, the track it went to is not recorded || `68` (1.0.6) | 2026-10-16 | Built, same code as iOS 1.0.6 (68); to be uploaded by hand || `70` (1.0.7) | 2026-10-19 | Production, sent for review. Same code as iOS 1.0.7 (70): desktop's harness actions (clone, fork, change agent, delete), files in the New form and from the key bar, find in terminal, hardware-keyboard paste, panes that recover after their stream dies |-| `71` (1.0.8) | 2026-10-20 | Built by another session, same code as iOS 1.0.8 (71); uploaded by hand, the track it went to is not recorded |+| `71` (1.0.8) | 2026-10-20 | Built by another session, same code as iOS 1.0.8 (71); uploaded by hand to Production (reported by the release owner on 2026-10-21) |diff --git a/mobile/pubspec.yaml b/mobile/pubspec.yamlindex 4364e5df0..bf0d15f99 100644--- a/mobile/pubspec.yaml+++ b/mobile/pubspec.yaml@@ -2,7 +2,7 @@ name: harness_mobiledescription: "Harness viewer for iOS and Android."publish_to: 'none'-version: 1.0.8+72+version: 1.0.9+72environment:sdk: ^3.13.0