From “customers want this” to a pull request.
Press Approve with Claude on any idea. Claude gets a brief built from what customers asked for, opens a pull request in your repo, and when you merge it, every voter hears it shipped.
Prioritize
votes 30 · mrr 40 · effort 30| Idea | Votes | MRR | Effort | Score |
|---|---|---|---|---|
| Sheets source | 31 | $2.4k | M | 92 |
| Dark mode | 24 | $1.1k | S | 81 |
| Email digest | 17 | $640 | S | 64 |
| Notion embed | 9 | $180 | L | 28 |
Works with
your whole stack
Your backlog, with a builder attached
Murmur already knows what customers want and why. Fix with Claude turns that into a brief Claude can build from, and keeps you in charge of every step.
Approve with Claude
Press it on any idea and a side panel shows exactly what Claude will receive. Customer quotes go in as data, and suspicious text is flagged before you confirm.
Your own Claude routine
Murmur starts a run of your Claude Code routine in your Claude account. Claude works on a claude/ branch, reports progress back over MCP, and you can watch the session live.
Or the GitHub route
Prefer GitHub? Murmur opens an issue for @claude, and the Claude GitHub Action in your repo opens the pull request.
Or right in Claude Code
When you open Claude Code in your project, it sees the fixes you’ve approved and asks whether to start one.
Always a pull request
Claude never pushes to main, merges or deploys. Every change waits for your review, like any other pull request.
Closes the loop
When the pull request merges (or you mark it shipped), the idea moves to Complete, voters are emailed and a changelog draft is ready.
Set up once, then it’s one click
Onboarding asks how you built your app. Pick Claude Code and Fix with Claude is switched on for you; everyone else can turn it on in Settings.
- 1 Google Sheets as a data source — 31 voters
- 2 Dark mode for dashboards — 24 voters
- 3 Weekly email digest — 17 voters
Want me to start on #1?
- Set up your Claude routine (about five minutes, once), connect GitHub for the Claude GitHub Action, or add Murmur to Claude Code.
Customer words go in as data, never as orders
- See exactly what Claude receives before it starts
- Suspicious instructions in feedback are flagged
- Works on a claude/ branch, never on main
- Never merges or deploys on its own
- 1-click
- To approve
- 3
- Ways to run it
- 0
- Pushes to main
Sep 24, 2026
Google Sheets is here
Connect any sheet as a data source and refresh it every hour.
Fix with Claude FAQs
Straight answers about how Murmur works, what it costs and where your data lives.
Still curious? Email the maker
- Not on your machine. A Claude routine runs Claude Code on the web in your own Claude account, and the GitHub route runs the Claude GitHub Action in your repo. If you do use Claude Code locally, it sees your approved fixes when you start a session.
- Routine runs use your own Claude plan (Pro, Max, Team or Enterprise) with Claude Code on the web. The GitHub route uses the Anthropic API key you add to your repo’s secrets for the Claude GitHub Action.
- No. Claude works on a claude/ branch and opens a pull request. It never pushes to main, merges or deploys; you decide what ships.
- Turn Fix with Claude on in Settings. The GitHub route works with any GitHub repo that has the Claude GitHub Action set up.
- Murmur works hard to stop that. Customer text is passed as quoted data, anything that looks like an instruction is flagged in the review panel before you confirm, and every change still comes back as a pull request for you to review.
- Solo and Team. It’s also part of the 14-day Team trial, with no card needed.
Let Claude take the first pass.
Turn on Fix with Claude, approve an idea your customers asked for, and review a pull request instead of a blank editor.