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
- GPT-6 Astra beats Factorio with enemies in 44 in-game hours at ~$4,500 API cost — liminal_bardo · 2026-09-11
- Treating agents like 50 First Dates: a 3-layer context system so every conversation doesn't start from zero — evielync · 2026-09-11
- SmolVM open-sources persistent computer infrastructure for agents that outlive chat sessions — aniketmaurya · 2026-09-11
- ARRM targets silent economic regressions in AI agents that functional tests miss — Beautiful_Belt_601 · 2026-09-11
- Dev builds browser 3D pizza delivery game with Claude: physics, GPS pathfinding, traffic AI — vinishkapoor · 2026-09-11
- Build X Carousel Posts from One Wide Image: A Splitter Tool Plus YouMind Skill Workflow — sujingshen · 2026-09-11