Corbits Workbench

The multiplayer workspace for humans and agents.

Corbits Workbench is the open-source workspace where your team and your AI agents work side by side in shared benches — same threads, same workflows, same inbox. It is the default implementation of the Corbits Platform — a set of pluggable libraries with Interchange at the core — offering agents, workflows, and multi-tenant capabilities for organizations embracing agentic solutions. Grounded in your team's own knowledge, with every external side effect behind human approval.

Workbench will install and run with a single command. That command does not exist yet — until it does, work from a source checkout as described below.

Requires Bun >= 1.2.

bun install
bun run typecheck && bun run lint && bun run test

Requires Bun >= 1.2 and a local Postgres with the pgvector extension — any Postgres 17 you point DATABASE_URL at works. On macOS:

brew install postgresql@17 pgvector
brew services start postgresql@17

Then:

cp .env.example .env
bun run dev

bun run dev validates your .env (reporting every missing or malformed value at once), verifies the database in DATABASE_URL is reachable and actually speaks Postgres, applies any pending platform migrations, builds the web UI if it has not been built yet, and starts the hub and one sidecar together. Every required setting lives in .env.example with its expected shape, and the administrator account (HUB_ADMIN_EMAIL / HUB_ADMIN_PASSWORD, defaulting to [email protected] / password123 when unset) is seeded so you can sign in immediately.

bun run dev only seeds that account — it provisions no bench, catalog, or workflows. Once the stack is up, run these against it (in another terminal):

bun run setup
bun run seed

bun run setup provisions the bench for the administrator account; bun run seed deploys the default workflow set and plants the tenant catalog's model data, so interactive instances have a model to resolve against. Both read their configuration from .env (see .env.example) and are safe to re-run. ANTHROPIC_API_KEY is the one optional line worth setting before you run bun run seed — with it, seeding plants a real credential and the catalog is actually launchable; without it, everything above still runs, but inference errors until you set it and re-run bun run seed.

Leaving ANTHROPIC_API_KEY unset doesn't just apply to the administrator account: anyone who signs up gets a personal bench with no default routines deployed, and first-run tells them exactly that. Onboarding walks them through picking a provider — Anthropic, OpenAI, or Google — and pasting their own key, proves it with a real call before storing anything, then deploys and confirms the default routines on the spot — no separate bun run seed step, no docs to read. The tenant's browsable model catalog is only planted for Anthropic today; the other providers still get a credential and working routines, just not a catalog entry yet.

Email/password sign-in always works. To let people sign in with an existing Google or GitHub account instead, set that provider's client id and secret in .env — GOOGLE_CLIENT_ID/GOOGLE_CLIENT_SECRET and/or GITHUB_CLIENT_ID/GITHUB_CLIENT_SECRET, each an independent pair. The matching button then appears on the sign-in screen automatically; leave both values of a pair unset to leave that provider off. Setting only one value of a pair is a boot-time error — the hub refuses to start rather than silently disable the provider. See .env.example for where to register each OAuth app and what redirect URI to configure.

Chat — the shared conversation surface humans and agents both use — is documented separately in docs/CHAT.md.

• bun run check — the full gate: typecheck, lint, test
• bun run test — workspace tests
• bun run format — prettier write

Conventions and agent guidance: AGENTS.md. Contributions: CONTRIBUTING.md.

GPLv2 with the AI Exception — see LICENSE.md.