/feedback: “Save feedback bundle” is easily mistaken for submitting feedback
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start with the /feedback flow in Copilot CLI and reproduce the listed steps. Update the “Save feedback bundle” wording and explanation to make the local-only behavior explicit, then verify that the flow still creates a local archive without implying that feedback was submitted.
Written by the indexing model from the issue text.
Description
Describe the bug
The /feedback flow presents an option labeled “Save feedback bundle.” This wording is easily interpreted as saving/submitting the feedback to GitHub, but the action only writes a local diagnostic archive. A user trying to send a complaint can complete the flow without realizing that nothing was transmitted.
Affected version
1.0.83
Steps to reproduce the behavior
- Run
/feedbackin Copilot CLI. - Choose Save feedback bundle.
- Observe that a local archive is created, but no feedback is submitted.
Expected behavior
Use an explicit label such as “Save diagnostic bundle locally” and clearly state that it does not submit feedback. Provide a separate, obvious “Submit feedback” action when direct submission is available.
Additional context
Linux, Copilot CLI 1.0.83. No session logs are attached because the wording problem is reproducible without them.
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/copilot-cli
-
area:agents area:mcp
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/copilot-cli#4729 ·
-
area:sessions
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/copilot-cli#4712 ·
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
github/copilot-cli#4638 ·
-
Expose large_output_file_path on TaskShellProgress so clients can read complete shell-task output Openarea:tools
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github/copilot-cli#4630 · 1 comment ·
-
Clarify startup message "No copilot-instructions.md found" to specify it means the repo-scoped file Openarea:context-memory
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
github/copilot-cli#4475 ·
All issues in github/copilot-cli
Similar issues
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·
-
area: compat bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
zenhub-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenLiberty/ci.docker#747 ·