██████╗ ██████╗ ██████╗      ██████╗ ██████╗ ███████╗ █████╗ ████████╗ ██████╗ ██████╗ 
██╔══██╗██╔══██╗██╔══██╗    ██╔════╝ ██╔══██╗██╔════╝██╔══██╗╚══██╔══╝██╔═══██╗██╔══██╗
██████╔╝██║  ██║██████╔╝    ██║      ██████╔╝█████╗  ███████║   ██║   ██║   ██║██████╔╝
██╔══██╗██║  ██║██╔══██╗    ██║      ██╔══██╗██╔══╝  ██╔══██║   ██║   ██║   ██║██╔══██╗
██████╔╝██████╔╝██████╔╝    ╚██████╗ ██║  ██║███████╗██║  ██║   ██║   ╚██████╔╝██║  ██║
╚═════╝ ╚═════╝ ╚═════╝      ╚═════╝ ╚═╝  ╚═╝╚══════╝╚═╝  ╚═╝   ╚═╝    ╚═════╝ ╚═╝  ╚═╝
                                 
                       O S   A G E N T   W O R K S P A C E

🧠 BDB OS Agent Workspace (AI Orchestrator)

The ultimate Agent Meta-Harness and orchestratator for parallel AI coding agents

English · Deutsch · Português

An Agentic IDE that supervises parallel AI coding agents in isolated workspaces, with complete control and automatic feedback loops from CI failures, review comments, and merge conflicts.

What is BDB OS Agent Workspace?

BDB OS Agent Workspace is a meta-harness agent IDE for running AI coding agents in parallel. It gives agents like Claude Code, Codex, Cursor, Kimi Code, opencode, and others a shared workspace where their sessions, chat or terminal interfaces, branches, pull requests, and feedback loops can be supervised from one place.

The agents still do the coding. AO provides the harness around them: isolated workspaces, live terminal access, session state, PR awareness, and automatic loops that send CI failures, review comments, and merge conflicts back to the right agent. Instead of manually coordinating a pile of agent terminals, AO turns parallel agent work into a managed workflow.

Why BDB OS Agent Workspace?

AI coding agents become much more useful when they can work in parallel, but parallel work gets messy quickly. Branches overlap, terminals get lost, CI failures need follow-up, review comments need replies, and merge conflicts have to reach the right worker.

BDB OS Agent Workspace is built to keep that loop visible and manageable. It helps you:

• Start multiple agents from the same project without mixing their work
• Keep every session in a separate git worktree
• See which agents are working, waiting, finished, or blocked
• Route CI failures, review comments, and merge conflicts back to the right session
• Use different agent CLIs through one common supervisor

How it works

At a high level, BDB OS Agent Workspace follows a simple loop:

1. Add a project you want agents to work on.
2. Start one or more sessions from the desktop app or CLI.
3. AO creates an isolated git worktree for each session.
4. AO launches either the agent's terminal UI or a structured Chat controller, according to the session's selected interface.
5. The local daemon watches session state, controller activity, pull requests, CI, and review feedback.
6. The desktop app and CLI show the current state and let you send follow-up instructions to the right session.

The result is a local control layer for agentic coding: agents still do the coding, while BDB OS Agent Workspace keeps their workspaces, status, terminals, and feedback loops organized.

Features

The desktop app is the main control surface: projects on the left, active sessions in the center, and the selected session's Chat or terminal interface, pull request state, review runs, and browser preview in the inspector.

Supported Agents

AO ships adapters for 26 worker agent harnesses (shown by their configuration IDs):

Reviewer agents are configured separately. The current reviewer harness configuration IDs are:

Reviewer panes stay interactive. AO opens a fresh reviewer process for each pass so the selected harness's current task context, permissions, and environment are applied at launch. Pi reviewers run with project/user resource discovery and built-in tools disabled; AO loads an extension from its own data directory that exposes only read-only checkout inspection plus structured GitHub review posting and ao review submit. Agy, Continue, Devin, Droid, Goose, Kimchi, Kimi, Qwen, and Vibe are experimental host-trusted reviewers: their native modes and settings do not provide OS isolation, and some reviewers receive autonomous settings so they can complete review tasks. Grok, Crush, Auggie, Cline, and Autohand are experimental user-approved reviewers: AO supplies a hardened reviewer role and leaves native permission prompts enabled rather than passing broad unattended flags.

AO brings supported terminal coding agents into one supervised workflow.

Use the agent interface that fits the moment: structured Chat or its native terminal UI.

Install

As a BDB Agent OS Plugin (Recommended)

Integrate directly via the bdb-dev-optimized-agent-skills interactive installer. Simply select the BDB OS Agent Workspace add-on during the terminal setup.

Local Development

Clone this repository and run it locally to modify the electron app and daemon:

git clone https://github.com/hybridlabor-api/bdb-os-agent-workspace.git
cd bdb-os-agent-workspace
npm install
npm run dev

Documentation

| Document | Start here when you need | | ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | | docs/architecture.md | Backend mental model, lifecycle, persistence, CDC, status derivation, and daemon boundaries. | | docs/backend-code-structure.md | Package ownership and where each backend concern belongs. | | docs/cli/README.md | CLI behavior and daemon route mapping. | | docs/development.md | Prerequisites, build steps, running tests, and troubleshooting for local development. | | docs/STATUS.md | What currently ships on main and what remains in flight. | | docs/stack.md | Library, runtime, and dependency decisions. |

Anonymous telemetry

AO uses privacy-preserving product usage and reliability metrics—designed to exclude PII and project content—to understand adoption and improve the product. Learn more about telemetry and privacy.

License

Apache License 2.0. See LICENSE.