Relay Agent — Concept Prototype

← Concepts / Apps / Relay Agent

Relay Agent

erik's workspace

Live

Notifications

Claude Code wants to claim HAVVPX

relay-dev · 2m ago · needs approval

Expiring in 4h

"Auth unification handoff" · DS35RF

Milton claimed your code

DS35RF · code-split handoff

Erik

erik · Relay Context Inc.

Beta

Security

PasskeyEnabled

Active sessions2

morning brief

Two things need you, nothing's on fire. Milton's auth handoff expires in 4h.

Claude Code wants to claim

HAVVPX · relay-dev · 2m ago

capture: renew the auth handoff before it expires

📝

Captured to relay-ops

Filed, no transfer created yet

Filed it. Want me to draft the renewal as a transfer to Milton now, or leave it in the Stream for later?

claim HAVVPX

Auth unification handoff

HAVVPX · Milton · Jul 25 · Private

That's the one Claude Code just asked to claim, above, still pending your approval. Approve it first, or I can load a read-only preview now.

Jump to a feature

Ask Relay anything, or capture a thought…

What it can do that MCP clients can't

Approve above works, live. That's the deliberate contrast with the Chat concept, where connection-request approval is fenced off from any third-party agent (Claude, ChatGPT, Cursor) as a fail-closed rule. This surface is Relay, with the user's real session, so it's allowed to act where a guest agent isn't.

Where this lives

Not a new tab in the 5-tab mobile shell, and not a separate product. Reachable as a slide-out panel from the app/console (⌘K-adjacent) and as its own Capture-pane mode on mobile: one agent, several entry points, same Stream-aware context every time.

Tools panel: reaching Graph, Streams, Explore

Tap + next to the input: the tools sheet opens above it (the input visibly slides up), not a new page. Explore stays visible but locked (Horizon badge) rather than hidden, matching the fail-closed-visible rule used across the gallery. A feature you don't have yet should read as "not yet," never as if it doesn't exist.

Notifications + Profile/Security

The bell's badge count is the same number as the mobile Activity tab's badge: same data, two renderings. Profile is a quick-glance panel (identity, tier, passkey status, active sessions), not the full Settings screen; "Manage account" is where that handoff would go. See briefs/SPEC.app-components.md for the full cross-surface component matrix; these three (tools, bell, profile) now also apply to Mobile, not just here.

Scope

Concept only, unscheduled. Card component matches the shipped app/mobile visual language (not the MCP .cm block used in Slack/Chat) since Relay controls this surface end to end. Approve/Deny, the tools panel, and the profile/notification panels are live demo toggles, not real backend calls.

Concept prototype · not production UI · relay-creative/concepts/app-relay-agent.html