Qwen Code’s October 24, 2026 release gives GitHub maintainers a new way to delegate follow-up on proposed code changes, known as pull requests. Version 0.26.1 adds a command designed to attempt repairs after failed automated checks or review feedback, then push updates and post replies.
For a small software team, the choice is a single pass or a recurring local watch. Neither is a read-only preview: the workflow acts through the user’s Git and GitHub accounts. Final review and merging remain separate decisions.
Start with the supervision decision
Choose a supervised pass for a familiar pull request with a specific failing check or review request.
/autofix-prwith--onceruns one round without creating a watch, but can still commit and push. If this session already watches that pull request, the existing watch keeps running.Consider a recurring watch when feedback is likely to arrive in several rounds, the code is trusted and someone can handle exceptions. Keep the Qwen Code session running: session-scoped tasks do not survive a restart.
Keep design choices and other high-consequence decisions with a maintainer. A sensible first use is a bounded repair task whose code changes and check results a person can inspect.
One pass does not mean fewer permissions
For a supervised first attempt, explicitly select Ask Permissions with /approval-mode default and inspect existing preapproval rules. This is the mode intended to ask before file edits and shell commands, including pushes. The configuration name default is not a reason to assume that every installation starts in that mode.
Auto Mode can reduce interruptions by using a model to assess actions that need approval. Explicit deny and ask rules still apply, and an unavailable classifier can send an action back to manual approval. It does not guarantee that a watch can proceed without a person.
--yes skips the ordinary start confirmation, not tool permissions. Likewise, --no-reply suppresses GitHub posts, not pushes. Running once, posting less and granting permission are separate choices. A shorter or quieter run can still change code.
Teams also using Claude Code can compare its separate changes to unattended-job permissions; its defaults should not be assumed to apply to Qwen Code.
Check whose code and feedback it will use
Qwen’s released workflow instructions call for edits in a separate working copy, called a worktree, and project checks before committing. That separates the editing work; it does not keep your credentials out of the code’s reach.
When a pull request’s author lacks push rights to the repository, the workflow refuses a recurring watch. It offers only a confirmed single pass, because verification runs that contributor’s code with the user’s Git and GitHub credentials in reach. --yes cannot skip this confirmation.
Feedback is accepted from repository owners, members, collaborators, the pull request’s author and qualifying bot reviews or thread starters—not arbitrary commenters. Trusted feedback still cannot expand the permitted work: requests for unrelated changes or weaker checks go to a person.
The maintainer’s pre-release verification reports describe live helper and single-pass exercises, but exclude a sustained scheduled watch and limit their conclusions to the revisions examined. They do not establish a repair-success rate or time savings for the released feature.
A local watch has limits
The documented watch checks every two minutes by default and stops when the pull request is merged or closed, after ten pushes, or through /autofix-pr stop. That interval is not a guaranteed response time.
Session exit ends monitoring, and recurring tasks expire after seven days by default. A busy session can delay scheduled work. Runs without an interactive dialog support only a single pass with --once --yes, not a continuous watch; the outside-contributor confirmation still cannot be bypassed.
A change-detection gate can skip an AI turn when nothing changes. Active repairs and model-based permission checks still consume resources. Ten pushes is therefore a limit on branch updates, not ten successful repairs or a spending ceiling.
Check model access before leaving it running
Qwen Code’s current authentication guide offers subscription, usage-billed and custom-provider routes. Its former OAuth free tier ended on April 15, 2026—older access context, not part of this release. Running the client locally does not by itself make model calls free.
For example, Alibaba Cloud’s international Coding Plan lists Pro at US$50 a month, with quotas and limited availability. But it restricts use to interactive programming tools and excludes automated scripts and other non-interactive scenarios.
Those terms do not name this new command. Before choosing an unattended watch, confirm that your exact use is permitted or choose access that explicitly allows it. Support for Qwen Code as a client does not settle that question.
A practical starting point is one narrow pull request, explicit approvals and a maintainer present. Review the actual code changes and GitHub check results before merging. Move to recurring follow-up only when the permissions, session ownership and model-access terms fit the job.