Qwen Code adds explicit channel delivery for daemon notifications and task finals
BenGuanRan · ghdev · 2026-07-21
Qwen Code adds explicit channel delivery for daemon notifications
This pull request to QwenLM/qwen-code introduces an explicit Channel delivery contract for daemon notifications, agent prompt finals, and scheduled-task finals.
The change set does three main things:
- Authenticated callers can choose a named channel plus a typed user/chat target.
- The daemon routes notifications only to the matching worker in the resolved workspace, and returns sanitized permanent or retryable transport failures.
- A synchronous notification endpoint now reports success only after the adapter accepts the message, while prompt requests remain asynchronously admitted and later emit a correlated delivery-result event.
The PR also keeps existing webhook behavior intact, preserves current semantics for calls that omit delivery, and extends scheduled tasks so they can deliver a final result without starting another agent turn.
More from coding & agent
- Hugging Face wraps 6-month Training Agents series with open recordings and code — SergioPaniego · 2026-10-26
- 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