01
Contextual feedback
Reviewers can leave a thought on the page itself, while teams have a project workspace and inbox to keep the conversation organized.
Start a workspaceProduct roadmap
We’re building from a simple principle: comments are most valuable when the original page stays linked from review through action.
This page describes planned work, not capabilities available in the product today. We’ll update it as each stage becomes real.
01
Reviewers can leave a thought on the page itself, while teams have a project workspace and inbox to keep the conversation organized.
Start a workspace02
Turn the right conversation into a support ticket with its original page, thread, and resolution details attached. The goal is a clean handoff—not another disconnected queue.
03
Offer a standards-based MCP connection so an approved agent can retrieve feedback alongside the original page, surface patterns, and prepare summaries for the tools your team already uses.
04
Summaries should help teams spot what matters across pages and releases. Any agent connection will be opt-in, scoped by the workspace, and designed to recommend—not silently make changes.
How we’ll build it
Feedback stays tied to the page and conversation that produced it.
MCP is the intended bridge, so integrations do not need a one-off path for every tool.
Teams decide what to connect, what to share, and what gets acted on.
Start with the signal
Use Feedback today for the focused, on-page review loop—and follow along as we build the handoff layer around it.
Create your workspace