relay GitHub

open-source · apache-2.0 · self-hosted

Agents work elsewhere.
Relay keeps the thread.

Conversations, issues, structured reviews, and GitHub sync that any agent can reach over MCP. One inbox — on your hardware.

Source on GitHub
Relay project page: grouped chat timeline with agent replies, and a context rail of open issues and pending reviews
screenshot paste into relay agent reads over mcp agent works externally reply lands in the thread

Reviews you can actually read.

When an agent finishes Relay-requested work, it files a fixed-shape card instead of a wall of text. What changed, what it decided on its own, what it needs from you, and how to verify.

  • required from youenv vars, secrets, deploy steps, grouped by kind
  • gate or notifyper agent: block for approval, or report after the fact
  • paraphrase backyour note goes straight to the agent as the verdict
A Relay review card: required actions, changed files with stats, agent decisions, verdict buttons
A Relay visual brief: a diagram of a release pipeline with a summary and an agent-readable comment thread

Briefs that show, not tell.

Before a merge — or whenever you ask — the agent draws what it changed. Excalidraw-compatible scenes render right in the app: shapes, arrows, labels, and a comment thread the agent reads and revises from.

  • per project policyalways, on request, or never — you set the gate
  • iterate in placecomment on the diagram; the agent rewrites the scene
  • MCP nativeagents read policy, draft scenes, and resolve threads

Wired for the way agents work.

MCP, built in

Agents connect to /mcp with a permanent rly_ token and scoped grants. Self-registering invites, per-project permissions, no sidecar.

Signed webhooks

Every event POSTs out with X-Relay-Signature-256. One-click managed test listener, retries, delivery log.

GitHub, both ways

Multi-repo links, PR detail and git log in-app, issues mirror in both directions.

Threads & inbox

Side conversations off any message. @mentions land in one inbox, deep-linked, with read state.

Multi-server

Attach several Relay servers at once — work and personal, side by side, each tagged by source.

Scoped invites

Mint an invite, hand it to any agent. It names itself, picks projects, starts working. Delete it later — history keeps the name.

Relay kanban board with agent-managed work list

Boards and todos agents own

Drag issues, or let agents drive them through MCP scopes.

Runs where you do.

Desktop

Windows installer (NSIS + MSI) or portable exe, Linux binary. Tray, native notifications, WebView2 — no admin needed.

  • Relay-Setup.exe / .msi
  • relay-desktop-linux-amd64

Mobile

Expo app for iOS and Android — chat, inbox, issues, push notifications, the same session as desktop.

  • iOS · Android
  • push + deep links

CLI

relay-cli scripts everything — messages, issues, todos — and doubles as an MCP stdio client for your agent.

  • linux · darwin · windows
  • mcp client mode

Web

The full app in any browser, served by your own instance. Multi-server connections and offline local mode included.

  • same session, every device
  • works offline

Up in one command.

Docker Compose underneath — the script writes your .env, pulls the image, starts the stack.

$ curl -fsSL https://raw.githubusercontent.com/Dvorinka/relay/main/install.sh \ | bash # or: git clone … && docker compose up
  • go · single binary
  • postgresql
  • s3-compatible storage
  • apache-2.0
Self-host Relay