Stop losing what users tell you.
Feedback arrives in Discord, DMs, and your own head, and most of it is gone by the next release. In Frostbyte it all lands in one stream called Signals. Review each one once, make the call, and the reasoning stays with it.
Used by developers at
One stream for everything you learn.
A signal is one thing you learned about your product. It takes seconds to capture and carries what review needs: what was said, who said it, where it came from, and how many people want it.
Four kinds of input
Bug reports, feature requests, general feedback, and your own observations all live in the same stream.
Capture from anywhere
Public Feedback Portal submissions, quick manual capture, or your coding agent over MCP. Every source lands in the same queue.
One decision each
Turn a signal into a task, link it to existing work, keep it for later, or dismiss it with a reason.
Evidence stays attached
Accepted signals stay linked to the task they became, so you can always see who asked and why.
Votes carry through
Public submissions bring their vote counts into review, so the most-wanted request rises to the top of your queue.
Decisions keep their history
Every review records who decided, when, and the reason. Reopen a dismissed signal without losing the trail.
Open the doors and the feedback finds you.
You don't chase any of this down. Give users a public place to post and vote, put a button inside your product, and capture the rest yourself the moment you hear it. Every door leads to the same queue.
A public portal.
Your Feedback Portal gives users a branded place to report bugs, request features, and vote, with a public roadmap that shows what you did about it. No accounts needed.
A widget in your app.
The embed widget puts a quiet feedback button inside your product, themed to match it. Bug reports arrive with the page and browser details attached.
Your own ears.
Something said on a call, a bug you spotted yourself. Capture it from the Signals page in seconds, or let your coding agent log it over MCP while you work.
From something a user said to something you shipped.
Signals is the front door. Everything enters here, gets one honest decision, and leaves as committed work or a recorded no.
Capture it before it evaporates.
A user posts in Discord, a bug arrives through the Feedback Portal, you notice something yourself. File it as a signal in seconds, or let your coding agent file it mid-session.
Review it once.
Each signal gets one decision: become a task, join an existing one, wait in Kept, or get dismissed with a reason. Nothing sits in limbo.
Build with the evidence in view.
Accepted signals become tasks that carry their evidence. When you plan a release, you're weighing real requests and votes instead of guessing from memory.
Close the loop.
The work ships in a release, the public roadmap moves, and the people who asked can see it. That's what keeps the feedback coming.
Common questions about Signals.
Which plans include Signals?
What's the difference between a signal and a task?
Can my coding agent capture signals?
What happens to signals I dismiss?
Start the loop
Stop guessing what to build.
No credit card. Free stays free.
Capture your first signal in about five minutes.