Overview
What BWorlds does for a Build, and what the bworlds CLI lets you and your coding agent do with it.
BWorlds takes an AI-built app from "it works" to a product clients can rely on. For each Build (one app a Builder ships), it audits the live app against production essentials, watches it in production, and keeps a prioritized list of what needs attention. Builders see all of this in the app at app.bworlds.co.
bworlds brings the same Build to your terminal, your coding agent, and your CI. Source code only says what an app is meant to do. The CLI adds what has actually been observed around that code, so a change is planned against evidence instead of a guess.
Who uses it
- A Builder on their own Builds. Sign in with the identity you use in the app. Every Build in your Workspace is available.
- A developer or consultant helping a Builder. The Builder invites you to their Workspace from the app. You use your own BWorlds identity and see their Builds until they remove you.
- A coding agent or an automated runner. Claude Code, Codex, or a CI job runs the same commands with a personal token that represents you. Every result is available as stable JSON.
Access is the Workspace Membership itself. There are no per-Build permissions to configure. See Access and context.
What you can do
Each row maps one BWorlds capability to the screen a Builder knows in the app and to the commands that reach it.
| Capability | In the app | From the CLI |
|---|---|---|
| Read the Audit: what passed, what needs attention, how to fix it | Audits | audit show, audit run, audit reevaluate, audit override, control run, control status |
| Work the Build's prioritized to-do list | Findings | findings list, findings create, findings update-status |
| See what breaks in production and what your users live through | Errors, Sessions, Uptime | telemetry errors, telemetry sessions, telemetry uptime |
| Fix in the connected repository without handling a GitHub credential | GitHub connection | repo clone, repo refresh, repo push, repo local-setup |
| Keep the Build's shared memory: how it works and what never to touch | CLI only | dossier pull, dossier push |
| Know who you are, which Workspaces you belong to, which Build you target | Workspace sharing | auth status, repo list, build info |
Reads are free and immediate. Starting or rerunning an Audit, or checking one Control, consumes the Workspace's tokens and always asks for --confirm. See Pricing and tokens.
What this preview does not cover
- The Trust Page, SDK installation, billing, and Build settings stay in the app.
- Windows and Linux on ARM have no release binary.
- The CLI works on its own temporary clone of the repository. It does not attach to a folder you already have checked out.
Start here
Quickstart
Install, sign in, and read your first Audit. Five minutes, nothing charged.
Coding agent workflows
Give Claude Code or Codex verified Build context before it changes code.
Product model
Build, Workspace, Audit, Control, Finding, Dossier: the words the CLI speaks.
Agents and automation
Stable JSON, exit codes, request IDs, GitHub Actions.
Agent-readable sources
Code agents can start from /llms.txt, read the whole corpus at /llms-full.txt, fetch any page as Markdown, and validate flags against /command-reference.json.
Three portable skills install for every coding agent on your machine, each depending only on bworlds and these pages: bworlds-cli for the command contract, bworlds-audit to audit a Build end to end, and bworlds-check for a recurring health check.
npx skills add https://docs.bworlds.co/bworlds-cli-SKILL.md -g
npx skills add https://docs.bworlds.co/bworlds-audit-SKILL.md -g
npx skills add https://docs.bworlds.co/bworlds-check-SKILL.md -g