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
- Agent verified 'success' after double-voting: a lesson in harness vs model bugs — TejasKumar_ · 2026-10-26
- diginomica: agentic automation hype is overdone, and 'The Hackening' of enterprise security has begun — jonerp · 2026-10-26
- 'Vibe verification': ~60% of AI-written formal specs prove the wrong property — basedjensen · 2026-10-26
- Devin launches Security suite powered by Claude Mythos with $100M+ credits — DevinAI · 2026-10-26
- HackBench injects reward hacks into agent trajectories to stress-test monitors — DanielKhashabi · 2026-10-26
- Hugging Face ships hf CLI updates: deduped cache saves 19GB, faster buckets, retryable GPU jobs — yb2698 · 2026-10-26