Show HN: I made Claude Code listen before it codes (MIT)
github.com
I'm a heavy Claude Code user, and a couple of things kept bugging me. Claude really likes to jump into code. And its responses are too long. I'd skim past walls of text just to find the recommendation. Plan mode helps, but it didn't go deep enough. The questions it asked were still implementation questions, when what I actually needed was alignment on the problem. So I made it stop.
Relay is a different output style and two Python hooks. When you describe what you want, it sits with you to fully understand your intent. Then it moves into the approach phase: walks through the options, pros and cons, and tells you which one it leans toward and why. It writes code only when you say so. When you're confident you and Claude are aligned, that's when you give the go ahead. And responses stay short. Feels like texting a staff engineer, not reading an essay. No more scrolling.
Relay helps you make the right decisions.
When you make a call together, it lands in .relay/sessions/decisions.jsonl in your repo. What you chose, what you rejected, why. Your next session picks up where this one ended, with the reasoning intact. Commit it, your teammate pulls, their Claude Code knows why you did it that way too.
The entire "brain" is one markdown file plus ~50 lines of Python. Read all of it in 5 minutes. MIT.
Install: /plugin marketplace add basegraphhq/relay-plugin then /plugin install relay@basegraph.
What I'd actually love feedback on: the preference learning bit. Relay is supposed to learn how you want to work via AskUserQuestion at real decision points, and silently from corrections you make. Tell me when it asks too much or too little.