Skip to content
Charming Docs
Esc
↑↓navigate↵open⌘Jpreview
On this page

Feedback

People using your app can send you a bug report or a suggestion right from the app, and your agent can read it back and turn it into a fix.

What you can do

People report bugs and ideas from inside the app. Every hosted app has a Feedback button in the toolbar Charming puts around it (not something you have to build). Anyone who can use the app, not just the owner, can open it, pick a category (bug, crash, enhancement, praise, or other), write a message, and send it.

A read-only visitor gets a fallback instead. Someone with view-only access can’t submit through the button, since it can’t authenticate on their behalf. A “Copy for agent” button writes a ready-to-paste prompt to the clipboard that names the app and the message, so they can hand it to their own AI assistant instead.

Your agent reads it back and ships changes. Ask your agent to check an app’s feedback; it lists the rows, reads what people said, and can turn that straight into an update. See How Charming works for the update step.

Charming staff can reply to agent feedback. When an authenticated agent submits feedback over MCP, staff can add a question or resolution to that feedback thread. A later successful MCP tool call returns a machine-readable feedback-responses-available advisory. The agent fetches unread replies and decides whether to tell you or keep building. Charming never sends an end-user notification for these replies.

Technical

The Feedback button and its form are part of Charming’s own control-panel chrome, rendered around every app; nothing in the app’s own code has to add a form or an endpoint for it.

Copy this prompt for your agent

Check the feedback for my Charming app and act on it. Read
https://charm.ing/docs/capabilities/feedback.md first. Find the app,
check its feedback, and update the app to address anything
actionable. Ask me before making a change that isn't obvious from
the feedback text.

How an agent performs this job

Use submit_feedback to add an agent note and list_feedback to read feedback. Charming stamps the source, so an agent cannot present its own note as user feedback. Staff replies stay unread until the submitting account calls acknowledge_feedback_responses. Fetching with list_feedback_responses does not acknowledge them. Use update_app to ship a fix.

Charming has no durable connection to an inactive MCP client and does not claim push delivery. It adds the advisory to later successful authenticated MCP calls. Replies target the account that submitted the feedback, not one token or MCP client instance, and require that account to retain access to the app. Feedback submitted before account attribution existed, or through a non-user credential, cannot receive a reply.

The contract

The generated MCP reference and REST API reference define the request fields and error shapes.

Limits, access, and deletion

  • Caps and rates. See Limits.
  • Access. See Privacy and sharing.
  • Ordering and delivery. Unread staff replies are oldest-first with cursor pagination. Charming repeats the advisory until the agent explicitly acknowledges each reply.
  • Deletion. Feedback rows belong to the app. Deleting an app is the only way to clear its feedback log; it goes with the app.

Was this page helpful?