You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs(native-chat): say why /clear is refused while the agent works instead of queued - #28101
In native chat, typing /clear while the agent is working is refused ("The agent is still working. Run /clear when it's done."). /compact in the same situation can wait in the queue as a card. Nothing in the code says why /clear doesn't do the same, so it reads like an oversight, and someone may build it again.
That already happened twice: #26730 and its smaller rebuild #27928 both made /clear wait in line. Both are closed. The feature needed the queue to run Orca's own work, not only hand messages to the agent, and that cost more structure than the convenience was worth for now.
What changes for users
Nothing. This is a code comment only.
Mechanism
A comment on the delivery field of the conversation-command parameters. That's where /compact opts into waiting as a card. The comment records the structural reason /clear doesn't:
the queue only hands cards to the agent;
a clear is host work: it stops the agent and resets its context;
so queueing it would need the queue's drain to run host commands.
Why
It keeps the decision next to the code a future change would touch, so the next person sees the trade-off before rebuilding the feature.
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 7 remain after this review.
📝 Walkthrough
Walkthrough
The /compact comment now states that /clear is refused while the agent is active because queue draining does not perform the required host-side work. The parameter type and runtime behavior are unchanged.
Priority: ⬇️ Low
Merge Risk:⚪ Minimal · up to aea93
This change documents existing behavior: /clear is refused during a live turn while /compact may be queued. No merge-blocking behavior change is identified.
Pre-merge checks · 4 · 1
Failed checks (1 warning)
Check name
Status
Explanation
Resolution
Description check
The description explains the problem, user impact, mechanism, and rationale. It does not follow the repository template because it omits the required section headings and supporting details for Linked…
Complete the repository template. Add the required sections and provide the applicable issue reference, state N/A for Visual Proof with a reason, document testing or why it was not needed, complete applicable checkboxes, and address AI Disc…
Passed checks (4 passed)
Check name
Status
Explanation
Title check
The title clearly and concisely describes the main change: documenting why /clear is refused while the agent is working instead of queued.
Docstring Coverage
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Description check
Explanation
The description explains the problem, user impact, mechanism, and rationale. It does not follow the repository template because it omits the required section headings and supporting details for Linked Issue, Visual Proof, Testing, AI Disclosure, Review, boundary, Notes, and Checklist.
Resolution
Complete the repository template. Add the required sections and provide the applicable issue reference, state N/A for Visual Proof with a reason, document testing or why it was not needed, complete applicable checkboxes, and address AI Disclosure and review notes.
Fix all pre-merge checks with AI
✨ Finishing Touches
📝 Generate docstrings
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
In native chat, typing
/clearwhile the agent is working is refused ("The agent is still working. Run /clear when it's done.")./compactin the same situation can wait in the queue as a card. Nothing in the code says why/cleardoesn't do the same, so it reads like an oversight, and someone may build it again.That already happened twice: #26730 and its smaller rebuild #27928 both made
/clearwait in line. Both are closed. The feature needed the queue to run Orca's own work, not only hand messages to the agent, and that cost more structure than the convenience was worth for now.What changes for users
Nothing. This is a code comment only.
Mechanism
A comment on the
deliveryfield of the conversation-command parameters. That's where/compactopts into waiting as a card. The comment records the structural reason/cleardoesn't:Why
It keeps the decision next to the code a future change would touch, so the next person sees the trade-off before rebuilding the feature.