Signals

A signal is anything that might change what you build next: a bug a user hit, a feature someone asked for, a piece of general feedback, or an observation you made yourself. Signals land in one queue, you review them, and the ones worth acting on become tasks that carry the original input as evidence.

The review step is the point. Collecting feedback is easy; deciding what to do with it is the part that usually gets skipped. Signals exists so every input gets an explicit decision instead of drifting.

Where signals come from

Two sources feed the queue:

• Your public Feedback Hub, including the embed widget and the bugs-only link. Anything a user submits arrives here.
• Manual capture, for everything else: your own ideas, something a customer said on a call, a bug you noticed while testing. Capture it yourself from the Signals page, or have your coding agent capture it over MCP with signals_capture.

Every signal has a type (bug, feature, feedback, or observation), and public submissions carry their vote count with them.

Reviewing a signal

The Signals page splits into four tabs: New, Saved, Accepted, and Dismissed. Open a signal and you have four outcomes:

• Create a task, turning the signal into new work. The task links back to the signal.
• Link to an existing task, for duplicates and for signals that reinforce work you've already planned. The signal's public votes carry across as evidence on that task.
• Save for later, when it's worth keeping but not now. It moves to Saved and stays out of your New queue.
• Dismiss, when you're not going to act on it.

Every decision records who made it, when, and an optional reason. The full history stays on the signal, so a dismissed signal you reopen months later still shows the original call and why.

Signals, backlog, and releases

Accepting a signal creates a task in your backlog by default, not in your active release. Deciding something is worth doing and deciding it ships next are different decisions. Move it into a release when you're scoping that release. See Releases.

Limits

Free projects hold up to 20 pending signals at a time. Only unreviewed signals count, so accepting or dismissing one frees a slot immediately, and submissions through your public Feedback Hub are always accepted regardless of plan. See Plans and limits.

What's next

• Set up public intake: Feedback Hub.
• Let your agent read and capture signals: MCP server.