# Vibestrate > Vibestrate is an open-source, local-first AI coding environment that gives > developers CTO-style supervision (a "supervisor" sitting above the crew) of a > flexible set of models. It drives Claude Code, Codex, Gemini, OpenCode, Aider, > Cursor CLI, Amp, Goose, Crush, Qwen Code, and local models (Ollama, LM Studio, > llama.cpp) through reusable flows with human approval gates, shared flow > recipes, per-phase model swaps, and a full token / cost / decision ledger. You pay only for the AI models you choose to run with your own keys. Vibestrate itself never charges, never proxies your code through a hosted service, and never phones home. ## Core positioning Vibestrate is for developers who do not want to bet their whole workflow on one model, one chat, or one vendor. If Claude Code, Codex, Gemini, or another provider becomes unavailable, too expensive, or wrong for a phase, the flow stays intact and the crew can be swapped. The product metaphor is "your AI CTO": not an autonomous black box, but a supervision layer that plans the work, seats the right model in each phase, stops at approval gates, logs what happened, and keeps the human in charge. ## Privacy guarantees (auditable in the source) - **Your API keys never touch Vibestrate.** Anthropic / OpenAI / Google / Ollama credentials live in the respective vendor CLIs that already had them. Vibestrate spawns those CLIs as child processes and reads their stdout - it is not in the middle of any model call. - **No model proxy.** Prompts and responses travel directly between the vendor CLI and the vendor's servers. Vibestrate does not see, log, store, or forward any of it. - **The ledger (tokens, costs, durations) is a local estimate.** Computed on your machine from CLI output and locally cached public-pricing tables. It is not authoritative billing data; the vendor's own dashboard is. It is good for budgeting on your machine. - **No telemetry to Vibestrate, ever.** No phone-home, no relay, no update check. (An optional OpenTelemetry export of a run's metrics to *your own* collector exists - opt-in and off by default.) Ledger entries are saved to a local SQLite file in your Vibestrate data directory - not synced, uploaded, or aggregated to any server. - **The marketing site uses cookieless aggregate page-view analytics only** (Cloudflare Web Analytics). The software itself collects nothing. ## What Vibestrate is for Vibestrate is for software engineers who want one chat-with-an-LLM replaced by a *supervised* multi-agent workflow. It targets real work - refactors, migrations, end-to-end features - where: - Multiple models contribute (a planner, an arbiter, an executor, a reviewer, a verifier) - Models can be swapped when one vendor is unavailable, overpriced, or weak for a phase - Phases are explicit and visible (no hidden "agent loop") - Humans approve at the gates that matter - Flows are reusable, shareable, and forkable - Tokens, dollars, and decisions are recorded and replayable It is **not** a hosted SaaS, not a cloud relay, not an "agent framework" library you have to learn. It is a single local process you run, plus a CLI, a TUI, and a tiny local web dashboard ("Mission Control"). ## Supported providers Vibestrate detects and auto-configures eleven built-in providers, and any CLI tool that streams structured output can be added: - **Claude Code** (Anthropic) - **Codex** (OpenAI) - **Gemini CLI** (Google) - **OpenCode** - **Aider** - **Cursor CLI** - **Amp** - **Goose** - **Crush** - **Qwen Code** - **Ollama** and other local runtimes (LM Studio, llama.cpp) over a localhost proxy, so nothing leaves your machine and no key is needed A crew can mix frontier models, cheaper models, and fully local models in one flow, with a different seat per phase. ## Architecture - **Orchestrator** - a single local Node process (no daemon, no cloud); manages a sandboxed git worktree per run - **Providers** - thin adapters over CLI tools you already have installed (claude, codex, gemini, opencode, aider, cursor, amp, goose, crush, qwen, ollama, etc.) - **Flows** - YAML recipes that define a run: phases, roles, approval gates, validators - **Mission Control** - local web UI for live phase rail, terminal stream, diff inspector, ledger - **CLI** - `vibe init`, `vibe doctor`, `vibe run`, `vibe status`, `vibe ui`, `vibe approvals approve`, `vibe ledger`, scriptable end-to-end ## Key pages - [What is Vibestrate?](https://vibestrate.com/what-is-vibestrate/): the official, citable answer for search and AI systems - [How it works](https://vibestrate.com/how-it-works/): Brief, Flow, Crew, Run end to end - [Model independence](https://vibestrate.com/model-independence/): why swappable crews reduce single-vendor risk - [Flow hub](https://vibestrate.com/hub/): browse, pull, and publish reusable flows (verified + community) - [Shared flows](https://vibestrate.com/shared-flows/): how reusable flow recipes work - [Vibestrate vs one AI chat](https://vibestrate.com/compare/one-chat/): supervised flows compared with a single model conversation - [Vibestrate vs agent frameworks](https://vibestrate.com/compare/agent-frameworks/): productized supervision compared with building your own framework - [Open-source AI coding tools compared](https://vibestrate.com/compare/open-source-ai-coding/): honest feature comparison vs Vibe Kanban, OpenHands, Claude Squad, Open SWE, Aider, and Plandex - [Aider alternative](https://vibestrate.com/alternatives/aider/): how Vibestrate compares with, and runs, Aider - [Cline alternative](https://vibestrate.com/alternatives/cline/): supervised terminal flows vs an in-editor agent - [Homepage](https://vibestrate.com/): positioning and the scripted product demo - [Pricing](https://vibestrate.com/pricing.md): free, Apache 2.0 - [Security](https://vibestrate.com/security): responsible disclosure (best effort, GitHub-only) - [Privacy](https://vibestrate.com/privacy): cookieless aggregate analytics, nothing else - [License](https://vibestrate.com/license): Apache 2.0 for the software, "all rights reserved" for the marketing site ## Documentation Vibestrate's full documentation lives at `/docs`. Reference pages (CLI commands, config schema, providers, workflow stages, run-state machine, and agent roles) are generated from the live vibestrate repository, so they never drift from the code. Concept and workflow pages are handwritten in a plain, two-layer ("professional + simple") voice. A flat, always-current index of every documentation URL is at . ### Start here - [Docs home](https://vibestrate.com/docs/): what Vibestrate is, reading paths - [Installation](https://vibestrate.com/docs/getting-started/installation/) - [Your first run](https://vibestrate.com/docs/getting-started/first-run/) - [Set up a provider](https://vibestrate.com/docs/getting-started/providers/) - [Attach skills](https://vibestrate.com/docs/getting-started/skills/) ### Core concepts - [Supervisor](https://vibestrate.com/docs/concepts/supervisor/) - [Flow](https://vibestrate.com/docs/concepts/flow/) - [Crew](https://vibestrate.com/docs/concepts/crew/) - [Role](https://vibestrate.com/docs/concepts/role/) and [Seat](https://vibestrate.com/docs/concepts/seat/) - [Provider](https://vibestrate.com/docs/concepts/provider/) - [Workflow](https://vibestrate.com/docs/concepts/workflow/) - [Worktree](https://vibestrate.com/docs/concepts/worktree/) - [Run state](https://vibestrate.com/docs/concepts/state/) ### Reference (regenerated from vibestrate's code) - [CLI commands](https://vibestrate.com/docs/reference/cli/) - [Config reference](https://vibestrate.com/docs/reference/config/) - [Providers](https://vibestrate.com/docs/reference/providers/) - [Workflow stages](https://vibestrate.com/docs/reference/workflow/) - [Run states](https://vibestrate.com/docs/reference/state-machine/) - [Agent roles](https://vibestrate.com/docs/reference/agents/) For workflows, extending, architecture, troubleshooting, and the glossary, see the complete index at . ## Contact All contact and contributions happen on GitHub: . There is no email address, no Slack, no Discord, no support portal. ## Install ``` # macOS, Linux, WSL - install script (recommended) curl -fsSL get.vibestrate.com | sh # or via npm npm install -g vibestrate ``` After install, point Vibestrate at a git repo and start a run: ``` vibe init # scaffold .vibestrate/ - touches nothing else vibe doctor --fix # detect and wire up the provider CLIs you already have vibe run "Add a /healthz endpoint" # add --ui to open Mission Control ``` ## Project status Vibestrate is free and open source (Apache 2.0), built and maintained by [Guy Shonshon](https://shonshon.com). It runs entirely on your own machine, never proxies your code, and collects no telemetry. It is provided as-is and supported through GitHub - there is no paid tier, no commercial support contract, and no SLA. The marketing-site source and content are © Guy Shonshon, all rights reserved. ## License - Vibestrate software: Apache 2.0. - This marketing site source and content: © Guy Shonshon, all rights reserved. Last reviewed: 2026-06-18.