Configuration
Model providers, credential storage, and the directories Vibes uses.
Provider resolution
The API selects the first configured provider in this order:
AI_GATEWAY_API_KEYZHIPU_API_KEYOPENAI_API_KEYOPENROUTER_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
OPENAI_API_KEY=your-provider-key
PORT=3000
NODE_ENV=development
SKILLS_DIR=./skillsFor development, place configuration in a local .env file. The launcher also accepts environment variables and stored credentials. Keep credentials out of source control.
| Variable | Purpose |
|---|---|
VIBES_HOME | Override the launcher’s runtime-data directory. |
SKILLS_DIR | Optional directory for discoverable skills. |
EXA_API_KEY | Enable Exa web search. |
TAVILY_API_KEY | Enable Tavily web search. |
BRAVE_API_KEY | Enable 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.