Skip to content

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.

43.3 KB
Raw Blame

Releasing the mobile app

The App Store record is Autonomous Harness (ai.autonomous.harness.ios, team 54DJVWMJCC — Autonomous Inc.). Everything up to Android is the iOS side; the desktop app ships from desktop/RELEASE.md on its own tags and shares nothing with this.

The two numbers that decide whether an upload is visible at all

App Store Connect keys a build on the pair (CFBundleShortVersionString, CFBundleVersion) — in pubspec.yaml that is version: 1.0.0+2, so 1.0.0 and 2.

  • Bump the +N before every upload. A pair ASC has already seen is refused, and the refusal arrives by email — the ASC UI shows nothing at all, which is exactly what "I uploaded it and nothing happened" looks like.
  • The short version must match the ASC version record. A build uploaded as 1.0.0 never appears under a version record called 1.0: the Build section stays empty and the version cannot be submitted. Rename one so the two strings are identical.

Upload

One command. Credentials are already on the release Mac, so there is nothing to export:

bash mobile/scripts/release-ios.sh                 # build -> validate -> upload
bash mobile/scripts/release-ios.sh --validate-only # rehearse, upload nothing
bash mobile/scripts/release-ios.sh --skip-build    # upload what the last build left in build/ios

The build is flutter build ios --config-only followed by xcodebuild archive and -exportArchive, not flutter build ipa: Flutter cannot hand xcodebuild an API key, so on a Mac with no signing certificate and no Xcode account it failed at signing whatever key was configured.

The archive is unsigned; the export signs the app and its frameworks with the team's Apple Distribution certificate. Signing the archive would need an Apple Development certificate on the Mac, and the shared release account ([email protected]) has used up its quota of those — Xcode answers "Choose a certificate to revoke", and revoking one breaks whichever Mac holds it. Runner has no entitlements file, so the export's own entitlements are all the app needs.

Where the credentials live, and why not here

~/.appstoreconnect/harness-release.env          ASC_KEY_ID + ASC_ISSUER_ID   (chmod 600)
~/.appstoreconnect/private_keys/AuthKey_<ASC_KEY_ID>.p8   the private key    (chmod 600)

The script sources that .env whenever the environment does not already carry the values, so CI can still pass them in. They are deliberately not written into this file. This repo is public, and a Key ID plus an Issuer ID are precisely the two halves a leaked .p8 would need to become a working App Store Connect session — the repo's own .gitignore already refuses *.p8 and .env*, and putting the other halves in Markdown would walk straight around that.

Setting up a second machine: create a Team Key at App Store Connect ▸ Users and Access ▸ Integrations ▸ App Store Connect API (role Admin), drop the one-time .p8 download into ~/.appstoreconnect/private_keys/, and write the two ids into the .env above. That is the whole setup: the script hands the same key to the export, which signs with the team's cloud-managed distribution certificate — nothing to sign into Xcode, nothing to import into the keychain. An App Manager key uploads but cannot sign that way. An Apple ID plus an app-specific password (ASC_USERNAME / ASC_APP_PASSWORD) uploads too, but then signing needs the account in Xcode (below).

The script validates before uploading, which is what catches a duplicate build number or a missing icon size in thirty seconds instead of in an email twenty minutes later.

Upload with an existing Xcode account

With neither credential set, the script signs and uploads with the Apple account signed into Xcode ▸ Settings ▸ Accounts (a member of the Autonomous Inc. team): it archives as above, then runs xcodebuild -exportArchive -allowProvisioningUpdates with method = app-store-connect, destination = upload, signingStyle = automatic, teamID = 54DJVWMJCC and manageAppVersionAndBuildNumber = false on mobile/build/ios/archive/Runner.xcarchive. Nothing is validated first — altool cannot borrow Xcode's session — so --validate-only refuses this path, and a duplicate build number shows up as the upload failing.

Build 49 used this path, by hand. Apple accepted the upload and started processing it. Xcode reported a non-blocking missing dSYM for the vendored WebRTC framework; native crashes inside that framework may lack symbolicated stacks until the matching symbols are supplied.

Already uploaded

