What is Agent MCP vs Container MCP?
The hosted broker versus the per-project executor. Agent MCP coordinates across projects; container MCP acts inside one workspace with its credentials and files.
Related terms
Model Context Protocol (MCP)
The open standard connecting agents to tools: initialize, list tools, call, read resources, ping. MCP turns chat models into operators with real capabilities.
MCP stdio Bridge
Running the BYOB CLI as a standard MCP server over stdio so Claude Code, Codex, and other clients attach directly. One command turns the workspace into tools any agent can call.
BYOB CLI
The command-line companion for BYOB projects: workspace status, deploys, database, storage, auth, email, analytics, git, and DNS from the terminal. The bridge between chat-built apps and local agent workflows.
Svelte Runes
The `$state`, `$derived`, `$effect`, and `$props` primitives powering Svelte 5 reactivity. Runes are mandatory in generated code: explicit, compilable, and consistent across every component.
File-Based Routing
Pages defined by file location: `+page.svelte` renders, `+layout.svelte` wraps, `+server.js` serves data. The route tree is the app map — no separate router config to drift.
Load Function
Server-side data loading for a route before it renders. Load on the server for content crawlers and users need immediately; reach for client fetching only for interactive extras.