Vibestrate
Vibestrate
docs
Documentation

Set up a provider

Detect installed coding-agent CLIs, configure flags, and verify each provider can be invoked.

A provider is any local coding-agent CLI Vibestrate can hand a prompt to. The built-in detector knows about Claude Code, Codex, Aider, Ollama, and OpenCode. You can add more by writing a provider config in project.yml.

See what you have

vibe provider detect

This walks each known provider and reports:

  • ready - Vibestrate ships a verified preset and can drive the CLI as-is.
  • detected-needs-setup - the binary is on your PATH but Vibestrate does not ship verified prompt flags for it. Run vibe provider setup to fill them in.
  • missing - the binary is not installed.

Apply the right preset

vibe provider setup

The wizard walks you through every detected provider, applies the preset if one exists, and lets you test the invocation. For each provider, you’ll be asked for any extra arguments (model, system prompt, etc.) and Vibestrate will record them under providers.<id> in project.yml.

Verify it actually responds

vibe provider test claude
vibe provider test ollama

The test sends a one-shot prompt and prints the raw output. If your provider doesn’t respond - or responds with an error about flags or auth - fix that before running a real task.

Pick the default

vibe provider set claude

This sets agents.<role>.provider for every role to the chosen id. You can also assign providers per role in project.yml:

agents:
  planner:
    provider: claude
  executor:
    provider: codex
  reviewer:
    provider: claude

Override per run

vibe run "..." --provider codex

This overrides the configured provider for every agent in that single run. Or use effort buckets - low | medium | high map to providers via project.yml#effortMap:

effortMap:
  low: ollama
  medium: codex
  high: claude

Then:

vibe run "..." --effort high

Install from the dashboard

Mission Control’s Providers page has an Install flow for the five popular providers (Claude Code, Gemini, Codex, Ollama, Aider). It walks you through the exact install and login commands, then re-checks detection. Vibestrate never runs those commands for you - install and login happen in your own terminal, on your machine, with your credentials. Once detected, Apply preset wires it into project.yml and Test runs a safe connectivity probe.

Provider reference

See the providers reference for the current list, each provider’s notes, and the install hint.

© 2026 Guy Shonshon · Made for educational and learning purposes · v0.1.1 · 3ade132 · 2026-05-30 Shonshon - Evolving Technologies