Configuration
DOCS / START HERE

Configuration

Model providers, credential storage, and the directories Vibes uses.

Provider resolution

The API selects the first configured provider in this order:

  1. AI_GATEWAY_API_KEY
  2. ZHIPU_API_KEY
  3. OPENAI_API_KEY
  4. OPENROUTER_API_KEY

Model availability and defaults are defined in apps/api/src/model-factory.ts. If you have several keys configured, account for this order when troubleshooting model selection.

Environment variables

env
OPENAI_API_KEY=your-provider-key
PORT=3000
NODE_ENV=development
SKILLS_DIR=./skills

For development, place configuration in a local .env file. The launcher also accepts environment variables and stored credentials. Keep credentials out of source control.

VariablePurpose
VIBES_HOMEOverride the launcher’s runtime-data directory.
SKILLS_DIROptional directory for discoverable skills.
EXA_API_KEYEnable Exa web search.
TAVILY_API_KEYEnable Tavily web search.
BRAVE_API_KEYEnable Brave web search.

Where credentials live

Vibes attempts to use the OS keychain: Keychain on macOS, Credential Manager on Windows, and Secret Service on supported Linux desktops. Where this is unavailable, it falls back to AES-256-GCM encrypted credentials in ~/.vibes/credentials.json.

The fallback uses CREDENTIAL_ENCRYPTION_KEY when configured, otherwise a locally generated key file. Since that key can live beside the encrypted file, this fallback does not protect against an attacker who can read both. Environment variables are useful for CI because nothing needs to be stored.

Runtime state

Launching vibes keeps runtime data under ~/.vibes/ by default. Direct API development uses the configured workspace paths. Sessions persist in SQLite and have their own agent instance and state. Shared memories are separate from the session scratchpad.

Improve this page Grounded in the Vibes source.

Find a guide, command, or concept.