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
- Anthropic researcher: 99% of engineers now run swarms of 300+ self-improving agents — AlishaOutridge · 2026-09-11
- Gergely Orosz: Shipping 10x PRs With AI Agents, Sites Fill With Small Regressions — ducha_aiki · 2026-09-11
- Same Echo Maze prompt, three frontier models: all passed visually but shipped the same hidden bug — eyishazyer · 2026-09-11
- Astra storyboards plus Minimax H3 per-shot generation boost video success rates — Hailuo_AI · 2026-09-11
- Codex tip: use Sol with Astra and Luna sub-agents to save usage — pvncher · 2026-09-11
- agents-best-practices: a provider-neutral Agent Skill for designing and auditing agentic harnesses — tom_doerr · 2026-09-11