Connect your agents

Connect has one job: wire your AI coding agents to your design system so the code they generate defers to it. Every tool speaks MCP to the same preset AI endpoint.

Copy link to sectionThe status line

The top of the page tells you only what preset AI can actually verify:

• Governing <your design system>: the system your agents are governed against.
• gateway online / unreachable: a live reachability check of the MCP gateway.
• last agent request: when we last saw a real request arrive, if any (across both API-key and browser-OAuth agents).

If your design system is bound to a GitHub organization, a second line explains why: it's the repo preset validates against and where CI runs the design-system gate. Use Change source to rebind.

Copy link to sectionEditors & agents

Pick your tool for the exact setup snippet:

• Browser auth (no key): Claude Code, Cursor, VS Code, and Gemini authenticate in your browser on first use. Nothing to paste but one command or config.
• API key: Codex, Windsurf, JetBrains, and Zed use a design-system-scoped key. Generate one under API keys and drop it into the snippet.
• Anything MCP-capable works, even if it isn't listed. Point it at the same endpoint.

Prime offline with a context file

Tools that read a drop-in context file (Claude Code, Cursor, and VS Code / Copilot) offer a Download in their expanded row: a point-in-time file carrying your real tokens, presets, and enforcement rules, for when live MCP isn't available. Place CLAUDE.md and .cursorrules in your project root, and copilot-instructions.md in .github/. Live MCP is preferred (it stays in sync); the file is a fallback. Tools that don't read one of these files (Codex, Gemini, Windsurf, JetBrains, Zed) connect over live MCP instead.

Copy link to sectionManage your keys

Each API key on Connect shows what it has been doing, so you can tell a key apart before you act on it:

• Usage: how many calls the key made in the last week, plus the last tool it ran and when. A brand-new key reads "no calls yet"; if we cannot load the activity we say "usage unavailable" rather than guess.
• Revoke: turns the key off without deleting it. Tools using it stop working, and the key stays in the list marked "Revoked" so you keep the record. Revoke asks you to confirm first, so a stray click never takes a key offline.
• Delete: removes the key permanently. It also asks you to confirm, and it cannot be undone.

Copy link to sectionVerify and enforce

• Verify it's working hands you a prompt to paste to your agent; the moment a real request arrives, it confirms here. See Verify your connection.
• CI enforcement gates pull requests on design-system validation via GitHub Actions (OIDC, no key stored in CI).

Copy link to sectionActivity

The Activity line on Connect summarizes what your agents have done in the last 7 days: total requests, success rate, average response time, and the last tool that ran. View activity opens the full view, with the most recent requests, the drift the gate caught, and your monthly gateway-request usage.

The totals count every connection type: API-key tools, browser-OAuth tools, and CI (GitHub Actions), plus any keyless call we cannot attribute. Each stream is logged separately and Activity reads them all, so the number is the true total, not just the keyed half. The counts and success rate cover the whole 7 days; the request list shows the most recent (up to 50).

Copy link to sectionWhere the other things went

Connect used to also carry GitHub source binding, Figma sync, and your component foundation. Those moved to their own homes: source binding and Figma live under Sources, and component foundation lives under Foundations. Connect is only about your agents now.