Openbase Coder is a voice IDE for real engineering work. Speak a task, keep a live coding call open, steer long-running agent threads, approve sensitive actions, read reports, and review diffs from the same control surface.

This repository is the main open-source entry point for Openbase Coder. It contains the local openbase-coder runtime, the public product docs, the developer setup path, and the service layer used by the Mac app, iOS app, Android app, web console, and Openbase Cloud.

Openbase Coder is built around the actual loop of AI-assisted engineering: describe the change, let agents work, keep the thread moving, approve the risky parts, and inspect the result before it lands.

Core workflows are:

• Start and steer coding work by voice through a dispatcher agent.
• Route an active voice call between the dispatcher and individual Super Agents.
• Track running, waiting, completed, and failed coding threads.
• Continue threads from the Mac app, browser console, iOS app, Android app, or CLI.
• Approve or deny agent permission requests without babysitting a terminal.
• Review live output, generated Markdown reports, and git diffs.
• Browse projects, reports, routines, skills, templates, devices, service health, and runtime settings from the shared dashboard.
• Use your iPhone or Android phone as the remote control for calls, approvals, reports, diffs, and thread follow-up.
• Run the local runtime on your Mac, a Linux machine, Windows (natively — in beta — or via the Docker image), or an Openbase Cloud DevSpace.
• Extend the runtime with plugins, skills, routines, bootstrap commands, and console pages.

Openbase Coder has several user-facing surfaces backed by the local openbase-coder runtime:

• Mac app: the production, no-terminal path. It bundles the CLI, runs guided setup, hosts the dashboard, manages updates, and can share your screen into the active voice room.
• iOS app: the voice and review client. Start calls, transfer voice to agents, follow threads, handle approvals, read reports, and inspect diffs from your phone.
• Android app: the same phone client for Android (Kotlin/Compose), mirroring the iOS workflow — calls, threads, approvals, reports, diffs, and screen-share viewing.
• Web console: the same dashboard served in a browser by the local runtime.
• CLI: the local service manager and automation surface for setup, login, services, plugins, routines, voice routing, diagnostics, and development.
• Openbase Cloud: account, OAuth, device onboarding, subscriptions, and cloud DevSpaces.

The CLI runs the local Django API, WebSocket endpoints, LiveKit voice services, Codex/Super Agents coordination, project and diff APIs, plugin system, bundled agent instructions, skills, and console assets.

When you can use a terminal, the recommended path is the editable Developer Setup: clone the workspace and run its interactive ./scripts/setup. The Electron dashboard and Swift menu-bar app are optional visual surfaces after setup; Electron never owns a development install.

For a production install with no terminal:

1. Download Openbase Coder for macOS from openbase.cloud/downloads.
2. Open the app and follow guided setup. The app activates the bundled CLI, checks prerequisites, lets you choose a coding backend and voice provider, signs you in, and helps pair your phone over Openbase VPN or Openbase Direct.
3. Install the iOS beta or the Android APK from the Downloads page if you want the phone control surface for voice calls, approvals, reports, and diffs.

Prefer a container? Run the openbaseai/openbase Docker image instead of the Mac app — it runs the full runtime in a Linux container (with Docker Desktop on Windows). See Run in Docker.

On Windows you can also run the runtime natively (beta): ./scripts/setup works from a Windows checkout, and services are supervised without launchd or systemd through the Windows service backend, with Task Scheduler starting them at login. The Docker image remains the most battle-tested Windows path.

Openbase Coder is developed as a multi-repo workspace. Clone the workspace repo for source development, even if you are mainly changing the CLI:

uv tool install multi-workspace
git clone --branch main --single-branch \
  https://github.com/openbase-community/openbase-coder-workspace
cd openbase-coder-workspace
git checkout main
./scripts/setup

To install the current development branch instead:

uv tool install multi-workspace
git clone --branch develop --single-branch \
  https://github.com/openbase-community/openbase-coder-workspace
cd openbase-coder-workspace
git checkout develop
./scripts/setup

After cloning the workspace, use dev-docs/DEV_RUNBOOK.md for the full developer install, authentication, verification, and iteration flow.

The workspace setup syncs the public development repos with multi, builds the console from source, and runs openbase-coder setup --workspace-dir against the checkout. Keep the workspace on the branch you want before running setup: multi mirrors the workspace branch into synced subrepos, while repos pinned in multi.json stay on their configured branch. The CLI source for this repository lives at cli/ inside the workspace.

For CLI-only development after workspace setup:

cd cli
uv sync --extra dev
uv run openbase-coder --version
uv run pytest

If you want a persistent openbase-coder command backed by your checkout:

uv tool install -e ./cli

The product docs live in this repository under docs/ and are published at docs.openbase.cloud.

Downloads

Getting Started

Desktop App

iOS App

Web Console and Openbase Cloud

Run in Docker

Commands

Configuration

Troubleshooting

Openbase Coder is in beta. Please help shape the product by opening a GitHub issue or joining the community on Discord.

Special thanks to our Peruvian hackathon participants @rivacortez and @Diego22rct, whose fork work is the foundation of native Windows support — the cross-platform service runners, the Windows service backend, cross-platform file locking, and the Windows setup path all draw on their contributions.

The open-source Openbase Coder CLI/runtime is licensed under AGPL-3.0-only.