Local agents, MLX models and your own machines, connected in one desktop app.
Apple Silicon macOS. Release 4.0.1 is Developer ID signed and notarized.
Keep working on your laptop while a linked machine handles an agent task. Sign in on your devices, bring them onto your private mesh, and choose where the work runs.
Link brings device discovery, availability and remote prompt execution into LeanZero Agent. The destination keeps its own workspace and compute. Your laptop does not need to hold every model.
LeanZero Link ships inside LeanZero Agent and, for now, works only there.
Choose the task and target
Run the agent in its workspace
If you know LM Studio’s LM Link, the goal will feel familiar: use compute on another machine from the device in front of you. LM Link exposes remote models inside LM Studio. LeanZero Link connects LeanZero Agent devices and lets you dispatch agent work to them.
They are separate products and separate networks. LeanZero Link is not an LM Studio integration or affiliation.
LeanZero Agent runs its own userspace Tailscale mesh, isolated from your existing Tailscale installation. Email-code sign-in associates your devices; authenticated device traffic uses the mesh. Only link machines you trust.
The target must be awake, and it only accepts remote runs after its owner switches them on. Link does not synchronize your project files automatically, and choosing a cloud provider still sends inference requests to that provider.
LeanZero Agent 4.0.1 is our desktop agent app under its new name. A 3.x installation does not update itself to 4.0.1: download it once from this page, and later releases arrive through the updater.
Since release 3.0.110, LeanZero Agent runs two independent Forge benchmark builds from one desktop action, using the same selected provider configuration. Each build keeps its result and evidence. When both completed results are comparable, the app reports their median and range.
Cancellation covers the gap between builds. Reopening the app preserves the saved outcome without automatically replaying paid work. The frozen Forge 2.0 task and scorer stay unchanged.
Release 3.0.4 improved benchmark failure explanations and preserved complete browser recordings. The SB7.1 task and numeric scoring rules were unchanged.
New grading evidence retains the complete browser recording in original order and at original speed. The website player shows duration and position, supports seeking and makes the ending and replay explicit. Older excerpts remain identified as clips.
Initial synchronization and later recovery are reported separately. The published Gemini explanation is corrected without changing its score, original scorer provenance or its 3.0.2 build attribution.
Run the latest stable benchmark published in the catalog. Legacy, beta and alpha benchmarks cannot be launched from the app.
The app fetches the current catalog before starting a model build or retrying scoring. If it cannot verify the current release, the action stops with an explanation.
If the bundled benchmark is older than the current published version, update LeanZero Agent before running it. An older saved build cannot be retried against a different benchmark.
Earlier results, checks and recorded media remain readable. Launch restrictions do not rewrite historical scores or make different task versions comparable.
This maintenance release improves reporting and recording. The SB7.1 task, numeric scoring rules and published 49.92% score are unchanged; that model build was completed with release 3.0.2.
Release 3.0.2 introduced SB7.1, benchmark tools, activity and scoring retry. Earlier releases introduced Agent Work, memory and skills, LeanZero MLX, and agent-creation and MCP-setup refinements.
Forge 2.0 asks one model to ship v2 of an installed Jira app in an offline harness. LeanZero Agent runs two independent builds and retains each result so you can inspect what the model delivered.
The payments result below is historical SB7.1 evidence. That task asked an agent to build the Meridian Payments Console from an editable starter, combining backend consistency and recovery with a live 3D payment field, a detailed inspector and animation driven by committed updates.
For that historical task, the app recorded model activity, individual checks, screenshots and a clip from the graded browser. Swarm nodes could mix local and cloud providers; Single model used one configured provider.
The app built real payment geometry and committed-update animation, but failed important money, recovery and presentation checks. Initial synchronization completed with only 8,388 payments; daily bucket counts did not match the full fixture, applying a ×0.6 critical multiplier. Later recovery was measured separately. The 69.9% admission ceiling did not reduce the score further because earned credit was already lower.
Model build: 10m16s. Final scoring retry: 14m14s. Earlier interrupted and failed grading attempts are additional. The retry used the saved completed build without another model call. This one result does not establish subjective artistic excellence or how every leading model will perform.
Earlier evidence remains separate: the preserved development candidate scored 79.9% with 96.83% earned before its ceiling. The historical 69.9% Gauntlet 7.1 pilot retains its original sb-7.1-rc task and evidence.
We will keep shipping maintenance and feature releases. Compatible stable updates will be available through the app’s automatic updater and as a download on this page.
Use Settings → App → Updates to check now. Automatic downloads are optional. Save your work before a restart, or replace the app manually with the latest DMG.
From your first installation to a linked agent workspace. Open a chapter for the actual controls, prerequisites and recovery steps.
Choose Download for Mac to download the DMG directly. The published macOS package is for Apple Silicon (arm64); do not use it as an Intel Mac installer.
Open the disk image, drag LeanZero Agent.app into Applications, then eject the disk image. Launch LeanZero Agent from Applications. A normal first-open confirmation for an internet download can still appear on a notarized app.
The macOS arm64 release is Developer ID signed and notarized. Notarization checks the distributed software; it is not a guarantee about generated code or third-party models.
If macOS reports that an app is damaged or its signature is invalid, stop and download a fresh copy from this page. Do not disable Gatekeeper or remove quarantine attributes as a routine installation step. Report the exact version and message if it persists.