Documentation

From project to preview to live.

Start on the web, with your Agent or in the CLI.

Inspect a projectCheck support and adaptation →Connect an AgentInstall the CLI and local MCP →Manage your accountManage identity and access →

01 / Installation & client compatibility

Download the local CLI. Native Agent client combinations still await validation.

Integration and availability

CLI 0.5 provides static checks, source selection and controlled three-step publishing entry points. Actions depend on server availability. It is unpublished on npm; native Codex, Claude Code and Cursor setups await validation.

Client compatibility and tested versions

Client	Connection	Verified version	Package
Codex	BB Skill / stdio MCP / CLI	Not verified	Local package; unpublished
Claude Code	BB Skill / stdio MCP / CLI	Not verified	Local package; unpublished
Cursor	BB Skill / stdio MCP / CLI	Not verified	Local package; unpublished

View a local inspect report ↗Download CLI 0.5 local package SHA256

Local test package · Node ≥ 22.12 · Native client hosts not verified

Local installation and removal

Verify the package SHA256 before installing into a separate directory. Run these commands from the download directory; they use no global installation or MCP configuration changes.

shasum -a 256 brainbrawn-cli-0.5.0.tgz

Local package SHA256

a67a1ba713745984c899c0c610153d4b7043359c83c91d3c900adb0cf95ce7dc

After confirming the digest, install dependencies. This step requires npm registry access and disables installation scripts.

mkdir brainbrawn-cli-local
npm install --prefix ./brainbrawn-cli-local --ignore-scripts --no-audit --no-fund ./brainbrawn-cli-0.5.0.tgz
node ./brainbrawn-cli-local/node_modules/@brainbrawn/cli/dist/main.js version

Locally verified on macOS arm64, Node 26.11.0 and npm 11.20.0. Other systems and client combinations remain unverified.

Default read-only credentials do not grant write access. Source upload and publishing require specific scopes and browser confirmation; model claims cannot replace authorization.

The client starts local MCP within your explicitly authorized project directory. This is a process command, not a verified configuration for the three clients.

node ./brainbrawn-cli-local/node_modules/@brainbrawn/cli/dist/main.js mcp serve --stdio --workdir /absolute/canonical/project

The product Skill is included at integrations/skills/brainbrawn-deploy. The configuration template is for review and does not overwrite personal settings.

Remove the CLI package from the separate directory. Existing server credentials still need revocation from your account page.

npm uninstall --prefix ./brainbrawn-cli-local --ignore-scripts --no-audit --no-fund @brainbrawn/cli

Configuration protection and future integrations

The local package version and digest are available for verification. Client versions, installation scope, configuration merging, and uninstall steps remain unverified. Existing MCP and Skill settings are not overwritten automatically.

Remote MCP/OAuth is a later enhancement. Passing a remote workdir does not authorize reading or uploading files from your computer.

02 / Current availability

Account & projectsIntegrated locallyLocal CLIAvailable to downloadCloud releasesComing later

Integrated capabilities and upcoming scope

Current validation is primarily local. Accounts, projects and the three-step publishing model are integrated. Source intake, builds and cloud releases depend on the connected service.

Real email, paid purchases and native client combinations are not yet validated. Local tests do not mean cloud publishing is open.

Open Console →

03 / Target deployment flow

Select project
Preview
Publish

How the Agent and Console work together

Select a project, preview and confirm publishing on the web. Agent and CLI share the same operations and permissions. Build and version details are available when needed.

Current scope of the six MCP tools

Directory inspectionStatic inspection

bb_app_inspect

Existing App referenceCheck only; no creation

bb_app_create

Operation stateOriginal operation and publication progress

bb_deployment_status

Preview deploymentSubmit code, confirm on the website

bb_deploy_preview

Build logsService unavailable

bb_build_logs

Production publishingWebsite confirmation

bb_publish

Tool entry points and execution availability are checked separately. Unavailable services report that explicitly. Metadata or task acceptance does not mean a product is live.

04 / Identity & authorization

One account. Access within approved scopes.

Account, credentials and project permissions

Console, CLI and MCP share identity and resource ownership. Tenant changes, logout and session invalidation clear protected page data. App domains do not receive platform management cookies.

The local CLI reads only explicitly authorized project scopes. Platform credentials stay in restricted local files, outside Skills, source, examples, and logs.

05 / Confirm publishing

Preview and Production have separate permissions.

Review the preview version and its impact in the Console, then confirm publishing. The server result is authoritative.

Production approval scope and validity

Preview tokens do not grant production publishing, budget increases or payments. Production approval binds the App, environment, artifact, configuration and migration digests, budget ceiling and expiry.

Reuse an existing explicit approval while its scope remains valid. Changes beyond its target or impact require new approval. An Agent-provided confirmed=true, tool text or model statement cannot grant authorization.

06 / Source & builds

Pin source snapshots. Verify every build result.

Source protection, retries and cancellation

Review the source scope before upload, excluding .env, keys, node_modules, caches and .git internals. Builds reference a pinned snapshot or Commit, not a changing branch head.

Accepted does not mean succeeded. After a timeout or disconnect, reconcile the original operation before retrying. Closing the Agent or page stops local waiting, not the remote task.

07 / Supported scope

For supported JS/TS Web and PWA projects.

Runtime, database and compatibility limits

Scope	Targets and boundaries
Static / PWA	HTML, CSS, JavaScript and supported frontend build outputs. Offline behavior requires separate validation.
Dynamic	Adapted JavaScript / TypeScript Fetch handlers. The first target stack is React, Vite and Hono.
d1 / none	D1 or no database. Preview and Production bind data, secrets and access separately.

This is not a general Node.js host. Arbitrary Python, Go, OCI images and persistent filesystems are not promised. Inspection must distinguish supported, adaptation required and unknown. A plan upgrade cannot fix Runtime incompatibility.

08 / Data protection & exit

Manage releases, data and exit separately.

Backup, rollback and exit rules

Release rollback does not restore data. Incompatible schemas block rollback. Adapting SQLite code to D1 does not implicitly import local data or write to production.

Backup, restore and export depend on available capabilities. Archive and permanent deletion require separate confirmation; the only data source is never silently removed.