Signals

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

Sky Enterprise Filmatic Rollcall MyPacks Volvox NextGame Switchboard
What a signal holds

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.

01

Four kinds of input

Bug reports, feature requests, general feedback, and your own observations all live in the same stream.

02

Capture from anywhere

Public Feedback Hub submissions, quick manual capture, or your coding agent over MCP. Every source lands in the same queue.

03

One decision each

Turn a signal into a task, link it to existing work, keep it for later, or dismiss it with a reason.

04

Evidence stays attached

Accepted signals stay linked to the task they became, so you can always see who asked and why.

05

Votes carry through

Public submissions bring their vote counts into review, so the most-wanted request rises to the top of your queue.

06

Decisions keep their history

Every review records who decided, when, and the reason. Reopen a dismissed signal without losing the trail.


How it works

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.

01

Capture it before it evaporates.

A user posts in Discord, a bug arrives through the Feedback Hub, you notice something yourself. File it as a signal in seconds, or let your coding agent file it mid-session.

02

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.

03

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.

04

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.


FAQ

Common questions about Signals.

Which plans include Signals?
Manual capture and the review queue are on every plan, including Free. The public Feedback Hub with feature requests and voting is Indie and above; Free includes bugs-only public intake.
What's the difference between a signal and a task?
A signal is an input waiting for a decision. It only becomes a task when you decide it deserves to be built. The backlog holds possible work; a release holds committed work.
Can my coding agent capture signals?
Yes. Over MCP, Claude Code or Codex can file a signal mid-session. Tell it "a user reported the export breaking" and it lands in your review queue. MCP is Indie and above.
What happens to signals I dismiss?
They move out of the queue with your reason attached. Nothing is deleted, so you can reopen one later with its full decision history intact.

Start the loop

Stop guessing what to build.

No credit card. Free stays free.
Capture your first signal in about five minutes.