Getting started with Relay

Sign in and set up your organization (~1 min)

1. Open console.exemplar.dev  and sign in.
2. Create an organization (or accept an invite) if you do not have one yet. See Account Settings.
3. Confirm you can open the console home for that org.

Connect your coding agent

Install Relay for each surface you use. Prefer global (user-level) install so every workspace is covered; project-only is optional. Org policy is the same either way.

Option A — exemplar-skills (~5–8 min)

npx github:Exemplar-Dev/exemplar-skills
# preferred for Relay across all workspaces:
npx github:Exemplar-Dev/exemplar-skills --global

In Cursor or Claude chat, run /exemplar-relay or ask: “Set up Exemplar Relay.”

The skill walks you through surface selection, a personal API key with RELAY scope (Tokens), and writing hook settings (global or project).

Guide: Install IDE agent skills.

Option B — Connect tab (~10–15 min)

1. Open console.exemplar.dev  → Relay → Connect.
2. Pick surface, environment, and platform.
3. Create a personal API key with RELAY scope and export EXEMPLAR_API_KEY.
4. Copy the generated settings / bridge / hooks / plugin and install (global or project).
5. Use Verify on the Connect tab when ready.

Surface-specific notes: Connect surfaces.

Define Control rules

Create active rules under Control rules across bash, path, MCP, and prompt. Start with allowlists for safe package scripts and repo paths; deny secrets paths and destructive shell.

You can add a starter pack from Connect / Rulebook after hooks are live. Full walkthrough with screenshots: Apply and manage policy packs.

Verify allow and deny (~2–3 min)

Trigger a known-allowed action (for example npm test) and a known-denied one (for example write to .env). Confirm decisions in audit and replay and that Live wire shows the correct surface (claude, cursor, codex, or opencode).

Denied calls should return a clear deny in the IDE—not a silent failure.

Turn on Behavior Guards (Starter+, optional)

On paid plans, open Relay → Guards. Enable Behavior Guards, tune detectors (or disable one), run a Sample from a detector row, and confirm open incidents. Details: Behavior Guards.