Skip to content

Model Providers

Nightly only for now. The AI features these settings configure ship in the nightly builds and the next npm release.

Run and Check share one AI configuration. Each invocation still starts a fresh conversation.

SettingEnvironment variable
ProviderVIBIUM_AI_PROVIDER
ModelVIBIUM_AI_MODEL
Optional API base URLVIBIUM_AI_BASE_URL
Optional reasoning effortVIBIUM_AI_REASONING_EFFORT

Supported providers, with their credentials:

ProviderCredentialDefault API base URL
openaiOPENAI_API_KEY, requiredhttps://api.openai.com/v1
xaiXAI_API_KEY, or a signed-in Grok CLI sessionhttps://api.x.ai/v1
anthropicANTHROPIC_API_KEY, requiredhttps://api.anthropic.com/v1
googleGOOGLE_API_KEY, or GEMINI_API_KEYhttps://generativelanguage.googleapis.com/v1beta
openai-compatibleOPENAI_API_KEY, optionalExplicit base URL required
localOPENAI_API_KEY, optionalhttp://127.0.0.1:8080/v1

local targets an OpenAI-compatible server you already run on localhost; it does not download or launch a model server. Reasoning-effort settings apply to OpenAI, xAI, and compatible endpoints; leave them unset for Anthropic and Google.

When XAI_API_KEY is unset, Vibium reuses a signed-in Grok CLI session (read-only — it never refreshes or rewrites that login).

vibium setup prompts for these values and writes ~/.config/vibium/ai.env (mode 0600, previous copy kept as .bak). vibium config init writes the same file as a commented template without prompting. On each command, Vibium loads that file for AI variables that are empty in the environment; a nonempty process environment always wins. Set VIBIUM_LOAD_AI_ENV=0 to skip loading.

Confirm the configuration with:

Terminal window
vibium ready ai

It lists missing settings and tests the provider’s model and tool support with at most two small requests. Exit 0 means ready.

Run, Check, and ready ai accept the same overrides, which apply to that invocation only:

CLI flagJS / MCP / Java optionPython keyword
--providerproviderprovider
--modelmodelmodel
--ai-base-urlaiBaseURLai_base_url
--reasoning-effortreasoningEffortreasoning_effort
Terminal window
vibium run "change my timezone and save it" --provider anthropic --model your-claude-model
vibium check "the timezone persists after reload" --provider google --model your-gemini-model

When the provider changes, supply the model explicitly; Vibium clears the old provider’s model, endpoint, and effort before applying your options. Credentials always come from the provider’s environment variable — there is no API-key flag.

Renamed flag: --base-url used to mean the AI endpoint. It now names the site under test for Run and Check; the AI endpoint is --ai-base-url.

The CLI reads settings on each call. SDK and MCP processes read their environment at startup — restart them after changing environment defaults. Per-call overrides take effect immediately either way.