A good start begins with the right Mac.
On the Mac that will do the work, choose Apple menu → About This Mac.
- Chip: Apple M1 or M2. Use native Apple silicon software.
- macOS: version 15 or newer.
- Memory: plan for 16 GB or more. An 8 GB Mac has not been qualified.
- Storage: allow 40 GB free, plus room for downloads and work.
Use a dedicated Mac with reliable power and internet. Keep it awake and its work account logged in while testing. If you are unsure, ask your helper to check before changing anything.
You have checked the chip, macOS, memory and storage. This page does not inspect your computer.
One download. All six roles.
The published complete archive is 406.3 MB. Download the named Mac Fleet ZIP and its matching checksum file from the official release.
ZIP: AGI_Fleet_macOS_v1.20.2.zip
Checksums: SHA256SUMS-macOS-v1.20.2.txt
Before opening code, ask your helper to open Terminal, type shasum -a 256 with a space at the end, drag the downloaded ZIP into the window, then press Return. Compare all 64 characters with the published checksum for that filename.
When they match, double-click the ZIP. Keep the complete extracted folder together in a permanent location. Open START_HERE.html for the offline guide. GitHub’s “Source code” downloads are for developers.
The checksum matches the exact ZIP, and the complete folder is extracted. A checksum is not an Apple developer signature.
Give approvals and work separate homes.
Your administrator creates two new Standard accounts in System Settings → Users & Groups, with separate passwords:
- Approval account (signer): protects the wallet and lets you approve actions.
- Work account (compute): runs the AI tools and provider sign-ins. No wallet belongs here.
Log in to the work account. Use the pinned Apple silicon Docker Desktop 4.93.0, with User CLI tools and the user Docker context. The administrator may need to place Docker in Applications; the work account stays Standard. Open Docker there, accept its terms yourself, and wait for the engine to run.
Your helper should use the verified Docker download, checksum and preparation instructions. Do not run Fleet with sudo.
Two fresh Standard accounts exist, and Docker is running in the work account.
Prepare the role you chose.
Log in to the approval account. Open the matching launcher in the complete extracted Fleet folder.
Agent: open Launch-AGI-Agent.command. The role folder is packages/AGI_Agent.
Node: open Launch-AGI-Node.command. The role folder is packages/AGI_Node.
First launch can prepare a verified private Node 24.21.0 runtime. Keep internet available. Node here is the software runtime; the Fleet “Node” role is the reviewer.
For a new wallet, use the role’s Seed-Wallet launcher and Create wallet. Keep the 12 or 24 recovery words and any optional passphrase in your private recovery records. Leave the wallet unfunded during testing.
In the connection panel, choose the intended model and Download private setup file (Node: Download my private setup file). This file connects the approval app to its worker.
You have the private setup JSON for the correct role. The wallet and recovery words stay in the approval account.
Transfer just one file.
Transfer only the private setup JSON into the work account’s own private folder. An encrypted removable drive can help. Copy it while logged in as that work user, then eject the drive.
In the work account, open Terminal. Type chmod 600 with a space at the end, drag only the copied setup JSON into the window, then press Return. This restricts access to that file; it does not display the secret.
Do not move a wallet, recovery words or the whole approval-account folder. Never upload the setup JSON to this website, GitHub or a support conversation.
If ownership or permission checks fail, use the recovery guide with your helper. Keep the original file unchanged.
The setup JSON belongs to the work user, with owner-only access. The wallet remains separate.
Follow the installer, one prompt at a time.
- Make sure Docker is running in this work account.
- Open Install.command in the complete Fleet folder or matching role folder.
- Drag the private setup JSON into the waiting Terminal prompt and press Return.
- Read the account-separation confirmation. The installer prepares its private Node and OpenClaw runtime.
- Complete the provider sign-ins shown below, in this work account.
- Review the role, permissions and limits. Type the displayed APPROVE phrase only if they match your intent.
- Wait for authenticated readiness and transaction: complete. Keep the setup report.
Agent sign-ins: Creator, Checker and Reviewer, in separate stores.
Node sign-ins: Checker and Reviewer, in separate stores.
New profiles allow up to 256 runs per rolling 24 hours and 32 image attempts for Agent/Node. Provider usage can cost money; set your approved provider budget before testing. Separate stores alone do not establish independent reviewers.
The installer reports transaction: complete, with authenticated readiness. A listening port alone is not enough.
Look at the actual result.
Return to the approval app. Review the authenticated worker identity and approve only the intended bounded connection test.
Choose Test my connection, then Create test documents. Download and open the files. Check that they contain the expected work. You can then try a small public task in Studio using Create & check the work.
Use the Node review workflow with the original public inputs, the actual delivered files and explicit acceptance criteria. Check the reviewer’s evidence and decision. An Agent result cannot qualify this Node.
Confirm positive cleanup evidence for both work and browser containers, the saved observer record and workspace finalization. If COMPUTE_STOP appears or cleanup is uncertain, preserve the stopped state and use the help below.
You have inspected the real output or review, and both cleanup checks are confirmed. The website cannot verify these observations.
Keep the evidence. Know what comes next.
Record fresh installation, Docker isolation, real provider work, document results, cleanup, stop/recovery and reboot identity using the physical qualification checklist. The full qualification also requires 72 uninterrupted observed hours and independent review.
The release targets M1 and M2; completing one machine does not qualify the other. Each role needs its own observations. Apple signing and notarization remain pending.
Keep funded jobs and transactions off until the required operating, contract and review checks are accepted. Marking these guide steps does not grant permission to run paid work.
Your observations are recorded for this exact release, with outstanding items clearly identified.
Your checkmarks are personal reminders. They do not install software, inspect the Mac or verify qualification. This website never asks for wallet recovery words, passwords or the private setup file.
A little help, right here.
Which account should I be in?
The label above each step tells you. Your administrator prepares accounts and shared applications. Your Standard approval account protects the wallet. Your separate Standard work account runs Docker and AI tools. Return to the approval account to approve actions and inspect results.
macOS will not open the app
This release is unsigned and unnotarized. Check the official ZIP and its checksum first. Ask your helper to follow the file-specific approval in System Settings → Privacy & Security for that verified item only. If approval is unavailable, stop and use the recovery guide. Open recovery help ↗
The installer stopped or cleanup failed
Keep the error and stopped installation. Do not delete COMPUTE_STOP, containers, profiles or accounts. In the existing work account, open Repair-Compute.command from the matching role folder and choose 1 — Export current sanitized report. If no profile exists yet, keep the installer’s failure and report location. Review the report before sharing; never send the setup JSON or credentials.