Connect your apps

The Gate Connect quickstart is the fast path: install the app, sign in, and turn on your apps from the menu bar. This page covers what happens underneath and the details for each app. Prefer the terminal? See the command-line interface.

Two ways Gate Connect routes an app

Gate Connect connects an app in one of two ways, and picks the right one for you:

• Config integration — for apps with their own config, namely Claude Code, Codex, and opencode. Gate Connect writes the setting that points the app at your gateway, and removes it again when you disconnect.
• Proxy — for apps that talk straight to a provider with no such setting, like Claude Desktop / Cowork and ChatGPT. Gate Connect runs a local proxy that intercepts traffic to that provider’s domain and routes it through Gate. You choose which provider domains to route.

Either way the app works exactly as before; its requests now pass through Gate first.

Notes per app

• Claude Code — config integration. Gate Connect points it at your gateway through Claude Code’s custom-header setting. Your existing Claude Code sign-in is untouched.
• Codex — config integration. Gate Connect writes the base URL into ~/.codex/config.toml. You do not need to set OPENAI_API_KEY; Gate handles upstream auth.
• opencode — config integration. Gate Connect adds Gate as a provider. The keys from opencode auth login stay in place.
• Claude Desktop / Cowork — proxy. Cowork manages its own sign-in: when prompted, sign in to Anthropic from inside Cowork. Gate Connect only points its traffic at Gate; it does not change how you log in.
• ChatGPT, Gemini, and others — proxy. Turn on the matching provider domain and their traffic routes through Gate.

Confirm it is working

Send a message from a connected app, then open the dashboard. New requests appear on the Messages page within a few seconds, each with its model, cost, and security result. If nothing shows up, see Manage connections for status checks and fixes.