Repository navigation
🐛🧑💻 - Explain rejected comment command input with actionable validation errors #701
Description
Is there an existing issue for this?
- I have searched the existing issues.
Which actions are affected?
Issue, Pull Request
Which platforms are affected?
Linux, macOS, Windows
Description
A malformed comment command is correctly rejected before effects, but its public reply discards the specific parser reason and gives only validation.invalid-input and “Correct the input and retry”. A contributor cannot tell whether the command exceeded the argument count, exceeded the character limit, had invalid quoting or used an unsupported form.
Observed on PR #699: #699 (comment)
Source request: #699 (comment)
Run: https://github.com/vypdev/copilot/actions/runs/40211874692
Correlation: comment:6400176794; error reference cb3dbecc-7ba6-4704-afcf-d62d4d75c6c9.
The request placed a long explanation after /copilot recheck, exceeding its 20-argument parser bound. This was an invalid request, not a crash during review. The corrected bare command succeeded in run 40212533462: #699 (comment).
Expected: preserve strict grammar/2,000-character/argument/authorization limits and show a safe, localized reason plus a valid next action. Do not echo arbitrary operands, credentials or private prose.
Representative reply:
Request not accepted: this command exceeds the allowed argument count.
Send/copilot recheckon its own; place scope explanations in a separate comment.
No review ran and no repository changes were made.
Command help
Reproducing the issue
- In a permitted issue/PR comment, submit
/copilot recheckfollowed by more than 20 whitespace-separated words (within 2,000 characters). - Observe the correct early rejection.
- Observe that the published error does not disclose the safe parser cause or a correct command example.
- Submit the bare command and observe that review can proceed.
Audit the documented argument contract for every command; distinguish bounded operands from supported human prose. Do not silently widen recheck semantics or weaken command validation to hide the UX defect.
Acceptance:
- A closed safe validation-reason contract reaches the localized error presenter.
- The reply identifies the violated rule and a valid next action without raw input leakage.
- Unsupported/malformed/over-limit inputs remain effect-free; replay reuses the existing semantic reply.
- Help, command examples, relevant SDD/catalog evidence and docs agree with the parser.
- Minimum 12 distinct regressions: 4 parser boundaries, 5 safe presentation/recovery behaviors and 3 end-to-end/replay/corrected-retry behaviors. Run the supported-locale matrix in addition; preserve repository coverage gates.
- This is separate from 🐛🧑💻 - Reopened dismissed Bugbot finding remains verification required after copilot recheck and blocks guarded approval #700's reopened-finding state problem.
copilot Version
3.10.5; trusted runtime commit 39679e2.
Relevant Log Output
Error code: validation.invalid-input
Retained state: No new state or external effect was created.
Reference: cb3dbecc-7ba6-4704-afcf-d62d4d75c6c9
Additional context and comments
Deferred follow-up requested after merging #699. Do not start a branch, hotfix, release or deployment for this issue now. The valid recheck already completed; the follow-up concerns actionable validation UX and documented grammar. Source areas: src/domain/copilot_command.ts, comment-command routing, structured application errors, semantic error replies, localization and docs/issues/comment-commands.mdx.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
[-]Explain rejected comment-command input with actionable validation errors[/-][+]🐛 - Explain rejected comment command input with actionable validation errors[/+]vypbot commentedon Oct 25, 2026
Hi! I’m @vypbot, the Copilot assistant for this repository.
I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.
Try
/copilot helpto see the available commands, or mention @vypbot with your question.[-]🐛 - Explain rejected comment command input with actionable validation errors[/-][+]🐛🧑💻 - Explain rejected comment command input with actionable validation errors[/+]1 remaining item
vypbot commentedon Oct 26, 2026
Implementation plan
Acceptance: The supported-locale matrix and coverage gates pass; at least 12 distinct regressions verify that malformed, unsupported, and over-limit commands remain effect-free, replay reuses the semantic reply, and localized replies identify the safe violated rule and valid next action without exposing raw input; help, examples, SDD/catalog evidence, and docs match the parser.
Need something else? Mention the bot with a question or use
/copilot help.bugfix-701-explain-rejected-comment-command-input-with-actionable-val…
vypbot commentedon Oct 26, 2026
Issue closed — historical progress
Current status: closed as completed.
The last estimate is retained below as history. Closure does not certify a new percentage, tests, or branch alignment.
Action required: none for this closed issue. If work continues, reopen the issue; a fresh assessment can update this same card.
Last assessment before closure (historical)
vypbot commentedon Oct 26, 2026
Issue closed: synchronization recommendation retired
No branch synchronization is required for this closed issue.
The previous recommendation is historical. Issue closure does not certify that the branches are synchronized.