Every department needsan engineer.

Relay is an AI engineer that lives on your Slack, Linear, and GitHub. Give it a task — it reads the codebase, talks to the right people to gather context, catches what the ticket missed, writes the code, and opens a PR. Think of it as the engineer every department wishes they had on speed dial.

Claude Code and Cursor are incredible tools — for engineers, in their IDE, on tasks they already understand. Relay solves a different problem: the work that starts with a Slack message from support, a question from sales, or a vague ticket from a PM. Nobody is going to open Claude Code for that. Relay lives where the request starts, gathers the context across people, and ships the code. Use both — Relay for work that starts outside engineering, your coding agent for sessions you drive yourself.

Most autonomous agents work alone in a sandbox. Relay is multiplayer — it messages your PM to clarify scope, checks with customer success if a migration breaks key accounts, and loops in engineers for review. It coordinates first, then codes. That’s the difference between an agent that writes code and a teammate that ships the right code.

Relay is for your whole team. Your support team gets a support engineer who can investigate bugs and write customer-safe responses. Your sales team gets a technical partner who checks what’s real before they promise it. Your CS team gets an analyst who connects metrics to code. Your PM gets an assistant who breaks down features and gets them moving. Your engineers get a coworker who handles the coordination overhead.

Relay reads the message, understands who’s asking and what they need, traces the relevant code, identifies who else has context, asks targeted questions, and gets the work done — whether that’s investigating a bug, writing customer copy, shipping a fix, or coordinating onboarding. Everyone affected gets looped in automatically.

Slack, Linear, and GitHub. No new dashboard, no IDE plugin, no context-switching. Relay shows up where your team already works.

Same as any engineer — code review catches it. Relay opens PRs through your normal GitHub workflow. Your team reviews and merges. It doesn’t push to main or deploy on its own.

No. Relay handles the work that currently interrupts your engineers — the support escalation that needs a code trace, the sales question that needs a technical check, the PM’s feature breakdown. Your engineers focus on architecture, hard problems, and reviews.

It learns your team from your Slack and Linear — who owns what, who has context on which areas. When it needs scope clarity, it messages the PM. When it needs to check customer impact, it messages CS. You don’t configure routing rules — it figures it out the way a new hire would.

Bug investigations, feature implementation, refactors, incident coordination, customer escalation support, onboarding coordination, technical due diligence for sales, executive status reports. Anything you’d give to a strong mid-level engineer who knows your codebase and your team.