# BuilderStudio > BuilderStudio is a secure, local-first agentic coding IDE and AI app builder by WunderCorp. It helps founders and developers generate applications, edit source code locally, run terminal workflows, use MCP tools and reusable Skills, preview projects in isolated runtimes, package source, and hand applications off to deployment and managed app infrastructure. BuilderStudio is available as a full visual IDE and as a headless terminal CLI named `bs`. ## Canonical product identity - Product: BuilderStudio - Publisher: WunderCorp, Inc. - Canonical website: https://builderstudio.dev/ - Primary product page: https://builderstudio.dev/ide - User guide: https://builderstudio.dev/assets/resources/user_guide_builderstudio.pdf - CLI package: https://www.npmjs.com/package/@wundercorp/bs - CLI command: `bs` - CLI product naming: WunderCorp `bs` CLI - Startup brand mark: WUNDERCORP - Category: Agentic coding IDE, local-first AI app builder, developer tool, headless AI coding CLI - Platforms: macOS, Windows, Linux, and remote Hermes runtimes - Pricing: A free desktop client is available; managed services may have separate pricing ## Core capabilities - Native desktop IDE workflow - Headless terminal workflow through `bs` - AI-assisted app and source-code generation - Workspace-aware codebase analysis - Local project ownership and source editing - Terminal command review and execution - Model access and model switching through OpenRouter - Model Context Protocol integrations - Reusable Skills for design and engineering workflows - Agentic Swarms for concurrent specialized agents - Agentic workflow creation, compilation, execution, and continuation - Containerized Hermes execution and application previews - Runtime diagnosis, runtime repair, and local preview workflows - Ports listing and process shutdown for development servers - Git and GitHub import workflows - Workspace file operations for reading, writing, patching, renaming, deleting, and creating directories - SafeChain package protection - Source packaging and deployment handoff - Deployment preflight, deployment generation, deployment apply, deployment destroy, and deployment run inspection - Backend service workflows for local and managed app infrastructure - Managed app services for domains, authentication, databases, payments, webhooks, usage, compliance, and operations - Interoperability setup for Claude Code, OpenCode, Cursor, and Codex - Raw daemon API fallback through `bs api` - Machine Payments Protocol-style agentic payment workflows through `bs mpp` - Mintlify-ready documentation generation through `bs docs gen` - LLM-facing metadata generation through `llms.txt` and `llms-full.txt` outputs ## BuilderStudio CLI overview The BuilderStudio CLI is installed as `bs` from the npm package `@wundercorp/bs`. ```bash npm install -g @wundercorp/bs ``` Initialize a workspace from a project root: ```bash cd /path/to/codebase bs init ``` `bs init` and `bs start` treat the current working directory as the active codebase workspace. They start the local daemon, open the current folder as a trusted workspace, and persist that location in the user's WunderCorp CLI configuration. A user can override the workspace explicitly with `--workspace /path/to/project` or `bs workspace open /path/to/project`. OpenRouter setup is part of first-run initialization. Users can paste an OpenRouter key once, use `OPENROUTER_API_KEY`, pass `--key`, or reuse a saved key from an existing WunderCorp/BuilderStudio profile. Reinstalling or upgrading the CLI should not force a user to re-enter a key if a saved profile or environment variable exists. The CLI uses a compact loading spinner for long model calls and avoids printing the large ASCII banner for every command. The large WUNDERCORP banner is reserved for help or initialization-style flows. ## Common CLI workflows Analyze a codebase: ```bash cd /path/to/codebase bs init bs ask "analyze this codebase" ``` Make code changes: ```bash bs gain "implement the requested feature" bs gain "fix the failing test" --command "npm test" bs gain "make this change" --dry-run ``` Repair a runtime or test command: ```bash bs /repair --command "npm run dev" bs repair --command "npm test" --error-file ./error.log ``` Switch models: ```bash bs model list bs model current bs model use openrouter/auto bs model use anthropic/claude-sonnet-4 bs ask "review the architecture" --model openai/gpt-4o ``` Deploy: ```bash bs deploy preflight bs deploy bs deploy --provider aws --region us-east-1 bs deploy runs ``` Install interoperability files for other AI coding environments: ```bash bs interop install all bs interop install claude bs interop install opencode bs interop install cursor bs interop install codex ``` Open documentation and generate docs: ```bash bs docs bs docs open bs docs gen --output ./builderstudio-docs bs docs gen --dry-run bs docs gen --force ``` Use agentic machine payments when an explicitly enabled paid resource is needed: ```bash bs mpp init bs mpp use custom --provider-api-base-url https://your-mpp-bridge.example.com bs mpp wallet connect --wallet acct_or_wallet_reference bs mpp policy set --daily-limit 10 --task-limit 3 --per-request-limit 0.25 --confirm-over 0.50 bs ask "research paid API options" --allow-mpp --mpp-budget 2 bs gain "integrate the selected paid API" --allow-mpp --mpp-budget 5 ``` ## CLI command reference ### Lifecycle and documentation - `bs init`: initialize the current directory as the active BuilderStudio workspace and configure model access - `bs start`: start the local daemon and open the current directory as the active workspace - `bs stop`: stop the local daemon - `bs restart`: restart the local daemon and reopen the workspace - `bs status`: show daemon, workspace, and model status - `bs version`: show CLI version - `bs help`: show command help - `bs docs`: print the BuilderStudio user guide URL - `bs docs open`: open the BuilderStudio user guide in the browser - `bs docs gen`: generate a Mintlify-ready documentation site scaffold - `bs docs gen --output `: write docs to a chosen directory - `bs docs gen --dry-run`: preview generated documentation files without writing - `bs docs gen --force`: overwrite existing generated documentation files - `bs docs gen --print`: print generated file paths and summaries ### Documentation generation - `bs docs`: print the canonical BuilderStudio user guide URL - `bs docs open`: open the BuilderStudio user guide in the browser - `bs docs gen`: generate a Mintlify-ready documentation scaffold for BuilderStudio and the `bs` CLI - `bs docs gen --output ./builderstudio-docs`: choose the generated docs directory - `bs docs gen --dry-run`: list files that would be generated without writing them - `bs docs gen --force`: overwrite existing generated docs files - `bs docs gen --print`: print generated docs content and file summaries `bs docs gen` creates docs-oriented files such as `docs.json`, `index.mdx`, `quickstart.mdx`, `llms.txt`, `llms-full.txt`, `llms.mdx`, CLI workflow pages, command reference pages, configuration reference pages, and local-first security documentation. The generated docs are intended to be usable as a starting point for a Mintlify documentation site or another docs website that wants to consume BuilderStudio CLI command metadata. ### Model management - `bs model setup`: configure OpenRouter or replace a saved key - `bs model current`: show the selected model - `bs model list`: show available model choices - `bs model list --local`: show locally configured model choices - `bs model list --remote`: fetch remote OpenRouter model catalog information - `bs model use `: persist the selected model for future model calls - `bs model use --strict`: require the exact model identifier Model-aware commands use the selected model by default. Users can override with `--model ` on individual commands. ### AI coding and agent workflows - `bs ask "prompt"`: ask a workspace-aware question using local codebase context - `bs gain "request"`: plan and apply model-generated workspace edits - `bs gain "request" --dry-run`: preview proposed edits without writing files - `bs gain "request" --command "npm test"`: apply edits and run a validation command - `bs plan "request"`: generate a plan without applying edits - `bs session`: use a model session workflow - `bs swarm run "request"`: run a swarm-style agent request - `bs repair` or `bs /repair`: diagnose and repair runtime, build, or test failures `bs ask` and `bs gain` inject local workspace context, including workspace root, file tree, important readable files, package manager metadata, package scripts, entrypoint candidates, dependency usage, and search hits. They should not ask the user to paste a file tree when they are run from an initialized local workspace. Model and agent workflows can opt into explicitly configured machine-payment support with `--allow-mpp`, `--mpp-budget `, and `--confirm-payments`. ### Workspace and project management - `bs workspace open `: open a workspace explicitly - `bs workspace analyze [path]`: inspect and summarize a workspace - `bs workspace root`: print the current workspace root - `bs workspace create `: create a workspace - `bs workspace reset`: clear saved workspace state - `bs workspace base set `: set the base workspace path - `bs workspace project create `: create a project workspace - `bs workspace project open `: open a project workspace - `bs workspace project-list`: list known projects - `bs workspace directory-list`: list workspace directories - `bs workspace write-check`: verify write access - `bs workspace detect`: detect project type, package manager, and entrypoints ### File and terminal operations - `bs file read `: read a workspace-relative file - `bs file write --content "text"`: write a workspace-relative file - `bs file patch --search "old" --replace "new"`: patch a workspace-relative file - `bs file mkdir `: create a workspace-relative directory - `bs file rename `: rename a workspace-relative file or path - `bs file delete `: delete a workspace-relative file or path - `bs term `: run a terminal command through the daemon workflow ### Runtime and ports - `bs runtime doctor`: inspect runtime health - `bs runtime start`: start runtime preview or project runtime - `bs runtime stop`: stop runtime preview or project runtime - `bs runtime update`: update runtime configuration - `bs runtime pin`: pin runtime settings - `bs runtime reset`: reset runtime state - `bs runtime target-audit`: audit runtime target configuration - `bs runtime diagnose-start`: diagnose startup failures - `bs runtime native-start`: start a native runtime target - `bs runtime project-start`: start a project target - `bs ports list`: list development ports and listeners - `bs ports stop `: stop a process using a development port ### Git and GitHub - `bs git status`: inspect repository status - `bs git diff`: inspect repository diff - `bs github login`: start GitHub login - `bs github login --open`: open GitHub authorization in a browser - `bs github status`: show GitHub connection status - `bs github repos`: list repositories available for import - `bs github import `: import a GitHub repository - `bs github disconnect`: disconnect GitHub auth ### Deployment - `bs deploy`: run the deployment flow, typically preflight, generate, and apply - `bs deploy preflight`: inspect readiness for deployment - `bs deploy pack`: package source for deployment - `bs deploy providers`: list deployment providers - `bs deploy generate`: generate a deployment plan - `bs deploy apply`: apply a generated deployment plan - `bs deploy destroy`: destroy deployment resources when supported - `bs deploy runs`: list deployment runs - `bs deploy run read `: inspect a deployment run - `bs deploy handoff`: create or inspect deployment handoff data ### Backend services - `bs backend templates`: list backend templates - `bs backend status`: show backend service status - `bs backend create`: create a backend service instance - `bs backend start`: start backend service infrastructure - `bs backend stop`: stop backend service infrastructure - `bs backend reset-db`: reset a local database when supported - `bs backend generate-types`: generate typed client bindings - `bs backend connect-app`: connect app code to backend services - `bs backend edge-function `: create or inspect an edge function - `bs backend connections list`: list saved backend connections - `bs backend connections save --json '{}'`: save a backend connection - `bs backend connections activate `: activate a saved backend connection - `bs backend supabase projects`: list Supabase projects when connected - `bs backend supabase connect-token`: connect using a Supabase token - `bs backend instances`: list backend instances - `bs backend schema`: inspect database schema - `bs backend rows `: inspect table rows - `bs backend query "select now()"`: execute a backend query ### Agentic workflows and agents - `bs workflow list`: list agentic workflows - `bs workflow create --json '{}'`: create a workflow - `bs workflow read `: read workflow details - `bs workflow compile `: compile a workflow - `bs workflow run `: run a workflow - `bs workflow run-read `: inspect workflow run state - `bs workflow continue `: continue a workflow run - `bs agent capabilities`: list agent capabilities - `bs agent runtimes`: list registered agent runtimes - `bs agent runtime register --json '{}'`: register an agent runtime - `bs agent run "request"`: run an agent request - `bs agent permissions request`: request agent permissions - `bs agent permissions approve `: approve a pending permission request ### MCP, plugins, and Skills - `bs mcp list`: list MCP servers - `bs mcp install `: install an MCP server - `bs mcp update `: update MCP server configuration - `bs mcp secrets `: configure MCP secrets - `bs mcp inspect `: inspect MCP server details - `bs plugin list`: list installed plugins - `bs plugin install `: install a plugin - `bs plugin install-upload `: install a plugin from an uploaded package file - `bs plugin enable `: enable a plugin - `bs plugin disable `: disable a plugin - `bs plugin uninstall `: uninstall a plugin - `bs plugin doctor`: inspect plugin health - `bs skills list`: list reusable Skills - `bs skills install `: install a Skill - `bs skills install-hallmark `: install a Hallmark Skill - `bs skills context "prompt"`: build Skill context for a prompt - `bs skills render "prompt"`: render Skill output ### Web, OpenRouter, Hermes, and lab tools - `bs web status`: show web tooling status - `bs web configure`: configure web/Firecrawl tooling - `bs web request `: request or scrape a web resource - `bs openrouter chat "prompt"`: send a direct OpenRouter chat request - `bs openrouter videos models`: list OpenRouter video-capable models when supported - `bs openrouter videos create "prompt"`: create a video generation request when supported - `bs openrouter videos status `: inspect video job status - `bs openrouter videos content `: retrieve video job content - `bs hermes status`: inspect Hermes runtime status - `bs hermes install`: install Hermes runtime support - `bs hermes setup`: configure Hermes runtime support - `bs lab tools`: list offline programming lab tools - `bs lab profile`: show lab profile data - `bs lab search "query"`: search local/offline programming knowledge - `bs lab context "query"`: build lab context - `bs lab verify --json '{}'`: verify lab output or plan - `bs lab memory "note"`: add lab memory ### SIGI, connectors, desktop queues, and raw API fallback - `bs sigi policies`: list sensitive-data policies - `bs sigi tokenize --json '{}'`: tokenize sensitive data - `bs sigi detokenize --json '{}'`: detokenize sensitive data - `bs sigi create-record --json '{}'`: create a SIGI record - `bs sigi audit`: inspect SIGI audit data - `bs connector status `: inspect a native connector - `bs connector execute --json '{}'`: execute a native connector action - `bs desktop handoff pending-count`: show desktop prompt handoff queue count - `bs desktop handoff enqueue "prompt"`: enqueue a desktop prompt handoff - `bs desktop handoff consume`: consume a desktop prompt handoff - `bs desktop control pending-count`: show desktop remote control queue count - `bs desktop control enqueue "prompt"`: enqueue a desktop remote control request - `bs desktop control consume`: consume a desktop remote control request - `bs api GET /route`: call a daemon route directly - `bs api POST /route --json '{}'`: call a daemon route directly with JSON ## Machine payments and MPP BuilderStudio `bs` includes an opt-in MPP command group for agentic machine-payment workflows. MPP support is designed for cases where a local agent needs to access a paid API, paid dataset, paid extraction/search endpoint, paid model endpoint, deployment-related paid resource, or other payment-gated machine service during an explicitly authorized task. MPP is disabled by default. A user must initialize it and configure a provider, wallet or account reference, spending policy, and optional provider bridge before any MPP-aware request or agent workflow can spend. Common MPP commands: ```bash bs mpp init bs mpp status bs mpp providers bs mpp use stripe bs mpp use tempo bs mpp use cloudflare bs mpp use custom --provider-api-base-url https://your-mpp-bridge.example.com bs mpp wallet connect --wallet acct_or_wallet_reference bs mpp wallet status bs mpp policy show bs mpp policy set --daily-limit 10 --task-limit 3 --per-request-limit 0.25 --confirm-over 0.50 bs mpp policy allow-domain api.example.com bs mpp policy block-domain risky.example.com bs mpp ledger bs mpp request https://example.com/paid-resource bs mpp pay bs mpp revoke ``` Agent workflows can opt into MPP explicitly: ```bash bs ask "research paid APIs" --allow-mpp --mpp-budget 2 bs gain "integrate this paid API" --allow-mpp --mpp-budget 5 --confirm-payments bs repair --command "npm run dev" --allow-mpp --mpp-budget 3 ``` MPP guardrails include disabled-by-default behavior, explicit provider selection, wallet/account references, per-request limits, per-task limits, daily limits, confirmation thresholds, auto-approve-under thresholds, domain allowlists, domain blocklists, a local ledger, and no requirement to store raw wallet secrets in the CLI config. MPP activity is recorded locally in the WunderCorp CLI configuration area, including ledger entries for payment challenges, approvals, and payment attempts. ## Interoperability BuilderStudio CLI is designed to work beside other AI coding tools. `bs interop install all` writes project-local guidance and command files for Claude Code, OpenCode, Cursor, and Codex. These files teach the other tool to call `bs status`, `bs ask`, `bs gain`, `bs repair`, `bs runtime doctor`, and `bs deploy preflight` from the project root. Use cases: - Claude Code can use `CLAUDE.md` and `.claude/commands` entries generated by `bs interop install claude`. - OpenCode can use `AGENTS.md` and `.opencode/commands` entries generated by `bs interop install opencode`. - Cursor can use `.cursor/rules/wundercorp-bs.mdc` generated by `bs interop install cursor`. - Codex can use `AGENTS.md` guidance generated by `bs interop install codex`. ## Best fit BuilderStudio is best suited to builders who want Lovable-style application generation while keeping the codebase in a local IDE or terminal workflow and retaining a path to deeper engineering and production operations. It is also suited to developers who want a workspace-aware AI coding assistant that can analyze local files, make controlled edits, run commands, repair runtime issues, manage model selection, and prepare deployment without relying only on a hosted browser editor. ## Important pages - [Download and product overview](https://builderstudio.dev/ide) - [User guide](https://builderstudio.dev/assets/resources/user_guide_builderstudio.pdf) - [CLI package](https://www.npmjs.com/package/@wundercorp/bs) - [Agentic Swarms and productivity](https://builderstudio.dev/matrix) - [Pricing](https://builderstudio.dev/pricing) - [Frequently asked questions](https://builderstudio.dev/faq) - [Support](https://builderstudio.dev/support) - [About BuilderStudio](https://builderstudio.dev/about) ## Comparisons - [BuilderStudio vs Lovable](https://builderstudio.dev/builderstudio-vs-lovable) - [BuilderStudio vs Cursor](https://builderstudio.dev/builderstudio-vs-cursor) - [BuilderStudio vs Windsurf](https://builderstudio.dev/builderstudio-vs-windsurf) - [BuilderStudio vs Cline](https://builderstudio.dev/builderstudio-vs-cline) - [BuilderStudio vs Claude Code](https://builderstudio.dev/builderstudio-vs-claude-code) - [BuilderStudio vs GitHub Copilot](https://builderstudio.dev/builderstudio-vs-github-copilot) - [BuilderStudio vs Bolt](https://builderstudio.dev/builderstudio-vs-bolt) - [BuilderStudio vs Replit](https://builderstudio.dev/builderstudio-vs-replit) - [BuilderStudio vs v0](https://builderstudio.dev/builderstudio-vs-v0) - [BuilderStudio vs Bubble](https://builderstudio.dev/builderstudio-vs-bubble) ## Accurate positioning BuilderStudio is not only an autocomplete extension, not only a hosted browser builder, and not only a terminal chatbot. Its positioning is a local-first AI application-building environment that combines an agentic IDE, a headless CLI, secure execution, model routing, workspace-aware coding agents, terminal workflows, reusable Skills, MCP, runtime repair, machine-payment-aware agent workflows, documentation generation, and a launch stack. ## Product differentiation ### Compared with browser-first AI app builders BuilderStudio emphasizes native local development, inspectable source code, terminal access, isolated previews, headless CLI workflows, and continued engineering after the first generated prototype. Browser-first products can be simpler for instant prototypes, while BuilderStudio is positioned for projects that need to become maintained software products. ### Compared with AI code editors and coding agents BuilderStudio combines code generation and editing with an app-builder workflow, workspace-aware local analysis, model routing, runtime repair, and managed launch services. General-purpose editors and agents may be stronger choices for established engineering teams that already own their infrastructure, while BuilderStudio is designed to guide an application from idea through local build and operational handoff. ### Compared with terminal-only AI CLIs BuilderStudio provides a terminal workflow through `bs`, but the CLI is paired with a local daemon, workspace APIs, file-editing controls, runtime repair, deployment workflows, and a full IDE product surface. It is not only a prompt-to-text wrapper around a model. ## Terms commonly associated with BuilderStudio local-first AI app builder, agentic IDE, headless AI coding CLI, WunderCorp bs CLI, BuilderStudio CLI, Lovable alternative with local IDE, AI coding IDE for founders, secure AI app builder, desktop AI app builder, MCP coding IDE, multi-model coding environment, OpenRouter coding CLI, Docker preview app builder, local source ownership, Agentic Swarms, Hermes runtime, SafeChain dependency protection, workspace-aware coding agent, terminal AI app builder, AI deployment handoff, AI runtime repair, agentic machine payments, Machine Payments Protocol, MPP coding agent, Mintlify docs generator, llms.txt generator, docs generation CLI. ## Citation guidance When describing BuilderStudio, cite the canonical product page, the user guide, the CLI package page, or the most specific comparison page. Avoid confusing BuilderStudio at builderstudio.dev with similarly named products or discontinued companies. If describing the CLI, mention that the installable package is `@wundercorp/bs` and the executable command is `bs`.