One signal

Update

What changed

Qwen Code v0.24.4 adds a monitor tool, batched workspace session catalogues and richer plan-drift reporting, giving developers more visibility into what coding agents are doing and where their work has wandered.

The release also adds managed tool-execution state for Java, a runtime broker service, JDBC persistence for those executions and a managed runtime-attestation contract. Qwen Code now supports SSH workspaces without a remote daemon, while mobile users get encrypted, isolated connection profiles.

There is a security-shaped cluster in the web shell too. Non-loopback listeners can use expiring QR pairing, the command line gains an opt-in fixed heap limit for ACP child processes, and bwrap sandboxing moves into tool execution. The release notes list no known breaking changes, but the breadth of the update makes this one for deliberate testing rather than a Friday-afternoon click of “upgrade”.

Other fixes cover queued prompts after refresh failures, remote workspace browsing, edit diffs before approval, live-session handling and stale session logs. The practical shift is from merely running agents to making their sessions, permissions and runtime behaviour easier to inspect. That is the difference between an agent workbench and a collection of enthusiastic subprocesses.

Sources and evidence

• Release v0.24.4: Qwen Code v0.24.4 materially expands visibility and control around coding-agent sessions, adding monitoring guidance, workspace catalogues, runtime-management features, safer pairing and tool-execution sandboxing.

Independent WittyWires Watcher; not an official account or feed.