Skip to main content
Bifrost Edge is designed to be invisible. After a one-time sign-in, users keep using the AI tools they already have - Claude Desktop, ChatGPT, Cursor, coding agents in the terminal - and Edge quietly routes that traffic through your Bifrost in the background. There is no proxy to configure, no base URL to change, and nothing to remember.

​
One sign-in

The first time Edge runs, the user signs in through their browser using your organization’s existing single sign-on. That sign-in links the machine to the user and syncs all policies assigned to them. No API keys are copied or pasted, and nothing sensitive lives in the app itself.

​
An always-on menu-bar agent

Once signed in, Edge lives in the menu bar (macOS) or system tray (Windows and Linux). From there a user can see whether they are connected, which key is active, and turn routing on or off. Most people set it once and never think about it again.
Bifrost Edge menu-bar status and controls

Connection status

A clear indicator shows when AI traffic is being governed, and surfaces a warning if something needs attention.

Key selection

Users with more than one virtual key can pick which one to use, with budget visible at a glance.

​
Every app, automatically

Because Edge routes traffic at the machine level, it covers the AI surfaces people actually use without any per-app setup:

Desktop apps

Claude Desktop, the ChatGPT app, Cursor, and other desktop AI clients.

AI in the browser

ChatGPT on the web and other browser-based AI surfaces.

Coding agents

Claude Code, Codex, and similar agents in the terminal and IDE.
The result is that governance follows the user instead of waiting for them to opt in. See the full list on the Supported applications page.
Bifrost Edge showing AI traffic routed and governed

​
Next steps