--- name: multi-agent-feedback language: en description: "Send one message to the maintainer: a bug, an idea or a question. Only the text you type is sent - no logs, no repo names, no paths. Shows the payload and asks before sending. Use when a run went wrong and the maintainer should know." user-invocable: true argument-hint: "\"\" [bug | idea | question] - with no argument, you are asked for the text" --- # multi-agent feedback - tell the maintainer **Input**: $ARGUMENTS One message to the maintainer's admin panel. It exists because the alternative is a problem nobody hears about: a run goes wrong, the person works around it, and the defect is still there a month later. ## What is sent Only the text you type, plus `kind` (bug / idea / question), the installed pipeline version, which host CLI, and the timestamp. **No logs are attached, ever** - not the agent log, the diff, the repo name, the branch, or a file path. This package installs from a public registry, so an automatic log attachment would take a corporate user's internal identifiers off their machine into someone else's database. Paste the one line you think matters; a script cannot know which line that is. ## Flow 1. Take the message from `$ARGUMENTS`; with no argument, ask for the text and then the kind. 2. Print the exact payload via the script's own dry run, so what is shown is what goes: `node "$HOME/.copilot/scripts/feedback-send.mjs" --text "" --kind --dry-run` 3. **Confirm before sending.** Nothing leaves the machine before a yes; autopilot does not exempt this, because a message to a person is never fired unattended. 4. Send the same command without `--dry-run`. 5. Report the outcome plainly. A failure is surfaced, not swallowed - the person is waiting to hear whether their message went. Auth reuses the usage ingest token, so nothing extra is onboarded. `usageLog.optOut` does not silence this: telemetry is passive collection, feedback is a deliberate act. The endpoint must be TLS; only loopback is exempt.