ABRALO / OPEN-SOURCE AGENT WORKSPACE

Build software
with a team of agents.

Give coding agents a shared brief. Let them hand off work, inspect each other’s changes, and bring decisions back to you.

Local service + browser UI · Apache 2.0
Codex / Claude Code / OpenCode connection details ↗

RECORDED BUILD 001

A working uptime monitor, from a shared brief.

3 Codex agents · Real code
01 / RESULT

A real monitoring service, dashboard, and incident history.

Recorded demo · Starting automatically
Edited recording · Waiting time removedFull recording ↗

Actual Abralo sessions and application captures. A detailed sample brief, three Codex agents, and an operator directing the build. This demonstrates a local prototype, not unattended production deployment.

THE OUTPUT / CHECK IT YOURSELF

The code is part of the demo.

01 / RUN IT

Beacon uptime monitor

HTTP checks, a live dashboard, persistent incident history, and a documented API. Node.js, no third-party dependencies.

Source & run instructions ↗
02 / VERIFY IT

17 tests. A real bug caught.

The reviewer caught a content-type validation defect. The backend engineer fixed it; all 17 tests now pass, including the unchanged regression test.

Read the validation results ↗
03 / FOLLOW IT

The actual handoffs

Read the brief and agent messages, including the operator’s follow-up decisions. No fabricated responses or generated activity feed.

Open the build transcript ↗

Scope: local developer prototype. Test targets are controlled loopback fixtures. The Docker configuration is included; its verification status is recorded with the test results. No production-readiness or speed benchmark claim.

HOW ABRALO FITS

A conversation layer
around the tools you use.

Abralo keeps people, agents, and project context in one workspace. The native coding runtimes still do the work.

01Browser interfaceDMs, shared rooms, threads, decisions
02Local workspace serviceConversation state, task routing, artifacts
03Native agent runtimesCodex · Claude Code · OpenCode
04Your provider accountsModel processing and provider billing

Shared context, explicit tasks

Address an agent in a room. Give it a bounded job and follow the result in the same conversation. Direct messages stay separate.

Work you can inspect

Repository tasks use separate Git worktrees from committed HEAD. Ordinary folders are edited directly. Review the output before merging or using it.

Your machine, your accounts

Workspace state stays on your computer. Model requests go to the provider you connect. Local execution is not a universal security sandbox.

04 / BEFORE YOU BEGIN

A few useful
details.

What exactly am I installing?

A local workspace that opens in your browser, with a service running on your computer. It gives people and AI agents direct conversations, rooms, and threads. The preview app currently appears as Agent Workspace in your application menu.

Which agents can I connect?

The preview includes Codex, Claude Code, and OpenCode runtimes. You need your own supported provider account and any required entitlement. OpenCode also needs a model selected from its connected provider.

Access and billing depend on the provider. Claude’s third-party subscription sign-in route remains a public-launch limitation; we have not established provider approval for that route. The recorded build above uses Codex only.

Provider and onboarding notes ↗
Where does my work go?

Workspace conversations are stored on your computer. Agent requests are processed by the provider you connect, and tools may send data to services you authorize. Running locally does not mean model requests stay on your device.

Access and privacy details ↗
Is it free? Is it open source?

The Abralo source is available under Apache 2.0. Provider subscriptions or API usage are separate. Bundled third-party components retain their own licenses.

How finished is the preview?

It is an early release. Automated builds and checks passed for Windows x64, Linux x64, and both Mac architectures. That is not a guarantee for every machine or account. Windows and macOS packages are unsigned; follow the installation guide and expect security warnings.

The terminal installer step is still part of setup. There is no published npm installer yet.

THE OPEN-SOURCE PREVIEW / v0.1.3-preview

Bring one task.
See where it takes you.

Start with a small project and one agent. Review the result, ask for a revision, and make the workspace your own.

Start with the setup guide ↗

Unsigned preview · Your own provider account required