Qwen Code moves ACP runtime ownership from sessions to the workspace
ytahdn · ghdev · 2026-07-20
What this PR changes
This PR moves qwen serve lifecycle ownership from the last active session to the registered workspace runtime.
Main behavior changes
- ACP lifecycle and capability state now belong to the workspace, not the most recent session.
- channelIdleTimeoutMs is optional; omitting it disables automatic ACP idle reaping.
- A value of 0 is no longer accepted; use a positive timeout for compatibility cleanup or omit the option for persistent ownership.
- qwen serve no longer preheats the primary ACP child by default, so the first request can pay the cold-start cost.
- A daemon may keep one ACP child per live workspace, which is a memory/process tradeoff operators may need to tune.
Why it matters
Extensions, MCP, Skills, and tool management need a stable owner even when no chat session exists. The workspace runtime now serves that role, while sessions become consumers of the reusable runtime.
Test plan
The PR verifies that a registered workspace can be prepared without creating a session, that runtime state persists across later sessions, and that cleanup follows the configured workspace lifecycle.
More from coding & agent
- NVIDIA says Nemotron 3 Ultra hit 97.1% on agentic RTL chip-design tasks — NVIDIAAI · 2026-07-27
- Tokyo Agent Forge hackathon shipped production-ready AI agents in one day — DavidBennett__ · 2026-07-27
- Long-running agents will need immutable event logs, this thread argues — sebpaquet · 2026-07-27
- Agentic Data Science in Practice: Agents Write Code but Answer Wrong Questions — hugobowne · 2026-07-27
- A VS Code extension adds Markdown-style highlighting to Alchemy string templates — samgoodwin89 · 2026-07-27
- Claude’s Stripe MCP connector is being called unusable after repeated disconnects — evielync · 2026-07-27