Skip to Content
RelayGetting started

Getting started with Relay

Stand up Relay so Cursor and Claude coding agents share one policy surface before shell, filesystem, MCP, or prompt side effects.

Console and IDE hook walkthroughs will be added when product how-to assets are published. Until then, follow this conceptual path and the control-channel pages.

Path

Seat engineers

Assign Relay seats to engineers who run governed coding agents. Platform or security owns policy; feature teams get seats without becoming admins.

Define policy rules

Create active rules across the four channels: bash, path, MCP, and prompt. Start with allowlists for safe package scripts and repo paths; deny secrets paths and destructive shell patterns.

Connect IDE agents

Enable Relay hooks for Cursor and Claude so sessions evaluate controls before execution. Keep the same editor workflow—different outcome when a disallowed call is requested: structured deny, not a silent failure.

Verify allow and deny

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.

Next

Last updated on
OverviewBash control