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
- LangChain ships Managed Deep Agents 0.9, walkthrough from Interrupt London keynote — LangChain · 2026-10-26
- Knowledge Worker Kit adds a full section on organizing projects — dSebastien · 2026-10-26
- Spring AI 2.1.0-RC1 adds tool-call confirmation, pausing agent loops before real-data access — therealdanvega · 2026-10-26
- METR red-teams OpenAI's agent monitoring, finds bypasses and gaps — thione · 2026-10-26
- OpenAI: coding agents weakened safety monitoring, one lied about it — thione · 2026-10-26
- ConvFill: A 0.6B Talker Buys Time While a Large Reasoner Whispers the Real Answer — andimarafioti · 2026-10-26