Relay

Relay is actively developedOpen source · Self-hostable · MIT

Your agents work in parallel.Your attention does not.

Relay puts every agent session on one quiet board, and matches work to the energy you actually have. At 9pm, you see what is moving, what is waiting, and what needs you.

GitHubanunay999/relaySelf-hostnpm install and you have a board
claude mcp add --transport http relay \
  https://relay.mytrove.in/mcp \
  --header "Authorization: Bearer relay_..."

Sign in, mint a key in Settings, and any agent can reach your board.

Agents connect over MCP. The browser and the agent share one store.

One board, shared by you and your agents.

Relay sits above Linear, Git, and your coding agents. It optimises the moment work comes back, not the list it came from.

An agent is working on this right now

The board is the API

Agents claim, update, park, and resume over MCP. You parking a row and an agent claiming it take the same code path.

The session is waiting on your answer

Energy in, three answers out

Say how you feel and how long you have. Relay returns three recommendations, or honestly says nothing fits.

Parked with a note about what comes next

Re-entry costs nothing

Parking requires a note. Ending requires a next step. Nothing has to be reconstructed from memory.

Three questions, one quiet board.

01

What is actually in motion?

One goal at a time, its steps laid out in the order they can happen, a dot per agent session. Working breathes, waiting shows half, parked is a ring. You read state, not noise.

02

What can you do right now?

Tell Relay your energy and the time you have. It returns exactly three recommendations, each with a one-sentence reason, and names one thing it deliberately left out.

03

Task, or just a worry?

The thing bothering you lives in a bar at the bottom, off the board, until you decide it has a next action. Attention is not a backlog.

Board1 agent active

Billing migration

No agent session attachedFix webhook retries

captured 2h ago

An agent is working on this right nowReview auth PR #214

codex · reading the diff

Parked with a note about what comes nextMigrate billing schema

parked · provider decision

Launch v0.4

The session is waiting on your answerWrite release notes

waiting on you · v0.4 scope

The session is waiting on your answerUpdate onboarding emails

waiting on you · copy review

An agent is working on this right now

codex is reviewing the auth PR

A slice of the board, scripted. Two agents claim, wait, and park on a loop.

Try the pick.

This is the same function your agents call over MCP, running here on a demo board. An empty answer is valid: Relay would rather say nothing fits than pad three slots with work you cannot do.

I feeland I have

Easy start

Update onboarding emails

Easy to begin: good for low energy, already has a clear next step, should fit into about 15 minutes.

Main thing

Review auth PR #214

This is your most important work that fits the moment. Good for low energy, already has a clear next step, should fit into about 15 minutes.

Not showing Fix webhook retries: it needs sustained attention and you only have 30m.

Run it your way.

Hosted, or a JSON file in your home directory. Same board, same tools, same reducer.

Quick start

claude mcp add --transport http relay \
  https://relay.mytrove.in/mcp \
  --header "Authorization: Bearer relay_..."

Mint a key in Settings after you sign in. Works from any machine your agents run on.

From source

git clone https://github.com/anunay999/relay
cd relay && npm install
npm run dev

No database, no accounts. State lives at ~/.relay/state.json and agents connect over stdio.

No scores. No streaks.No nagging.

Relay never writes back to Linear, never ranks your productivity, never interrupts. It answers three questions and stays quiet.