Relay in Slack — Concept Prototype

Same card, native chrome

The card body below (glyph, bold title, Code, metadata line) is the identical component used in the MCP chat-tool reference (mcp/response-cards.html), just wrapped in Slack's own attachment left-bar instead of a chat-tool header. One visual grammar, worn differently per host.

Two directions

In: /relay capture, a 📌 reaction, or forwarding a message to the Relay app pushes content into the capture pipeline (same slackbox integration as the Capture concept). Out: approvals, claim notifications and resurfacing land here as native, actionable messages, no context-switch to approve/deny.

relay-ops 4 members · #relay-ops

Milton 9:14 AM

forwarded a doc to Relay, plus /relay capture "renew the auth handoff before it expires"

◉

Relay APP 9:14 AM

Capture · relay_stream_update

📝 Captured to relay-ops

"renew the auth handoff before it expires" · routed from Milton's message

filed, no transfer created yet

◉

Relay APP 11:40 AM

A claim needs your approval.

Needs you · relay_request_list

⏳ Claude Code wants to claim

HAVVPX · relay-dev · requested 2m ago

◉

Relay APP 2:03 PM

Resurfacing · expiring

⏰ Expiring in 4h: "Auth unification handoff" from Milton

DS35RF · relay-dev

Message #relay-ops, or try /relay …