Ara CLI

The ara command line and the Ara Device worker it installs, which runs approved Ara work on your computer.
View as Markdown

August 7, 2026 — Workspace reuse behind a Git proxy

  • The Ara Device worker now reuses an existing run workspace on machines whose Git configuration rewrites remote URLs, via url.<base>.insteadOf (common with corporate Git proxies and with ssh-instead-of-https rules). The reuse check previously read the rewritten URL back and compared it against the original clone URL. Those never matched, so the worker treated a perfectly good checkout as foreign and re-cloned the repository on every run.

August 7, 2026 — Notarized CLI and worker

  • Ara CLI 0.2.31 ships an Apple-notarized command line and Ara Device worker. The signed broker and its Keychain library are now submitted to Apple’s notary service during release, so macOS Gatekeeper clears them on first launch instead of warning that Apple could not verify the app is free of malware.
  • The compiled worker no longer bundles the macOS fsevents native addon, so it no longer unpacks an unsigned helper library at runtime that triggered a second Gatekeeper warning. File watching falls back to the portable watcher.

August 4, 2026 — Verified Device handoffs

  • Ara Device and Ara Cloud now advertise and verify the same versioned worker entrypoint, protocol, and SHA-256 artifact before a session can claim the relay. A mismatched worker is fenced instead of accepting frames from a different build.

August 3, 2026 — Clean-host worker packaging

  • Execution-target status for a Device session now reads as a slim bar in place of the composer, the same way an archived session does, instead of a large block above the transcript. While Ara retries the Mac or moves the session to Ara Cloud, the bar states what it is waiting for and input stays closed; the Retry Mac and Continue in Ara Cloud choices sit inline in that bar.
  • The background worker’s login item now identifies itself as Ara wherever Ara for Mac is installed, instead of surfacing the signing certificate’s developer name in macOS background-activity notifications and Login Items.
  • Ara CLI 0.2.29 binds the active managed-runtime identity into its LaunchAgent configuration. After an upgrade, the next bare ara device gracefully replaces an older resident worker; repeated invocations on the same version remain idempotent. It also lets a completed Device session report its final Hands lifecycle events before Ara closes the run, so clean teardown is recorded without recovery cancellation or stale operation frames.
  • Ara CLI 0.2.30 advertises the exact Ara Hands worker artifact so the broker can fence stale Device installations before enqueueing work. Older Devices remain registered for existing capabilities while Hands waits for the signed upgrade instead of receiving an incompatible payload.
  • Ara CLI 0.2.27 validates persistent REPL requests before execution on the signed Bun runtime, preserving multi-statement and explicit-return browser calls without risking duplicate evaluation.
  • Ara CLI 0.2.26 embeds the browser runtime metadata used by Ara Device, so a newly installed worker no longer depends on files from the release builder.
  • Production publication now waits for the signed Darwin arm64 package to run its version and Device lifecycle checks on a checkout-free Mac.
  • Ara’s local operation broker now admits the long-lived Hands connection used by Device sessions, so a selected Mac can receive the session instead of stopping before the operation reaches its worker.
  • Device checkpoints use leader-consistent object writes and reads, with a bounded transport retry, so a Mac and Ara Cloud can verify the same durable workspace even when they run in different regions.
  • Ara persists verified Device checkpoint metadata under explicit database types before allowing the Mac turn to continue.
  • Repository-bound Device sessions stay on the selected Mac when a full-tree checkpoint exceeds the 100 MiB safety cap. Ara durably marks cloud continuation unavailable and rejects stale checkpoint handoff instead of misreporting the Mac as unreachable or restoring older work.
  • If a session restarts before a Mac binds, recovery fences the old Device writer, confirms the relay name is absent, then waits for the recreated cloud worker before starting relay services. If the old one-slot worker is still draining, Ara retries only that same Mac after complete cleanup; it never silently switches targets.
  • Display prewarm skips Device relay workers because the real browser and desktop live on the enrolled Mac.

August 2, 2026 — Managed native worker

  • Run ara login, then bare ara device, to install or repair this Mac as a full-access background Ara Device. Repeating ara device is idempotent.
  • The signed worker updates its managed runtime, health-checks the active release, and rolls back a failed activation.
  • Ara Device stays an execution target for an Ara session; conversation and session history remain in Ara web.
  • Ara CLI handles sign-in and local setup, MCP connects coding agents to Ara’s typed tools, and Ara Device runs approved file and shell operations on the selected computer.
  • To connect a Mac, open Workspace → Devices, choose Copy Ara CLI setup on the Add a Mac card, and complete the browser approval.