Point it at your warehouse and your codebase alike. It grounds in your real schema and dbt lineage before writing a line, races N parallel agents on every task, and an outcome-aware gate rejects the dangerous actions · even in full-auto. Your credentials never leave your machine.
The CLI is free. No subscription, no seat fees, no markup. Bring your own key and pay your model provider directly, at cost · your code never leaves your machine.
One binary sits between your stack and the work you ship. Every task is grounded in the real schema and repo, raced by parallel agents, gated by an outcome check, and verified before it may call itself done.
repo · branches · tests · git is the undo
Postgres · Snowflake · BigQuery · Databricks +11 more
dbt · Airflow · Bonacci Studio · any MCP server
real schema · dbt lineage · recalled memory · no hallucinated columns
code & SQL in isolated git worktrees · any model, your key
predicts consequences · proceed / defer / reject · cost preview on writes
build · tests · dbt run · can't declare "done" on broken work
a synthesis pass names the winner · land merges it
cost-previewed writes, executed credential-local
outcomes remembered · recall improves every run
It introspects the real schema and reads your dbt lineage before touching anything, runs SQL across 15 connectors, and keeps your credentials on your machine.
Exact columns/types + dbt catalog & lineage injected before generating · it answers "what breaks if I rename customer_id?" before touching anything.
SQL across Postgres, Snowflake, BigQuery, Redshift, Databricks & more · opt-in per connection, cost-previewed by EXPLAIN, gated by the forward check.
A runner embedded in the CLI executes against your warehouse locally; the cloud orchestrates the work but holds zero credentials.
manifest.json for grounding & blast-radius; runs dbt build/run/test to materialize models.compare_tables verifies rows & schema · a parity check it can't fake./connect airflow brings Apache Airflow in as tools · list / trigger / inspect DAG runs.Agents are non-deterministic · run the same prompt twice, get two different results. Betting a task on one run is a coin flip. So don't: N agents race the same task in isolated git worktrees, a synthesis pass names the winner, you merge it.
run --agents 4 "…" launches four agents on one prompt · each in a physically separate git worktree, never colliding. Each agent can run a different model: --mix auto-distributes your providers (a bake-off), --models assigns them explicitly, or the /fleet wizard picks per agent.land vibecodecli/… from the shell) and the winner's commits merge into your branch. Git is your undo.Every other agent starts each session blank. With the ThinkingMemory backbone, vibeCodeCLI auto-recalls relevant past facts, decisions, and outcomes · a code decision or a data incident alike · into every turn, and auto-remembers what happened. The more it runs, the sharper it gets.
base_url at localhost to self-host. Unconfigured? A silent no-op.An LLM predicts tokens, not consequences. Before any irreversible action, a forward check predicts the outcome and decides · proceed, defer, or reject · even in full-auto.
careful · auto · full-auto · risky calls prompt with what they predict, not just the command.DROP TABLE, terraform destroy, kubectl delete, mutating MCP tools · same forward check.0600 file · cloud-memory writes are redacted first · a cloned repo's config can't run code until you trust it.Straight talk on local models. Self-hosted Ollama works end-to-end, but small models have a real quality ceiling · pick a proper tool-calling model (qwen3, llama3.3; ~14B is the floor). For serious work, point it at a frontier model via BYOK. Details in the docs →
Run it bare for a persistent session · pinned input, status bar, inline diffs, 30+ slash-commands. Under the hood: repo map on start, MCP servers, pre/post_tool_use hooks, an explore subagent, a thrash guard, decorrelated review, prompt caching.
Hosted memory database with a ranked, cited recall primitive. Free tier included.
15 connectors, the runner, and the workspace MCP server behind /connect tl.
Build Kafka / Spark / SQL pipelines on a canvas · then drive the whole account via /connect studio.
One line to install, one menu to add a key, one command to ship. No build step, no Rust toolchain · a single static binary for macOS & Linux.
PATH.“spun it up over the weekend and the parallel worktrees thing actually held up on a messy refactor, memory carried across sessions which was a nice surprise”
Metehan · on Product Hunt
Built in Rust by ThinkingDBx. Questions or feedback? [email protected] →