Architect is the web dashboard for Relay (relay/web). After hooks capture locally and relay sync uploads events, platform and security teams review what coding agents actually did.
Open Architect
Dev environment:
https://app.dev.relay.oprag.aiSign in with the same organization you registered during relay install.
Sessions list
The Sessions view shows:
- Agent runtime (Cursor, Claude Code, wrapped CLI)
- Repository or workspace context when available
- Start time, duration, and sync status
- Environment ID matching
relay status
Filter by date or environment when rolling out multiple pilot machines.
Timeline detail
Click a session to open the tool-call timeline:
- Reads — files and docs the agent accessed
- Tool calls — shell, search, MCP, or custom tools with inputs
- Failures — errors and retries (useful for debugging agent loops)
- Metadata — session ID, environment, IDE version
Timelines are the primary artifact for security review — not chat transcripts alone.
Compare environments
Use Architect when validating capture before rollout:
| Pilot machine | Expected in Architect |
|---|---|
| Engineer laptop A | Distinct environment ID, sessions after sync |
| Engineer laptop B | Separate environment, same org |
| CI runner (if enabled) | Wrapped relay run sessions only |
Sharing findings
Export or link session detail pages when filing tickets. Avoid pasting raw hook JSON — Architect already redacts org vault references.