Launching today
Relay
Stop repeating yourself to every AI
104 followers
Stop repeating yourself to every AI
104 followers
❌ Every time you open a new AI chat, you paste the same context all over again — your stack, decisions, constraints, where you left off 🛠️ Relay fixes this. It captures what matters from your AI chats and keeps a living project brief ready. One click injects your full context into any fresh conversation 🦾 Via MCP, your IDE agents (Cursor, Claude Code, Windsurf, Codex, etc.) read and write the same brief, synced automatically Works with: ChatGPT, Claude, Gemini, Grok, and more. Free to start
Relay
HasData
@alimkhan_y for me, what should persist: stack + versions, current sprint goal, key architectural decisions plus the ones we rejected, naming conventions, last 'state of play'. what should be forgotten: random debugging tangents, throwaway one-off questions, anything we reverted. the brief should feel like a living readme, not a chat log.
The pain is real — every new Claude/GPT/Cursor session starts from zero and you spend the first 5 minutes re-explaining your stack. A shared context layer that just follows you across tools is the right fix. What happens when context gets stale or contradictory — does Relay surface that, or does it trust whatever was saved last?
Relay
@dmitrii_volosatov Great question. Relay does not blindly trust every saved note forever. The idea is to keep context inspectable and updateable: agents can recall what was saved, then overwrite, supersede, or clean up stale context as the project changes. We’re leaning hard into “living context,” not an append-only memory dump.
The 'stop repeating yourself' pitch hits home. Does Relay sync your context across different LLM interfaces (like ChatGPT and Claude) simultaneously?
Relay
@rivra_dev Yes, that’s the goal. Relay gives different AI clients a shared project memory layer, so Claude, ChatGPT/Codex, Cursor, etc. can pick up the same brief, decisions, tasks, and project context instead of each starting cold.
Starnus
@alimkhan_y Congrats, every day I have this challenge, but I solve it by keeping a clean set of md files in my repos and always instructing the agents to keep them updated (e.g. build plan, architecture, progress, audit, summary, etc.). I was curious to know how it would be different from that and what would be the added value/benefit here?
Btw, very cool product and love the website!
Relay
@khashayar_mansourizadeh1 Thank you, and that markdown-file workflow is exactly the closest manual workaround today. The difference is that Relay makes it shared across tools, searchable/recallable by the agent, and easier to keep focused on durable project state rather than a pile of files that every agent has to be re-taught to read and maintain. The added value is less ceremony and fewer stale docs while still keeping the context inspectable.
Atlas Navigation
This is painfully relatable. I run a 3 person startup and we use Claude, Claude Code, and ChatGPT across the team. the context re-pasting is real. Solo founder from Kazakhstan building this is impressive too. Good luck today!
Relay
@tjclayton Thank you TJ, really appreciate it. That cross-tool context re-pasting is exactly the pain Relay is trying to remove.
TabAI
Goated idea, real problem i've been suffering from myself. Building in the same space, tried their product and LOVED it. Congrats on the launch guys! Good luck
Relay
@igor_martinyuk Thanks!
HasData
Relay
@nikita_naumov Thank you Nick, really appreciate the support. That pain point is exactly why I started building Relay.