See every prompt, response, and tool call
Architect replays agent sessions as a scrollable timeline — assistant messages, file reads, greps, and shell commands with timestamps and duration.
Relay captures Cursor, Claude Code, and other agent sessions via CLI hooks — then surfaces timelines, tool calls, and org secrets in the Architect dashboard.
Free tier · 500 sessions/month · No credit card
500
Free sessions every month
3 min
Typical relay install setup
1
CLI to verify capture
7 days
Starter retention included
Sessions you can replay. Relay captures agent runs with tool-level detail — not screenshots or guesswork.
Why teams switch
What changes when agent runs are captured, searchable, and shared across your organization.
Why Relay
Capture coding-agent runs from developer machines, stream them to Relay, and review timelines in Architect — without standing up your own log pipeline.
Architect replays agent sessions as a scrollable timeline — assistant messages, file reads, greps, and shell commands with timestamps and duration.
Relay normalizes hook events from different coding agents into a single session model so platform teams aren't chasing logs in three IDEs.
The Relay CLI wires local hooks, writes nested auto-collect captures, then relay sync uploads them before you roll observability out to the whole org.
relay install
relay sync
Adapter keys and API tokens live in your Relay organization vault — scoped to admins, encrypted at rest, and injected at capture time.
Filter sessions by tool name, repo, or developer. Review exactly which files an agent touched before a bad deploy or security incident.
Who it's for
Standardize how coding agents run across repos. See which tools developers use and where sessions fail before they block a release.
Audit agent tool calls — file reads, shell commands, network requests — with org-scoped retention and export for compliance.
Replay the session that produced a bad diff. Filter by grep, read, or terminal events to find the step that went wrong.
Understand agent adoption without standing over shoulders. Session volume and duration metrics show where AI assistance actually lands.
One Architect workspace for every adapter. Compare Cursor vs Claude Code usage and consolidate secrets in the org vault.
How it works
Three steps: install the CLI, verify a capture, then review agent runs in Architect.
Run relay install in your repo. The CLI registers Cursor hooks (and other adapters) to stream session events.
After a Cursor or Claude Code task, run relay sync to upload nested files from ~/.relay/captures/<agent>/<session>.json.
Open the Architect dashboard — browse session timelines, filter tool calls, and manage org secrets.
Building headless? Read the docs →
Guides
Step-by-step workflows for installing Relay, verifying capture, and reviewing sessions in Architect.
Browse all guidesUse the Architect dashboard to inspect agent timelines, tool inputs, and failures across Cursor and Claude Code.
Run relay run, trigger a Cursor task, and confirm events in Architect before team rollout.
Run relay install, trigger a Cursor task, and confirm hook events land in ~/.relay/captures before you sync to the API.
Recently added
What's new
Updated
Capture your first agent session in minutes.
Run relay install, trigger a Cursor task, and open Architect to see the timeline
— free, no credit card.
Pricing
No hidden fees. Upgrade, downgrade, or cancel anytime.
Solo devs & small teams trying capture
What's included
Platform teams standardizing on agents
What's included
Security review, SSO, and custom retention
What's included
| Feature | Starter | Team | Enterprise |
|---|---|---|---|
| Agent sessions / month | 500 | 5,000 | Custom |
| Session retention | 7 days | 30 days | Custom |
| Architect dashboard | |||
| CLI (relay install / relay run) | |||
| Cursor adapter | |||
| Claude Code & Windsurf adapters | |||
| Org secrets vault | |||
| Tool-call timeline search | |||
| Team roles | |||
| SSO & audit exports | |||
| Dedicated support |
One session equals one captured agent run — from hook install through Architect review.
Enterprise
Same capture pipeline and Architect dashboard — plus contracts, security reviews, and hands-on rollout for larger orgs. Most teams start on the free tier.
FAQ
Relay records agent sessions from tools like Cursor and Claude Code — prompts, assistant responses, tool calls (read, grep, shell), hook events, and timing. You get a searchable timeline in the Architect dashboard, not a black-box log file on each laptop.
Run relay install in your repo. It wires Cursor hooks (and other adapters as they ship) to write nested auto-collect captures. Use relay sync to upload them before your team rolls it out org-wide.
API keys and adapter credentials live in your Relay organization vault — encrypted at rest, scoped to workspace admins, and never checked into git. Developers authenticate with Relay CLI; secrets are injected at capture time, not pasted into agent config.
Retention depends on your plan: Starter keeps 7 days, Team keeps 30 days, and Enterprise offers custom retention. You can export session timelines before they age out.
Yes. Relay normalizes events from Cursor, Claude Code, Windsurf, and other adapters into one session model so platform and security teams see a single audit trail — not siloed logs per IDE.
Sessions are isolated to your organization. Relay does not train models on your capture data or share timelines across tenants.
Install Relay, capture your first session, and open Architect — free tier includes 500 sessions every month.