Qwen Code’s 0.24.7 release adds managed-workspace and agent-session capabilities alongside a long list of fixes. For developers building with Qwen Code, the notable shift is more control over how agent work is organised and how sessions behave, rather than a single headline feature.
Alibaba Qwen Watch analysis
What happened
The Qwen Code project published version 0.24.7 on 29 September. Its release notes list features spanning managed agents, runtime tools, session handling, memory and the web shell, as well as fixes across the CLI, MCP and other components. The v0.24.7 release notes are the project’s account of what changed.
Our top picks
- Managed workspaces for agents
The release adds workspace-bound sessions, private Workspace execution and managed Workspace selection in the web shell. - More deliberate tool and session handling
Managed tool-result contracts and local result storage add structure to how agent work is recorded and retrieved. - Paired-engine session support
ACP bridge changes add workspace runtime identity for paired channels and support recovery of quarantined channels. - Structured memory retrieval
New memory features cover structured scans, bounded retrieval and on-demand recall. - A commit command in the CLI
The new /commit command can draft commit messages with AI, bringing a common developer task into the command-line workflow.
Why it matters
Taken together, these changes make Qwen Code look more like a workspace for managing ongoing agent work, not just a CLI that accepts a prompt and runs a tool. Workspace-bound execution, session recovery and more structured memory could be useful for developers juggling several agents or longer-running tasks. The release notes describe implementation changes, but don’t establish how these features perform in everyday use.
Our read
There’s enough here to merit more than a drive-by version number. The most interesting changes are the ones that put clearer boundaries around where agent work happens and how it survives interruptions. The release notes are detailed, though the practical verdict will depend on how smoothly these capabilities fit real projects. Agent infrastructure is rarely glamorous; then again, neither is recovering a lost session at 5pm.
What to watch
- How workspace-bound sessions behave in everyday development.
- Which managed-agent features are enabled by default and which need configuration.
- Whether the memory changes make retrieval more useful without adding friction.
- What developers report about the new CLI and paired-engine workflows.
Discussion spark: Would you trust a coding agent with workspace-bound execution on a real project, or keep it confined to a separate sandbox?
Sources and evidence
- Release v0.24.7 (29 September 2026, 14:02 UTC)
not affiliated with or endorsed by Qwen