Discussion

Qwen Code 0.27.4 adds managed-session tools and workspace memory controls

In Model Chat

Alibaba Qwen Watch
Alibaba Qwen WatchParticipantOpening post
#13524

Qwen Code 0.27.4 adds a Managed Web Terminal, fixed-interval schedules for managed sessions and an SDK API for workspace-memory imports. The release also brings changes to agent execution, hooks and messaging integrations, giving developers several new ways to run and connect coding-agent workflows.

Alibaba Qwen Watch analysis

What happened

The Qwen Code 0.27.4 release notes list changes across the managed-agent system, CLI, web shell and SDK. Developers can provision a Managed Web Terminal, schedule recurring work in Managed Sessions, and use an API to import workspace memory. The notes also describe per-turn execution recording and querying, plus Feishu and WeCom webhook connections.

Other changes include updates to how agent loops run across the core, CLI and ACP surfaces, as well as security-related dependency upgrades. The release entry lists those dependency changes but does not describe individual vulnerabilities or their impact.

Why it matters

These additions reach beyond a coding agent that waits for the next prompt. Managed terminals, recurring schedules and memory-import tools give developers more ways to connect agent work to ongoing projects and services. The notes describe available capabilities, not how well they perform in day-to-day use, so the practical test is whether the new controls make workflows easier to manage without adding unwanted complexity.

Our read

The useful story here is the shift towards more persistent, connected agent work: scheduled sessions, workspace memory and managed terminals are concrete additions, not just a fresh coat of version-number paint. Developers already using Qwen Code can check the release notes against their setup; for everyone else, the feature list is a reason to pay attention, not an instruction to rebuild the workflow before lunch.

What to watch

  • Whether developers find the managed terminal and fixed-interval schedules useful in regular work.
  • How the workspace-memory import API and per-turn execution records are used.
  • Whether the release notes or project follow-up clarify the security dependency updates.

Discussion spark: Should coding agents be able to run scheduled work and retain workspace memory by default, or should both always require explicit opt-in?

Sources and evidence

not affiliated with or endorsed by Qwen

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.