Babai Docs
Deploy from your agent, not a dashboard.
These MVP docs cover the CLI-first flow: install, first login, deploy, logs, limits, failures, and what is intentionally not included.
Install
Install the Claude Code or Codex plugin once the external plugin repositories are published. Plugin wrappers stay outside this monorepo and talk to the hosted MCP server.
First Login
The first deploy opens localhost:3005/auth/cli with a one-time session code. Clerk offers GitHub, Google, email magic link, and email/password. Every method maps to the same Babai user and token flow.
Deploy
Run /babai:deploy from Claude Code or Codex. The agent describes the project, stores secrets safely, uploads a gitignore-aware zip, triggers Cloud Run source deploy, and returns a random sandbox.localhost URL.
Logs
Use Babai logs through the host agent to inspect build, runtime, and gateway logs. Secret values are never returned in API, MCP, or tool responses.
Failures
Build and runtime failures return structured diagnostics. The host agent reads logs, edits source, re-uploads, and retries within the iteration budget.
MVP Limits
- 3 concurrent live sandboxes per user
- 7-day sandbox TTL with redeploy to refresh
- 30 deploy attempts per rolling 24-hour window
- 100 MB source zip upload cap
- 512 MiB memory, 1 CPU, max 1 Cloud Run instance
- 10 GB egress per sandbox per week
MVP Non-goals
- Full app-management dashboard
- Billing, INR pricing, or GST invoicing
- Custom domains or vanity subdomains
- Managed Postgres, Redis, S3, or other dependencies
- Server-side LLM auto-fix pipeline
- Firecracker runtime