Tideline Join the waitlist

macOS companion · coming soon

Your hardware.
Any agent.
Proven results.

Connect your Mac to the coding agents you already use. They build, boot simulators, and run acceptance tests on your machine — and hand back evidence you can verify.

No rented Macs. Nothing crosses the line without your scope.

4 agents · 3 simulators
Animation of four cloud coding agents, Claude Code, Codex, Cursor and Grok, sending jobs to Tideline at the same time. Tideline passes the jobs across the line to three iPhone simulators on your Mac and runs them in parallel; Grok's job waits in a queue and runs on the first simulator to finish. Each simulator passes its checks, and the evidence travels back to the agent that asked for it.

How it works

The agent works in the cloud. The proof happens on your Mac.

  1. 01

    Connect a Mac

    Install the menu-bar companion and pair it with your account. Your Mac becomes a worker — with your Xcode, your simulators, your signing setup.

  2. 02

    Point your agent at it

    Claude Code and other coding agents request jobs through Tideline. Each job is scoped to a repository, a branch, and the actions you allow.

  3. 03

    Build, launch, assert

    Your Mac compiles the change, boots a simulator, drives the app, and checks the expectations the agent wrote down before it started.

  4. 04

    Get evidence back

    Screenshots, a recording, logs, and assertion results return to the agent and to you — so “it works” comes with something you can check.

Evidence

Watch the agent prove it.

The agent says it fixed the bug. Tideline runs the change on your Mac: it builds, boots the simulator, taps through the app, and checks what should be on screen. Every step leaves a line: solid once proven, dashed while it runs, dotted until it happens.

Proven
Compiled, launched, asserted, or captured.
In progress
Running now; the result is not in yet.
Pending
Planned, not yet reached.
Live · Mac Studio
Animation of an example run. You ask the agent to fix a crash and prove it. The agent patches the code and starts a run on your Mac. The app builds, the iPhone simulator opens the app, taps Get started, types an email address, and checks that the Verify your email screen appears. A screenshot is captured, and the agent reports that 14 of 14 checks passed, with six screenshots and a recording attached.

Workers

Every Mac you own, one status line each.

See which machines are online, what they are running, and which simulators are ready. The same glyph sits in your menu bar: a filled dot when all is well.

MacStatusXcodeResourcesCurrent job
Mac StudioM4 Ultra · 128 GB · macOS 26.1 Busy Xcode 26.1 62% cpu · 41 GB free Claude Code · feat/onboarding-v2 · UI tests
MacBook Pro 16″M3 Max · 48 GB · macOS 26.0 Online Xcode 26.0 4% cpu · 31 GB free Idle · 2 simulators booted
Mac mini (office)M2 · 16 GB · macOS 15.6 Sleeping Xcode 16.4 Wake on job Last seen 3h ago
  • Connected A worker is online and reachable.
  • Busy A job is being worked.
  • Offline The Mac exists, but isn’t here.
  • Error The connection itself is broken.

Scope

A tideline is a boundary. So is Tideline.

Remote agents work on one side of the line, your hardware sits on the other. You decide what crosses.

Agent access is a switch

Turn agent access on or off for each Mac from the menu bar. A sleeping or paused Mac takes no jobs.

Jobs are scoped

Every job names the repository, branch, and actions it needs. Anything outside that scope is refused, not attempted.

You can always stop it

Watch each step live, pause after the current one, or stop the agent outright. The timeline keeps what already happened.

Tideline for macOS is coming soon.

Join the waitlist and we’ll write when the companion app is ready to connect your first Mac.

Join the waitlist