Track.

Track / internal preview

Give your Record a home.

The local runtime keeps your Record on your Mac and supplies the tools your chosen agents use.

Download for Apple silicon

Runtime 0.3.2 · 47.7 MB · signed by Velislav Gerov and notarized by Apple.
The Track Mac app requires macOS 26 or later. Intel Macs are not supported by this installer.

Install, then return to Track.

  1. Open the downloaded ZIP, then open Track Runtime Installer.
  2. Choose Install runtime. The installer adds a background service for your user account.
  3. Return to Track. Setup checks the local runtime automatically.

No developer tools, terminal commands, or cloud account are needed. Runtime 0.3.2 supports new installations and updates to earlier consumer installations. Updates preserve your Record, pairing and keys, and restore the previous service if verification fails. A working developer runtime is checked and reused; it stays managed by your developer setup.

From Apple Health to a conversation.

In Track on iPhone, open Agents → Health Analyst and import the Apple Health categories you want. In Devices on your Mac, create a pairing code and scan it on your iPhone. Then allow Health Analyst access separately and sync your encrypted Record.

Continue in Agents on the Mac to install the Codex plugin. Codex hosts the conversation. A source connection alone never grants an agent access.

Your Mac stays part of the connection.

Local pairing requires iOS 18 or later. Keep the Mac awake and both devices on the same local network for phone-to-Mac sync. Approve local network access on your iPhone when requested. The pairing code pins this Mac’s certificate.

The runtime keeps data in encrypted local databases and keys in macOS Keychain. An approved agent can read or organise only the context and tools you select. Imported source observations remain separate from added context.

Preview limits

Large-history iPhone sync is still being verified in internal preview. Keep Track open during the initial transfer. The local connection certificate lasts one year; certificate renewal needs a future update. Expired connections stop rather than silently changing trust.

SHA-256
cb28f120819799b5fbb15afdf2a5ccb2d0996ff81aa432baf43dc3e36f1ece87