A small start.
A useful result.

01. Download the right package.

Choose your operating system and CPU on the official release page. On a Mac, Apple menu → About This Mac tells you whether you have Apple silicon or Intel.

Download the matching .tar.gz package and SHA256SUMS. The files called “Source code” are for developers and do not include the packaged application.

Get-FileHash .\abralo-windows-x64.tar.gz -Algorithm SHA256

shasum -a 256 abralo-macos-arm64.tar.gz

sha256sum abralo-linux-x64.tar.gz

02. Extract and install.

Extract the .tar.gz archive. Open the resulting package directory that contains release.json, runtime/, and scripts/. You do not need to install Node or run a build.

Windows x64

In PowerShell, you can extract the downloaded archive with:

tar -xzf .\abralo-windows-x64.tar.gz

Open the extracted package folder in PowerShell, then run:

.\scripts\install-windows.ps1 -ReleaseDirectory .

Open Agent Workspace from the Start menu. Administrator rights are not required.

macOS

Extract the archive in Finder. In Terminal, type cd , drag the extracted package folder into the window, and press Return. Then run:

./runtime/node scripts/install-posix.mjs

Open Agent Workspace.app from your home folder’s Applications directory.

Linux x64

Extract the archive, open a terminal in the package folder, and run:

./runtime/node scripts/install-posix.mjs

Open Agent Workspace from your application menu. Do not use sudo.

Windows and macOS may show security warnings because the preview is unsigned. If installation is blocked, use the detailed installation and trust guidance. Do not disable system security protection.

03. Connect one agent.

Open Abralo, enter your name, and choose a provider for Chief of Staff. Use the provider’s sign-in screen; never paste credentials into a conversation. Check the connection before continuing.

The recorded build uses Codex. OpenCode requires a connected provider and model selection. Read the provider limitations. The Claude subscription route is unresolved; do not choose it for this trial.

An objective can be a rough outcome; you can select a project folder later.

04. Ask for something you can check.

Create a folder named abralo-first-task outside an existing Git repository. Save these fictional notes as notes.txt inside it:

Project: Lantern reading club
Meets on the first Tuesday of each month at 18:30.
Location: the community library.
Bring one book recommendation.
Attendance is free; registration is not required.

In the Chief of Staff conversation, choose Ask using the permission control. Select the folder in the composer and grant access when prompted. Send:

Read notes.txt and create README.md in this folder with a title, a one-sentence introduction and a "How to join" section. Include every fact in the notes and do not invent any others. Do not browse or install anything. Show me the file you changed.

Open README.md in that folder. Check the name, meeting day and time, location, what to bring, and the free/no-registration rule. Ask: Keep all the facts, but make "How to join" a bullet list.

Success: the file matches the notes, the revision preserves the facts, and you can find the conversation and file after closing and reopening the app. Wait until the task finishes first. To cancel active work, use Stop; closing the tab does not stop agents.

05. Bring in a reviewer.

Use Add employee → Agent to create Reviewer with the same provider. Set its instructions to: Compare documents with their source notes. Report omissions and unsupported claims. Do not change files. Choose Ask for this agent too.

Create a room named first-review with Chief of Staff and Reviewer as members. Select the same folder in the room’s composer. Mention only Chief of Staff using the mention picker, so it can initiate the handoff. Use your agents’ actual names:

@Chief of Staff read notes.txt and README.md in this folder, then ask Reviewer in this room to check that the README matches every note and makes no unsupported promises. Do not change files, browse or install anything. Bring the review back here for my decision.

Success: you see a handoff and the reviewer’s findings in the shared room. Read the files yourself, then accept the result or ask for a correction. The reviewer may find no defects. This step uses additional provider allowance.

Ready for a larger build? Build Beacon with three agents, using the original brief and concrete checks for a working uptime monitor. You can inspect the recorded handoff first.

If something gets in the way.

Need a hand getting started? Email Chris, Abralo’s creator, at chris@abralo.com. Mention the step where you got stuck. This preview has no guaranteed support response time.

Note your OS, package version, the last successful step, and the exact error. Report the issue without sharing passwords, sign-in codes, private prompts, or unredacted logs.

Suspected vulnerability? Use private security reporting. Please keep security details out of public issues.

The recovery guide covers stuck tasks, restarting, and removing the preview while keeping your data.