send_feedback
Report bugs, friction, or feature ideas about VibeView itself to its team, showing the user the draft and getting approval before sending.
Instructions
Send the VibeView team a bug report, a friction note or a feature idea about VibeView itself. Only for problems with VibeView itself (the CLI, MCP tools, devices, sessions, runs, dashboard, docs) — never for bugs in the user's own app. Show the user what you will send and get their OK first. Never include passwords, tokens, API keys, test data values or personal data. One report per problem; do not resend it. kind: bug (something broke), friction (it worked but was confusing, slow or awkward), idea (a missing capability). user_quote: the user's own words, verbatim — never a paraphrase. The report includes the session's device and status when it names one.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"kind": "<kind>",
"summary": "<summary>"
},
"name": "send_feedback"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | bug, friction or idea. | |
| details | No | What you tried, what happened, what you expected; kept to 4000 characters. | |
| summary | Yes | One line; kept to 200 characters. | |
| session_id | No | Session ID to target. Optional: falls back to the MCP-server-held dev_start session, then this project's `vibeview dev --detach` state, if either is available. | |
| user_quote | No | The user's own words about the problem, verbatim (optional). |