Skip to content
Docs

basemodo feedback

Tell Basemodo what is wrong or missing, as the signed-in Person.

Terminal window
basemodo feedback [OPTIONS] <TEXT>

Feedback is kept, then emailed to Basemodo's support with the Person's email as Reply-To: the answer comes by email. Write what happened or what you wish Basemodo did, and say whether it is a bug, an idea or something else. Sent by an agent through the MCP, it carries the agent's MCP client (its name and version). One Person sends up to 10 an hour and 20 a day; the same text sent again within a day is the Feedback already kept.

Arguments

  • TEXT (required): What happened, or what you wish Basemodo did: up to 5000 characters.
  • --category <CATEGORY>: What it is about: bug, idea or other.

Like every command, it also takes the global options --json and --api-url.

Examples

Tell Basemodo about a bug:

Terminal window
basemodo feedback "The Logs stay empty after a Deploy" --category bug

Suggest something:

Terminal window
basemodo feedback "deploy could say which port it expects" --category idea

Output

With --json, it prints {"id", "email", "text", "category" (bug, idea, other or null), "context": {"route", "app", "workspace", "user_agent", "client": {"name", "version"}}, "sent_at", "read"}. Over 10 an hour or 20 a day is an error with code too_many_feedback.

From an agent

Basemodo's MCP serves it as the tool feedback. It changes things, so an agent's client may ask you before it runs. Its arguments are the command's, named as JSON keys: text (text), category (text). It answers what the command prints with --json.

Explained in