Feedback panel

import { MedianFeedback } from "@mediansh/widget";

<MedianFeedback apiKey="median_pk_...">
  <button>Share feedback</button>
</MedianFeedback>;

A visitor writes a note and presses Send. A model files it as a bug or a suggestion in Signal, or drops it as spam. Mounted alongside MedianSupport, the two share a visitor, so a person who writes in and leaves a note is one customer.

Props

MedianUser, telemetry, screenshot, diagnostics and appState work as they do on MedianSupport. See Context and diagnostics. To open the panel from a menu or a shortcut, see Control from code.

Where a note goes

The panel says thanks as soon as the note is saved. A model reads it afterwards.

• A note about something already on the list joins that signal instead of adding a row. Ten people with the same complaint make one signal with ten reporters. Each person's own words stay on their report.
• Spam is only what nobody could act on: adverts, links to unrelated products, keyboard mashing, and tests of whether the box sends. A rude note is not spam. Neither is a one word complaint.
• Priority is urgent, high, medium or low.
• Reading a note uses your workspace's AI credits. See Plans.
• If the model cannot read the note, nothing is filed. The visitor has already been thanked.

Turn filing on or off

Notes are filed only while Track bugs and suggestions is on in Agent → Behavior. It is on by default. The same switch controls what the agent files from conversations.

Pictures

A visitor adds pictures three ways:

• The Add a picture button, which opens the file picker for images.
• Dragging an image onto the panel. The box reads "Drop to attach" while it is over the panel.
• Pasting an image into the panel.

A picture that breaks a rule stays in the panel with its reason, and Send stays off until it is removed.

Automatic screenshot

When the visitor presses Send, the panel takes a picture of the page and adds it to the note.

Pictures show on the report in Signal, and on the Linear or GitHub issue when the signal is pushed to one.

Placement

Against a trigger or an anchor:

• The panel opens 8px below it, or above it when there is not enough room below and more room above.
• Its left edge lines up with the trigger's left edge. If that would run off the window, the right edges line up instead.
• It stays 16px inside the window and moves with scrolling and resizing.

The anchor is only a position. Pressing it does not open or close the panel, and closes an open panel like any press outside. An invalid selector logs Median: the anchor passed to <MedianFeedback> is {selector}, which is not a valid CSS selector. and the panel opens in the corner.

From a dropdown

Choosing a menu item closes the menu and removes the item, so the panel has nothing to sit against. Mount the panel outside the menu and point anchor at the button the menu opens from:

import { MedianFeedback, medianFeedback } from "@mediansh/widget";

<MedianFeedback apiKey="median_pk_..." anchor="#account-button" />;

<DropdownMenuItem onSelect={medianFeedback.open}>
  Share feedback
</DropdownMenuItem>;

Sending

• Send is off while the box is empty or a picture has a problem.
• After a send the panel shows "Thanks for your feedback." and closes itself 1.6 seconds later. It opens empty next time.
• Closing the panel without sending keeps the draft until the page reloads.
• A failed send keeps the draft and the pictures and shows the reason under the box.

A "Powered by Median" line sits beside the buttons. Hide it with Show Median branding in Settings → Billing, on a plan that allows it. See Plans.

Limits

Send notes from the CLI, API or MCP

Send notes collected outside the browser, such as app store reviews or survey answers, through the same reader. These routes wait for the verdict, usually a second or two, and return it.

median feedback submit --from user_8812 --body "The export button does nothing on my phone." --image https://files.acme.com/8812.png

curl https://api.median.sh/v1/feedback \
  -H "Authorization: Bearer median_key_..." \
  -H "content-type: application/json" \
  -d '{"session":"user_8812","body":"The export button does nothing on my phone.","images":["https://files.acme.com/8812.png"]}'

await median.feedback.submit({
  sessionId: "user_8812",
  body: "The export button on the billing page does nothing on my phone.",
  images: [
    { url: "https://files.acme.com/8812.png", name: "Billing page on iOS" },
  ],
});

The HTTP route is POST /v1/feedback. It takes a Median key or an OAuth token. See Authentication. Every CLI flag is in the CLI reference.

Over MCP, send sessionId in place of session, and pass each image as { url, name? }.

The response is { outcome, signalId }.