# baro - [Introduction](/docs): baro is an autonomous software factory — it compiles a goal into a contract, builds it with parallel agents, and blocks every merge behind machine gates. - **Getting started** - [Installation](/docs/installation): Install baro from npm. Verify your chosen LLM provider (Claude Code or OpenAI) is set up. - [Quickstart](/docs/quickstart): Run baro end-to-end on a small refactor and walk away. - **Running** - [Running baro](/docs/running): The CLI reference — foreground and background runs, following a run from anywhere, resume vs continue, and the flags that shape a run. - [Execution modes](/docs/execution-modes): baro classifies every goal as focused, sequential, or parallel — before the first agent spawns — and enforces the decision in code. - [Quick mode](/docs/quick-mode): A surgical fast path for trivial goals — typo fixes, renames, version bumps, single-file edits. - [The TUI](/docs/tui): A terminal workbench for your agent fleet — live signals, a dependency-graph view, and mid-run chat with any agent. - **Models** - [LLM providers](/docs/llm-providers): Claude Code, Codex CLI, native OpenAI (or any OpenAI-compatible endpoint), a hybrid preset, and per-story tier routing. Same DAG, same orchestration — the transport is your choice. - **How it works** - [How it works](/docs/how-it-works): Two processes, a mozaik event bus, bounded contexts, and an anti-corruption layer in front of every model — the architecture behind a run. - [Verification & gates](/docs/verification): What stands between an agent's diff and your branch — the contract, the gates, the evidence critic, and the rules they all obey. - **Cloud** - [Run from the cloud — baro connect](/docs/connect): Pair a machine as a remote runner. Fire goals from a dashboard, a teammate, or a GitHub issue — they run on your machine over your own subscription, code never leaving it. - [baro's cloud — hosted runs](/docs/cloud): No machine or subscription? Run a goal entirely on baro's cloud — an isolated sandbox on our infrastructure, billed from prepaid credits. - **Help** - [Troubleshooting](/docs/troubleshooting): How to diagnose a failed baro run — start with `baro --doctor`, then check the persisted log files.