Build When Where it went
1.0.0 (2) 2026-09-16 TestFlight. Universal (iPhone + iPad) — superseded
1.0.0 (3) 2026-09-16 TestFlight. iPhone only
1.0.0 (4) 2026-09-16 TestFlight. Adds agent/machine search (feat/mobile-search)
1.0.0 (5) 2026-09-16 TestFlight. Agent creation flow; Machines tab pairs/unpairs
1.0.0 (6) 2026-09-16 TestFlight. Custom voice input on a terminal tap — misheard Vietnamese, removed for the keyboard's own dictation
1.0.0 (7) 2026-09-17 TestFlight. Voice input back, transcribed by the backend (/api/voice/stt); opens on the last agent's terminal
1.0.0 (8) 2026-09-17 TestFlight. Search grouped by folder, most recent first, one-bar field; keyboard only from a tap on the prompt; hold-to-talk mic; slimmer terminal chrome
1.0.0 (9) 2026-09-17 TestFlight. Terminal chrome rebuilt around a search bar, header folds away on scroll, ⋯ sheet grouped into Agent / Machines / App
1.0.0 (10) 2026-09-17 TestFlight. Smoother swipes and scrolling: parked and keyboard-sliding terminals keep painting; the header folds over the terminal instead of resizing it
1.0.0 (11) 2026-09-17 TestFlight. Agents either side of the one on screen open in advance, so a swipe lands on output instead of "Attaching…"
1.0.0 (12) 2026-09-18 TestFlight. Named OpenHarness on the home screen and in the app; Backspace on the phone erases text typed on the desktop; Machines moved into the ⋯ sheet; hold-to-talk hardened
1.0.0 (13) 2026-09-18 TestFlight. Search reads what agents said (the desktop's content index), recent first; Vietnamese Telex in the search field; terminal search has no Cancel, and the terminal holds still as it closes
1.0.0 (14) 2026-09-18 TestFlight. Voice sends on the second tap again — as a composer turn, not keystrokes Codex read as a paste and left unsent; the terminal scrolls again after New Agent → back
1.0.0 (15) 2026-09-18 TestFlight. The floating mic, Search and + are always there, on a see-through background
1.0.0 (17) 2026-09-18 TestFlight. The terminal holds still as the keyboard opens. (16 went to Play only)
1.0.0 (18) 2026-09-18 TestFlight. Tab, clear and / on the terminal's key bar; account-wide agents list in the terminal sheet; the phone sheet no longer cuts off its last rows
1.0.0 (19) 2026-09-18 TestFlight. The floating mic, Search and + sit on frosted glass, so they stand out from the output under them
1.0.0 (20) 2026-09-21 TestFlight. The phone holds only the agent on screen: the two beside it are no longer opened in advance, and the one swiped away from is closed — each hands its terminal back to the desktop. Voice keeps the audio at both ends of a take
1.0.0 (21) 2026-09-21 TestFlight. The account's tabs reach the phone: a swipe stays inside the tab you are in, the tabs themselves sit behind a mark beside ⋯, and an agent started here joins that tab
1.0.0 (22) 2026-09-21 TestFlight. Named Harness on the home screen and in the app, with a new icon; the terminal runs to the bottom edge of the screen; only an explicit Take control press claims a terminal from the desktop
1.0.0 (23) 2026-09-21 TestFlight. The tabs mark unrolls the account's tabs as a rail of names under the header — the tab you are in wears a bar under its name — instead of opening a sheet; picking one switches and puts the rail away
1.0.0 (24) 2026-09-21 TestFlight. The tabs mark brings a panel up from the bottom: the account's tabs as a row of names, and the agents of the one picked as cards beside each other. A name changes the cards alone — another tab can be read into without leaving the terminal you are in — and a card is what opens an agent
1.0.0 (25) 2026-09-22 TestFlight. Opening an agent takes its terminal again: no read-only stream and no "Take control" band in front of an agent a desktop has open, including the one the app opens on. The band is left for the case it is about — a terminal taken back off this phone
1.0.0 (26) 2026-09-22 TestFlight. The tabs panel lists a tab's agents DOWN the page, as the rows the Agents tab draws, instead of as cards read sideways through a letterbox
1.0.0 (27) 2026-09-22 TestFlight. The tabs panel keeps one height — half the screen — whatever the tab holds, so reading a tab of one agent after a tab of six no longer moves the names along its top
1.0.0 (28) 2026-09-22 TestFlight. Search rebuilt on the desktop's own box: > commands, # projects, @ machines and ? help, and the desktop's ranking behind them, so a query that finds an agent on the laptop finds the same agent here. A result draws its identity as marks — engine, machine, folder, branch — instead of one run of text, and drops the square glyph and the age the desktop never had. Stopped harnesses are listed again, with Stopped on the row and a tap that brings one back; the field sits on the keyboard rather than above a strip of terminal
1.0.0 (29) 2026-09-22 TestFlight. The new logo reaches the phone — build 28 shipped the crop it superseded. ⋯ beside the tabs grid stands up as ⋮, and the two marks move apart far enough to hold a whole touch target each: at the old spacing their 44pt reaches overlapped by 6pt and the row hit-tests backwards, so ⋯ answered for the right-hand sixth of the tabs mark and the tabs mark did not
1.0.0 (33) 2026-09-23 TestFlight. Opens on the agent it was left on, even while the machine is still verifying terminals; a Stopped row resumes its saved conversation (agent_resume, sealed as E2EE) instead of failing, and stopped work with no conversation reads Resume unavailable; other rows no longer read No terminal during a resume; the app wears Logo Harness_4
1.0.0 (34) 2026-09-23 TestFlight. The search sheet opens on the desktop Harness Monitor's order (most recently active first) and names agents as the desktop does (Untitled Pane for a CLI-made name); rows show age, trouble, machine · folder · branch, and tokens / edits / PRs; New Harness asks the Git questions a window asks
1.0.0 (35) 2026-09-23 TestFlight. New Harness touch-ups (bubu/mobile-new-harness-touch); the confirm dialog sits on the app's dialog veil
1.0.0 (36) 2026-09-23 TestFlight. The mic becomes a morphing capsule: a live waveform and take timer while listening, and its own face for busy, sending, sent and retry; notices wrap to whole sentences and clear themselves
1.0.0 (37) 2026-09-24 TestFlight. When the agent left on has been paused, the app opens the most recently active one — the desktop monitor's order — instead of the oldest; the banner over a terminal another app drives names that machine ("MacBookPro2021.local is using this terminal") when its CLI says who holds it
1.0.0 (38) 2026-09-24 TestFlight. Tabs only: the "Other" group is gone, and a launch that cannot reopen the last agent opens the tab the phone was last in, on its first agent; search results follow the desktop's rules (every engine its machine can resume reads Paused and resumes, not "Resume unavailable"), and the terminal header reads like the desktop's pane header — the session's title, the repository rather than a worktree's folder, and no placeholder branch
1.0.0 (39) 2026-09-24 TestFlight. Notices, as the dial gives them: an agent that finishes a turn or asks a question while you are elsewhere chimes, wears an unread mark, and — with the app in the background — posts a system notification (local, so only while iOS keeps the app alive); opening the agent takes its notice down. Codex's queued questions get an Answer band, with Enter on the key bar and hints for keys a phone lacks. New Harness asks what the desktop's launcher asks, Approvals included. The terminal header names the machine. A launch whose desk answers after its machines no longer sits on "Opening your tabs…" until the next desk poll
1.0.0 (40) 2026-09-24 TestFlight. Each desk tab pill wears the unread dot of its agents — amber when one is waiting on you, blue when one finished — so the tab to open is visible before opening it; opening an agent now takes its mark (and its notice) down whichever way it was opened, including an agent with no terminal attached yet, which kept its dot beside the ✓ in 39
1.0.0 (42) 2026-09-24 TestFlight. Sign-in stays in the app: the email, then the 4-digit code sent to it (the Autonomous account API, as the Autonomous companion app signs in) — no browser and no loopback callback, which is what Play's reviewer could not get past. The New tab sheet groups agents by machine; the key bar carries its own modifiers and answers the thumb; Search stays reachable, and reaches the bottom of the screen, with the keyboard up. (41 went to Play only)
1.0.0 (43) 2026-09-25 TestFlight. Relay frames to a machine are sealed under the connection's E2EE session whenever the machine asks for it (strictDown, security issues OH-1/OH-10, #344); key hints move into the key bar; the keyboard comes back with the app after switching away; an opt-in setting holds the connection while the app is off screen
1.0.0 (45) 2026-09-25 TestFlight. The unread mark goes red and moves to the end of its row; the search sheet opens at full height; the opt-in "hold the connection while off screen" setting from 43 is taken back out (its foreground service needed a permission-and-notification walkthrough that cost more than the reconnect it saved). 44 was bumped but not recorded, so it is skipped
1.0.0 (46) 2026-09-25 TestFlight. The search sheet lifts to full screen while a search is typed; a machine that locks out remote-password attempts says so (OH-5, #353); the browser setup links are gone (OH-2, #348)
1.0.0 (47) 2026-09-25 TestFlight. The tabs/search sheet closes the easy way: Close beside the field, a pull of 120pt instead of half the screen, and a pull from anywhere on a list already at its top. The terminal keeps a snapshot's colours as tmux carried them (a wrapped dim line no longer turns bright after a resize or reconnect) — the fix is in the CLI, so it shows once the machine runs it; a truncated 38/48 colour no longer fails the renderer, and palette slot 15 is bright white
1.0.0 (48) 2026-09-26 TestFlight. Paste in the terminal's ⋯ sheet: the clipboard's text as one paste, or, with no text, its image as an attachment (iOS and Android, #321 by jaylfc). The pager no longer counts an agent it is about to close against its cap of open streams, so the page ahead attaches after a swipe
1.0.0 (49) 2026-09-28 TestFlight upload accepted; processing started. Phone polish and cleanup, full recent-first Agent picker, Project/Find search autofocus, collapsed Options with separate Branch/Worktree controls and Model choices, and trusted-device group sync from main. 1,643 offline tests pass; analyzer clean outside existing third-party infos.
1.0.0 (50) 2026-09-30 TestFlight. Light mode, with Dark and Light terminal schemes (#248); an agent's question is answered by tapping its lines; Find gets a tab filter, recaps for the rows on screen, and machine status drawn like harness rows; a new project and its agent are named after the first task (#94). Terminals open over the relay without waiting for p2p, picking an agent redials a machine that had backed off, and the home agent stays while its machine is briefly offline. Camera access that is off links to Settings; analytics are gone. Built from feat/mobile-ios-android
1.0.1 (51) 2026-10-01 TestFlight. First build on the 1.0.1 train — 1.0.0 was approved and its train closed, so ASC refused 1.0.0 (51). Faster launch to the first session; tabs named as on the desktop; Find recaps fold behind a chevron; device key log (#518). First upload from an unsigned archive signed on export (release-ios.sh, Xcode account). Built from feat/mobile-ios-android
1.0.1 (52) 2026-10-01 TestFlight. The launch terminal opens before the agent list; the desktop app, web and CLI sign in by scanning a QR with the phone (#519). Built from feat/mobile-ios-android after merging main
1.0.1 (55) 2026-10-02 TestFlight. Sign in with Google or Apple (an in-app SFSafariViewController over the loopback, so no Sign in with Apple entitlement); faster launch for large accounts and a full skeleton while it loads; back button on the Computers and device pages; device key codes to compare. ASC refused 54 as already uploaded — someone uploaded a 54 that is not recorded here. Built from feat/mobile-ios-android at f95db4a2
1.0.1 (56) 2026-10-05 TestFlight. Copy and paste in the terminal (the key strip's paste asks iOS hasImages, which never brings up the paste prompt); computers and profiles can be renamed, removed and retried; Devices DSH frames sealed as the CLI requires. Built from feat/mobile-ios-android at 28e95521
1.0.1 (57) 2026-10-06 TestFlight. Typing in the terminal no longer lags or drops keys: keys echo locally and go out before the IME resets. Remote scroll is smoother, with a native-like fling and a scroll mirror that follows the finger; the stray cursor is hidden; p2p holds when late relay frames arrive. Onboarding explains its sign-in steps and sign-outs, and scanning a computer's sign-in QR signs the phone in first. Uploaded with the Xcode account from the second Mac; Xcode again reported the non-blocking missing WebRTC dSYM. Built from feat/mobile-ios-android at b896acd8
1.0.1 (58) 2026-10-06 TestFlight. Remote scroll for Claude Code is faster and steadier: page keys and paced wheels fetch rows, each agent keeps its rows, and rows above are prefetched while idle. The key strip's hide-keyboard key is larger. Onboarding says where Add Phone is and which account to use, offers Scan again after a failed pairing, and shortens the scan page's sign-in hint. Uploaded with the Xcode account (release-ios.sh); Xcode again reported the non-blocking missing WebRTC dSYM. Built from feat/mobile-ios-android at 8b174045 after merging main
1.0.1 (59) 2026-10-07 TestFlight. Onboarding gets exits and shorter sign-in waits (fix/mobile-onboarding-exits), on top of 58. Built from feat/mobile-ios-android at 421c54d3
1.0.1 (60) 2026-10-07 TestFlight. Onboarding hardened: one pairing at a time, Scan again and a way out of slow waits, sign-out clears the last account's computers; computer set-up in three steps; iOS local network usage description. Uploaded with the Xcode account (release-ios.sh); Xcode again reported the non-blocking missing WebRTC dSYM. Built from feat/mobile-ios-android at 1d58a94e
1.0.2 (61) 2026-10-08 TestFlight. Shows when a computer is asleep instead of loading, polls faster while all are asleep and adds a refresh button; reopens the terminal before the agent list on reconnect; the key strip leads with a question's key hints, Codex glyph hints (⇧←) included. ASC refused it as 1.0.1 (61): 1.0.1 had been approved, which closes its train, so it went up as 1.0.2. Built from feat/mobile-ios-android at 99e17f3d
1.0.2 (62) 2026-10-09 TestFlight. One-button Connect your computer onboarding (feat/connect-your-computer); Google sign-in on iOS reuses Safari's signed-in accounts; swipe left opens Computers and New Harness moves into Find, which opens with the keyboard down. Built from feat/mobile-ios-android at bf8c4b4c
1.0.3 (63) 2026-10-12 TestFlight. Connect your computer relaid on one left edge, pinned to Computers, with the same set-up steps everywhere; Get it shows the download address to type; New Harness asks which computer, as on desktop. ASC refused it as 1.0.2 (63): 1.0.2 had been approved, so it went up as 1.0.3. Built in a separate worktree (autonomous-harness-release) from feat/mobile-ios-android at d1d696fc
1.0.3 (64) 2026-10-13 TestFlight. The new phone onboarding (feat/mobile-phone-onboarding): a sign-in welcome with the QR sign-in back and "Use " under the sign-in step, the "On your computer, go to" screen with its set-up steps and sign-out under the account, the "X is ready." moment. Also Settings ▸ Connectors, a new device confirmed once on any trusted device (#1196), and Swarm/Jev code removed. Built from feat/mobile-ios-android at 38e8e8ba
1.0.3 (65) 2026-10-13 TestFlight. A harness's sign-in page (Claude Code's /login) opens on the phone and the sign-in goes back to it; the welcome's scan button reads "Scan QR from computer"; Computers shows a refresh button and Settings sits only at home. Built from feat/mobile-ios-android at 3dcd4a6f
1.0.4 (66) 2026-10-14 TestFlight. A simpler welcome (Continue with Google or Apple, then "Continue with email · QR code" as words), a welcome message and pictures; download and sign-in steps under the QR camera; a dropped P2P channel redialled within seconds; a dismissed keyboard stays down; one word per machine state; Privacy settings tidied. ASC refused it as 1.0.3 (66): 1.0.3 had been approved, so it went up as 1.0.4. Built from feat/mobile-ios-android at 1399b887
1.0.5 (67) 2026-10-15 TestFlight. The terminal stays on screen while it reconnects, and a socket or stream that goes quiet is redialled or resynced; control is taken before a tapped answer or Interrupt; MCP Accept/Decline dialogs answered; a harness made from Find lands in the tab picked on the chips; the QR camera's first step matches "On your computer, go to"; onboarding stall counting; Phone set-up for a device with no screen. ASC refused it as 1.0.4 (67): 1.0.4 had been approved, so it went up as 1.0.5. Built from feat/mobile-ios-android at cf9e70d8
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. 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)
1.0.9 (72) 2026-10-21 TestFlight, then submitted as 1.0.9. The system banner shows while the app is open, and agent questions and turn tiers reach phones over the relay; faster terminal typing over P2P; Change agent hands over the conversation and can switch a busy Claude harness; a Harness OS computer's Version page, its update's restart and Unlock after one; Set up a device under Add computer; a desk tab renamed or closed by holding its chip in Find. Built from feat/mobile-ios-android at 9c329760, the merge of local main with origin's #1499
1.0.10 (73) 2026-10-23 TestFlight. The phone's first session: task chips, one suggestion with a Send button, the keyboard over its task and a mic that sends the prompt, and Desktop's engine choice; a Harness OS computer signed out, its password changed, SSH turned on; Version lists releases and takes a newer OS release only; a pasted image waits for its transcode before uploading. 1.0.9 had been submitted, so it went up as 1.0.10. Built from feat/mobile-ios-android at 3c024672
1.0.11 (74) 2026-10-26 TestFlight. Claude Code scroll keeps up with the finger. 1.0.10 is approved, so it went up as 1.0.11 to carry refreshed App Store screenshots. Built from feat/mobile-ios-android at 13b9b38b
1.0.12 (75) 2026-10-30 TestFlight. A Harness OS computer signs in to GitHub, checks for updates, sets up Intern 3 and offers Computer use; Settings ▸ Experimental with Swarm, off by default; WebSocket reconnects back off; terminal uploads no longer freeze. 1.0.11 had been submitted, so it went up as 1.0.12. Built from feat/mobile-ios-android at 3a258bb8
1.0.12 (76) 2026-10-30 TestFlight. Set up Intern 3 from Computers goes back to that list when done; in Swarm, a calmer Home, a simpler chat, Not delivered yet and Jump to first unread. Built from feat/mobile-ios-android at 3ab12ed5
1.0.12 (77) 2026-11-02 TestFlight. Start opens the new computer's harness, with a keep-on warning while updating and a bar while an agent installs; in Swarm, the floating chat composer, invitations, task steps and chat files up to 256 MB. Built from feat/mobile-ios-android at 78c63a84
1.0.12 (78) 2026-11-02 TestFlight. In Swarm only, nothing else in mobile/lib changed since 77: the Buddy tab opens your one Swarm Buddy chat, Home's Sort by and Filter menu and always-on While you were away, a long press on a machine opens its menu. Built from feat/mobile-ios-android at 2c6939e6
1.0.12 (79) 2026-11-03 TestFlight. In Swarm only, nothing else in mobile/lib changed since 78: invitations on Home with Join and Not now, Older chats from Home, a project's number counts only its own chat, the Buddy picker says when a machine is paused. Built from feat/mobile-ios-android at e8620dbe
1.0.12 (80) 2026-11-03 TestFlight. The iPhone joins the Intern 3 setup hotspot itself, and Set up Intern 3 reads a computer whose key is not logged yet as connecting, with a bar, on a slow Wi-Fi; in Swarm, the Slack-style Home and chat, Markdown in messages, route rows, terminal notes and proposals drawn as on Desktop, drafts and Not sent kept per account, search, and writes sent with the phone's own sign-in. Signed without its entitlements (see 83), so this build cannot join the setup hotspot itself. Built from feat/mobile-ios-android at 7814f059
1.0.12 (81) 2026-11-04 TestFlight. Set up Intern 3 tries the hotspot again, checks the Wi-Fi, falls back to Settings, keeps Wi-Fi passwords and says when a setup failed; a stopped agent can be resumed; in Swarm, voice messages, editing and deleting your own message, Mark unread and Remind me, link previews, adding and removing agents, project sharing and settings, and the System, Dark or Light theme. Signed without its entitlements, like 80. Built from feat/mobile-ios-android at 4aa17808
1.0.12 (82) 2026-11-05 TestFlight. Push notifications (APNs) and fewer repeated question notices. Signed without its entitlements, so it has no push and no setup hotspot: use 83. Built from feat/mobile-ios-android at 0c47f4f8
1.0.12 (83) 2026-11-05 TestFlight. The same code as 82, the first build signed with its entitlements: aps-environment (production) and the setup hotspot. 80 to 82 went up without them because the archive is unsigned and the export signs only what the app carries; release-ios.sh now signs them onto the archived app and checks the exported app before it uploads. Built from feat/mobile-ios-android at 0c47f4f8
1.0.12 (84) 2026-11-06 TestFlight, uploaded from another Mac with --build-number=84 (#3303). Whether it carries its entitlements was not checked. Built from main at b8b8c8ea

pubspec.yaml is at 1.0.12+85 with #3303, the next build number. Build 84 (1.0.12) is the last TestFlight build and 79 the last Play build (54 went up outside this record, 53 went to Play only); do not upload any of them again. 1.0.1 to 1.0.10 are approved and 1.0.11 is submitted or approved, so new builds go up as 1.0.12 until it is submitted or approved too. Check App Store Connect before uploading if another release has happened meanwhile.

Why the app is iPhone-only

TARGETED_DEVICE_FAMILY = 1. It was "1,2" — Flutter's default — and App Store Connect answers a universal binary by requiring a 13-inch iPad screenshot set on top of the iPhone one, which is what blocked Add for Review.

⚠️ The iPad LAYOUT still exists and is still reached by the shortest-side breakpoint in lib/phone/phone_layout.dart ("an iPad keeps the rail beside its terminals"). Nothing about it was deleted; it simply is not shipped to iPad any more. Putting iPad back is one line here plus a 13-inch screenshot set — and a new build, since the requirement follows the BUILD selected on the version, not the app record.

Uploading is not submitting. Processing takes 5–30 minutes, then the build becomes selectable in the version's Build section.

Metadata — what goes in each field

Fill these on Distribution ▸ iOS App 1.0.0. Apple will not accept the version while Description, Privacy Policy URL, App Privacy, age rating or pricing are blank.

Subtitle (30 max)

Your coding agents, anywhere

Promotional Text (170 max — editable later without a new build)

Attach to the coding agents already running on your machines. Same panes, same scrollback, end-to-end encrypted — now from your phone.

Description

Harness puts the coding agents running on your own computers in your pocket.

Claude Code, Codex, Cursor and a dozen others already run on your Mac or Linux box. Harness keeps
each one in a live session on the machine it runs on, and this app attaches to those sessions from
your phone — the same panes, the same scrollback, exactly where you left them.

WHAT YOU CAN DO
• Read what an agent is doing right now, from anywhere
• Type back: answer a prompt, approve a step, send a new instruction
• Send a photo or screenshot straight into a session
• Switch between machines and between agents in one list
• Rename, restart or delete an agent without opening your laptop

HOW IT WORKS
Sessions live on your machine, not in this app and not on a server. Closing the app, losing signal or
switching devices changes nothing about what the agent is doing — you reattach and the work is where
it was.

Everything between your phone and your machine is end-to-end encrypted. Where the network allows it
the connection is peer-to-peer; where it does not, the relay carries ciphertext it cannot read.

WHAT YOU NEED
• An Autonomous account
• At least one Mac or Linux machine running the free Harness CLI, paired to that account

Harness for iPhone is a companion to that setup, not a standalone editor or a general-purpose SSH
client. Without a paired machine there is nothing for it to attach to.

Keywords (100 max, commas, no spaces)

terminal,tmux,ssh,claude,codex,cursor,coding,agent,developer,remote,shell,devops,pair,session

URLs

Field Value
Support URL https://www.autonomous.ai/harness
Marketing URL https://www.autonomous.ai/harness
Privacy Policy URL https://www.autonomous.ai/privacy — the address every Harness listing names, and the one Settings ▸ About ▸ Privacy Policy opens (lib/phone/privacy_policy.dart)

What's New — leave empty for 1.0.0; it is only shown for updates.

App Privacy

Answer these from what the code actually does, not from habit. The app has one third-party SDK, on Android only: Firebase Cloud Messaging (firebase-messaging, no Analytics), which is how a push reaches an Android app that is not running (android/app/src/main/kotlin/ai/autonomous/harness/android/PushService.kt). iOS pushes go through Apple's own APNs, with no SDK. Analytics go to Autonomous's own event_tracking endpoint (lib/analytics/), and crash records are written to a local errors.log and never leave the device (lib/core/crash_log.dart).

Data type Collected Linked to the user Purpose
Contact Info ▸ Email Address Yes Yes App Functionality, Analytics
Identifiers ▸ User ID Yes Yes App Functionality, Analytics
Identifiers ▸ Device ID Yes Yes App Functionality: the push token, so the backend can notify this phone (docs/design/2026-11-05-phone-push.md)
Usage Data ▸ Product Interaction Yes Yes Analytics
Diagnostics No — crash log stays on device

Tracking: No. Nothing here follows a person across other companies' apps or goes to a data broker, so the app needs no App Tracking Transparency prompt.

Terminal contents are deliberately outside all of this: Analytics.track's contract forbids message text, prompts, terminal output, file contents and absolute paths, and the session bytes themselves are end-to-end encrypted.

App Review notes — the part that gets 1.0 rejected

A reviewer opens this app, signs in, and sees no machines, because they have none running the CLI. That reads as a broken or incomplete app (Guideline 2.1) and it is the single most likely reason this version comes back. So:

  1. Create a demo account and put it in App Review Information ▸ Sign-In Required.
  2. Leave a real machine online, paired to that account, for the length of the review — a reviewer who can attach to a live agent cannot mistake the app for an empty shell.
  3. Paste notes along these lines:
Harness is a companion app for developer agents running on the user's own computers.

Demo account: <email> / <password>
A Mac paired to this account is kept online for the review, so the Agents tab will list live
sessions. Tap one to attach to its terminal, read the output and type into it.

The app does not run any agent itself: it attaches over an end-to-end encrypted channel to sessions
owned by the user's own machine, which is why an account with no paired machine shows an empty list.

The camera permission is used only when sending a photo into a session (Agents ▸ a session ▸ the
image button).

The microphone permission is used only for voice input: the mic button under a session's terminal
records what is said, and it is transcribed into the message sent to that session (a session ▸ the
mic at the bottom right).

Submitting

  1. Build section ▸ + ▸ pick the build you uploaded.
  2. Fill everything above, plus age rating and Pricing and Availability.
  3. Add for Review ▸ Submit for Review.
  4. Watch for Pending Developer Release after approval — approved is not released; that state waits on a button of yours, forever if you let it.

Open risk — export compliance

ios/Runner/Info.plist declares ITSAppUsesNonExemptEncryption = false, which auto-answers the export question and is right only for an app whose encryption is the OS's own HTTPS. This app terminates its own end-to-end encryption (X25519, ChaCha20-Poly1305, a CPace PAKE — lib/e2ee/), so that answer is very likely wrong. Settle it with whoever owns export compliance before submitting: a wrong answer is not a build failure, it is review asking a question and the version standing still until someone answers it.

Android — Google Play

The Play app is OpenHarness, package ai.autonomous.harness.android. ⚠️ That id is permanent from the first upload on: Play keys the app on it and there is no renaming it afterwards.

Build

bash mobile/scripts/release-android.sh   # -> build/app/outputs/bundle/release/app-release.aab

It builds and checks the bundle is signed with the upload key; it does not upload. Play takes the .aab by hand: Play Console ▸ OpenHarness ▸ Test and release ▸ a track ▸ Create new release.

The versionCode is the same +N as the iOS build number. Each store keeps its own count, so one +N can go to both — but Play refuses a versionCode it has seen, exactly as App Store Connect does, so the +N is bumped after an upload to either store.

The upload key

~/.android-release/harness-upload.jks          the upload key (PKCS12, alias `upload`)   (chmod 600)
~/.android-release/harness-upload.properties   its path and passwords                    (chmod 600)

Outside this public repo for the same reason the App Store Connect key is. android/app/build.gradle.kts reads the .properties (or HARNESS_ANDROID_SIGNING, for CI); without it a release build signs with the debug key so flutter run --release still works anywhere, and the script refuses to build.

Play App Signing holds the real app signing key — accept Google's generated key when the first release asks. This one only proves an upload came from us, so a lost one is recoverable (Play Console ▸ App integrity ▸ request an upload key reset), but that takes days. Back both files up to the team's password manager.

First release — once

  1. Create app (Play Console ▸ Create app): name OpenHarness, default language, App, Free.
  2. App content — Play will not publish anything to production while one of these is open:
    • Privacy policy: required (the app asks for the camera and microphone). Same URL as iOS: https://www.autonomous.ai/privacy.
    • App access: sign-in is required → give the demo account from the iOS review notes, and keep a machine paired to it online, for the same reason as App Review notes.
    • Ads: no. Content rating: fill the questionnaire (a utility, no user-generated content shown to others). Target audience: 18+.
    • Data safety: the App Privacy table above, restated — email address and user ID (app functionality, analytics), app interactions (analytics), device or other IDs (the push token: app functionality); all encrypted in transit; no data shared with third parties (FCM carries the push as a service provider); crash logs stay on the device. ⚠️ Plus Audio ▸ Voice or sound recordings (app functionality), which that table leaves out: voice input uploads the recording to the backend's /api/voice/stt to be transcribed. Declare it processed ephemerally only if the backend keeps nothing — TODO(BE): confirm. The same gap is on the iOS side (App Privacy ▸ Audio Data). Pictures sent to an agent are not collected: they go end to end to the user's own machine, where we cannot read them.
  3. Store listing: the iOS subtitle and description fit the short (80) and full (4000) fields; plus a 512×512 icon, a 1024×500 feature graphic, and at least two phone screenshots.
  4. Internal testing first: Create new release ▸ upload the .aab ▸ add testers by email ▸ share the opt-in link. Live for testers within minutes, no review.
  5. Production: Create new release ▸ same .aab (or Promote release) ▸ Send for review. A new app's first review takes days, not hours.

⚠️ A personal developer account created after November 2023 must first run a closed test with at least 12 opted-in testers for 14 days before it can even apply for production. An organization account (Autonomous Inc.) is exempt — check which kind the account is before planning a date.

Already built

versionCode When Where it went
16 (1.0.0) 2026-09-18 Internal testing — the first Play upload
41 (1.0.0) 2026-09-24 Built for resubmission after Play rejected the build under the broken-functionality policy (its browser sign-in redirected to 127.0.0.1, which timed out on the reviewer's device). Signs in with an emailed code instead; also carries the notices and tab marks of iOS 39–40
53 (1.0.1) 2026-10-01 Internal testing. Same code as iOS 1.0.1 (52): faster launch, QR sign-in for desktop/web/CLI (#519), tab and Find polish. First Play build from the second Mac, with the upload key copied from the first (storeFile rewritten to this Mac's path)
60 (1.0.1) 2026-10-07 Internal testing. Same code as iOS 1.0.1 (60): Google/Apple sign-in, faster launch, terminal typing, paste and scroll fixes, renaming computers and profiles, the hardened onboarding
62 (1.0.2) 2026-10-09 Internal testing. Same code as iOS 1.0.2 (62), built with the pubspec briefly set back to +62 so the two stores match: one-button Connect your computer onboarding, asleep computers shown with a refresh button, the terminal back first on reconnect, question key hints, swipe left for Computers, New Harness in Find
64 (1.0.3) 2026-10-13 Built, same code as iOS 1.0.3 (64), with the pubspec briefly set back to +64; whether it was uploaded to Play is not recorded, so treat 64 as used
65 (1.0.3) 2026-10-13 Internal testing. Same code as iOS 1.0.3 (65): the new phone onboarding, Settings ▸ Connectors, a harness's sign-in page opened on the phone, refresh on Computers. Production, published 2026-10-13
66 (1.0.4) 2026-10-14 Production, sent for review 2026-10-14. iOS 1.0.4 (66)'s code plus 51ee54c3 (a copy of the agent memo sorted in terminal_page.dart), which landed between the two builds
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 to Production (reported by the release owner on 2026-10-21)
72 (1.0.9) 2026-10-21 Built, same code as iOS 1.0.9 (72); uploaded by hand, the track it went to is not recorded
73 (1.0.10) 2026-10-23 Built, same code as iOS 1.0.10 (73); to be uploaded by hand
74 (1.0.11) 2026-10-26 Built at a pulled-back pubspec number, same mobile/ code as iOS 1.0.11 (74); whether it was uploaded is not recorded, so do not reuse 74
75 (1.0.12) 2026-10-30 Built, same code as iOS 1.0.12 (75); to be uploaded by hand
78 (1.0.12) 2026-11-02 Built, same code as iOS 1.0.12 (78); to be uploaded by hand
79 (1.0.12) 2026-11-03 Built, same code as iOS 1.0.12 (79), from e8620dbe; to be uploaded by hand