Qwen Code preview adds managed sessions, workspace files and tighter agent controls

Qwen Code’s v0.25.3-preview.0 release adds managed sessions and workspace tools, alongside controls for agent permissions and access. It is a substantial preview of changes that could make the coding agent easier to operate, not a stable release to roll out unthinkingly.

Alibaba Qwen Watch analysis

What happened

The release notes list changes across Qwen Code’s managed-agent system, web shell, runtime and command-line tools. Notable additions include managed sessions in the home workflow, resident workspace file sessions, static Skills and extension configuration, and controls for switching shell access and session approvals. The notes also include read-only snapshots of child sessions, live trajectory executions, and opening workspace files from the chat header.

Other listed changes include creating files and deleting folders with confirmation, displaying response token rates when enabled, and stopping a child’s running turn when its parent closes. The full list is in Qwen Code v0.25.3-preview.0’s release notes.

Our top picks

• Managed sessions in the home workflow
  Sessions become part of the main workflow, rather than a feature users have to go looking for.
• Workspace files from chat
  Opening project files from the chat header shortens the hop between an agent conversation and the code it concerns.
• Shell access and approval switching
  Users get controls for changing shell access and session approvals, useful when an agent needs more or less room to act.
• Read-only snapshots of child sessions
  The release adds a way to inspect child-session state without changing it.
• Confirmed file operations
  File creation and folder deletion with confirmation bring useful workspace operations into the web shell, with a pause before deletion.
• Live trajectory executions
  Users can see executions as they happen, giving the agent’s work a more visible trail.

Why it matters

These changes are about the practical shape of using a coding agent: managing sessions, inspecting work and deciding what it can do in a workspace. Better visibility and clear permission controls matter because an agent that can act on files and run shell commands needs more than a confident chat bubble.

Our read

There is enough here to interest people building with or testing Qwen Code, particularly the combination of session management, workspace access and agent controls. But this is explicitly a preview: curious testers have a useful list to explore, while anyone relying on a stable setup can sensibly wait for a finished release.

What to watch

• Which preview features make it into the stable release.
• Whether the new session and permission controls are clear in everyday use.
• How the managed workflow behaves in real projects, beyond the release notes.

Discussion spark: For a coding agent with workspace and shell access, which should come first: smoother managed sessions or stricter, clearer permission controls?

not affiliated with or endorsed by Qwen