macOS · local-first · source-build alpha
Local-first AI agents, at home on your Mac.
OpenAgentFleet is a Mac app where AI agents do real work for you — on a separate computer you can watch, with everything stored on your own machine.
- Watch
- Stop
- Take control
- Approve
The workflow
Four steps from a fresh Mac to a working agent.
The actual setup screens of the current alpha — nothing turns itself on.
Agent Computer
A separate computer you can watch.
Browser and desktop work happens on a separate Linux computer, not on your Mac’s own screen. Its screen sits in the app, in plain sight, started only when a job needs it.
Chromium
Browsing, sign-ins and downloads happen there — never in your own browser.
Terminal
Command-line work runs on that computer, against its own files.
Files
What the agent fetches and edits stays there until you decide to take it out.
Your hand on the wheel
Watch it live, stop the run at any point, or take over the session yourself.
Capabilities
What the current build actually does.
- Named agents, local memory
- Each agent keeps its own role and memory on your Mac. You can review, edit or archive what it remembers.
- Three engines, one workspace
- Grok Build, Codex App Server and the built-in OpenCode each run on your Mac, under your own accounts.
- Approvals for sensitive actions
- Sensitive and external steps wait for your explicit yes. Passwords, two-factor codes and payments stay with you, on the Mac.
- Private phone control optional
- Follow conversations and the agent’s computer from your phone over a private, encrypted connection. Off by default.
Trust
Where the boundary actually is.
What stays on your Mac
Conversations, agent memory, attachments and the approval record are stored by the local OpenAgentFleet service. Only what you choose to send to an engine leaves the machine — through that provider’s own CLI and your own account.
What the Agent Computer is — and isn’t
The Agent Computer is the boundary for browser and desktop work: a separate Linux machine whose screen you can always watch. It is not full provider-process isolation — the engines’ CLIs themselves currently run on macOS. Sensitive input stays on the trusted Mac.
macOS alpha
The alpha builds from source.
There is no signed download yet, and notarization is not completed. Until it is, OpenAgentFleet is a developer build you compile yourself, and the repository stays private — alpha access is by invitation.
- Apple Silicon Macthe desktop app targets macOS on Apple Silicon
- Bring an engineGrok Build or Codex App Server if you have them — the built-in OpenCode works out of the box
- Agent Computer on demanda containerized Linux guest, started only when you use it
FAQ
The useful answers, when you need them.
A few plain-language boundaries for the current alpha. The full setup and troubleshooting guide lives in the repository.
Is OpenAgentFleet a cloud service?
The workspace, memory and Agent Computer run on your Mac. Your selected provider may still send prompts to its own remote AI service.
What is the Agent Computer?
A separate Linux desktop with Chromium, Terminal and Files. You can watch it, stop it or take control when a human needs to handle a sign-in or sensitive step.
Is the whole agent isolated from macOS?
Not yet. The Linux computer is the browser and desktop boundary. Provider CLIs currently run as normal processes on macOS.
Do I need Grok or Codex?
No. Grok Build and Codex App Server are optional engines. Bundled OpenCode is the starting fallback, subject to your local provider configuration.
Can I use the app from my phone?
Yes as an optional remote-client path: the Mac stays the execution host and the phone connects over a private network such as Tailscale.