Qwen Code 0.27.4: Auto Mode checks whether a risky action was explicitly authorised
In Qwen Code 0.27.4, Auto Mode now judges whether the user explicitly asked for a destructive or wide-ranging action. An action that merely relates to the request is no longer enough. The release also records hook executions and fixes vulnerabilities in dependencies.
Qwen Code’s developers released version 0.27.4 on GitHub on 15 November. The main change concerns the approval mode in which the coding agent takes some actions without asking the user. The release has no known breaking changes, the release notes say.
Auto Mode asks whether the user requested exactly this
Auto Mode sits between Qwen Code’s Auto-Edit and YOLO modes. Automater News, drawing on Qwen Code’s documentation, reported that the mode approves workspace edits and read-only built-in tools directly. A two-stage language-model classifier assesses all other actions.
The classifier now weighs the user’s explicit authorisation, not merely whether the action relates to the request, the release notes say. This applies especially to destructive and bulk actions, discarding changes and actions affecting shared history. In Automater’s reading, the default behaviour now resembles a softDeny hint that users can write into their settings. The documentation says such a hint blocks a destructive action unless the user’s latest request concerned exactly that action at that scope.
The classifier does not replace fixed rules. Automater wrote that permissions.deny blocks an action before the classifier runs, and permissions.ask requires user confirmation even in Auto Mode.
If the fast classifier times out, the session’s own model reviews the action once, but only if the model identifiers differ. With the default timeouts, this can add 30 seconds to a single tool call, Automater said. Auto Mode also no longer tries to interpret HTTP(S) addresses as file paths. On Windows, the attempt triggered slow network lookups, and a session could be cut off before the network request began. In the browser interface, Full Access mode now appears in a warning colour.
Hook logging and managed sessions
A harness is the program that controls an agent: it gives the model its tools and runs its steps. A hook is a command the harness runs at a set point. The new version records hook executions in session history turn by turn. Users can view the records on read-only pages and through the SDK, and the records feed summaries and signed snapshots.
When a browser user grants temporary permission, managed agent sessions (Managed Agent) can now use that user’s local directories without storing credentials or paths. Users can open an interactive terminal in a session with a short-lived token (Managed Web Terminal). The Japanese blog Labmemo reported that the terminal is off by default and requires the workspace’s OPERATOR permission. Automater said Qwen Code’s reference deployment guide calls the Managed Agent distribution experimental, and local tools are not enabled by default in a new installation.
Security fixes and availability
The release fixes dependency vulnerabilities in libraries including MCP, DOMPurify, qs, fast-uri, ip-address and Hono. It also includes an experimental shared agent loop, which is off by default. Other changes include sending messages to Feishu and WeCom by webhook and splitting long replies into ordered parts.
The CLI version can be downloaded from GitHub. Labmemo reported that the separate desktop app was released as desktop-v0.27.4 on the same day. The blog found no information in official sources on when the app will receive the version as an automatic update.
Read more: How an agent works · Agent map