[ WHAT IS IT ]
No environment variables, no config files. The CLI auto-configures keys, base URLs, and model settings so every request routes through Bifrost from the first session.
[ KEY FEATURES ]
Set up once, switch agents and models freely. The CLI remembers your configuration across sessions.
Bifrost CLI handles all technical setup automatically, including base URLs, API keys, and model settings. No manual configuration files or environment variables to manage.
AutomaticWork with multiple coding agents simultaneously in a persistent tabbed interface. Switch between sessions, open new tabs, or close existing ones using simple keyboard shortcuts.
Multi-sessionWhen launching Claude Code, Bifrost CLI automatically registers Bifrost's MCP server, making configured tools immediately available without manual setup.
MCP readyVirtual keys are stored securely in your OS keyring (macOS Keychain, Windows Credential Manager, or Linux Secret Service) rather than plaintext files.
OS keyring[ SUPPORTED AGENTS ]
[ GETTING STARTED ]
From zero to coding with enterprise controls in under 60 seconds.
Launch Bifrost CLI with a single npx command. No global installation required. Works with Node.js 18+ and connects to your running Bifrost gateway.
npx -y @maximhq/bifrost-cli
Enter your Bifrost gateway URL (default: localhost:8080), optionally provide a virtual key, and the CLI will fetch available models and configure everything automatically.
# CLI prompts you for: # 1. Gateway URL # 2. Virtual key (optional) # 3. Select agent (Claude Code, etc) # 4. Choose model # 5. Review and launch
Select your preferred coding agent and model through the guided setup. Bifrost CLI installs missing agents via npm automatically and launches your session with full MCP integration.
# Session starts with: # - Tabbed terminal interface # - Activity badges (active/idle status) # - MCP tools auto-registered # - Keyboard shortcuts enabled
[ CLI CAPABILITIES ]
Stay in one terminal, manage multiple agents, and never lose your setup between sessions.
Switch between Claude Code, Codex CLI, Gemini CLI, and Opencode before launching. The CLI remembers your previous selections across sessions.
Securely store and manage virtual keys for different teams or projects. Keys are encrypted in your OS keyring and never touch plaintext files.
Visual indicators show session status at a glance with clear markers for active processing, idle sessions, and alerts that need attention.
Settings stored in ~/.bifrost/config.json include gateway URL, default agent, and model preferences. Use -config flag for custom config paths.
Create isolated git worktrees for Claude Code using the -worktree flag, keeping experimental changes separate from your main branch.
Don't have Claude Code or Codex CLI installed? Bifrost CLI automatically installs missing agents via npm when you select them.
[ ENTERPRISE BENEFITS ]
When coding agents route through Bifrost gateway, platform teams get full observability, security guardrails, and cost controls without disrupting developer workflows.
All coding agent traffic routes through Bifrost gateway, applying guardrails, PII redaction, and content policies transparently.
Access 1000+ models through a single interface. Switch between Anthropic, OpenAI, Google, and more without reconfiguring your agent.
Every request from your coding agents is logged with full metadata including user, team, model, and latency. Export to any observability stack.
[ CLAUDE CODE INTEGRATION ]
Bifrost CLI automatically registers the MCP server when launching Claude Code. All tools configured in your Bifrost gateway become immediately available.
All Claude Code traffic routes through Bifrost gateway, applying security guardrails, cost controls, and observability transparently.
[ BIFROST FEATURES ]
Everything you need to run AI in production, from free open source to enterprise-grade features.
01 Governance
SAML support for SSO and Role-based access control and policy enforcement for team collaboration.
02 Adaptive Load Balancing
Automatically optimizes traffic distribution across provider keys and models based on real-time performance metrics.
03 Cluster Mode
High availability deployment with automatic failover and load balancing. Peer-to-peer clustering where every instance is equal.
04 Alerts
Real-time notifications for budget limits, failures, and performance issues on Email, Slack, PagerDuty, Teams, Webhook and more.
05 Log Exports
Export and analyze request logs, traces, and telemetry data from Bifrost with enterprise-grade data export capabilities for compliance, monitoring, and analytics.
06 Audit Logs
Comprehensive logging and audit trails for compliance and debugging.
07 Vault Support
Secure API key management with HashiCorp Vault, AWS Secrets Manager, Google Secret Manager, and Azure Key Vault integration.
08 VPC Deployment
Deploy Bifrost within your private cloud infrastructure with VPC isolation, custom networking, and enhanced security controls.
09 Guardrails
Automatically detect and block unsafe model outputs with real-time policy enforcement and content moderation across all agents.
[ SHIP RELIABLE AI ]
Change just one line of code. Works with OpenAI, Anthropic, Vercel AI SDK, LangChain, and more.
[ FREQUENTLY ASKED QUESTIONS ]
Bifrost CLI supports popular coding agents like Claude Code, Codex CLI, Gemini CLI, and Opencode. All agents work seamlessly with the Bifrost gateway for multi-provider routing and enterprise controls.
When launching Claude Code through Bifrost CLI, the CLI automatically registers Bifrost's MCP server, making all configured tools immediately available. This includes filesystem tools, database connectors, and custom integrations without any manual configuration on your part.
Virtual keys are stored securely in your operating system keyring (macOS Keychain, Windows Credential Manager, or Linux Secret Service). Configuration settings like gateway URL and default preferences are stored in ~/.bifrost/config.json. You can specify custom config paths with the -config flag.
Yes. Bifrost CLI supports virtual keys, allowing you to create separate credentials for different teams or projects. You can also use the -config flag to maintain different configuration files, and the -worktree flag to create isolated git environments for each project. Read more about virtual keys.