Qwen Code adds GitHub, GitLab, and Gitea polling adapters for agent workflows
OrbitZore · ghdev · 2026-07-20
Qwen Code adds polling adapters for GitHub, GitLab, and Gitea
A PR in QwenLM/qwen-code introduces three polling channel adapters so agents can continuously watch code hosting platforms for tasks.
What it adds
- GitHub, GitLab, and Gitea adapters that poll notification/todo APIs on a configurable interval.
- Each notification becomes a message envelope with chatId = repository and threadId = issue/PR/MR.
- Agent responses are posted back as comments.
- Poll cursors are persisted under /.qwen/channels/ for restart recovery.
- Same-timestamp deduplication uses an in-memory ID set.
Important design detail
- The cursor still advances, and notifications are marked read, even if handleInbound fails.
- That prevents infinite reprocessing loops.
- Docs were added for each adapter plus a new “Polling Channels” section.
- Example configs require groupPolicy: "open"; otherwise notifications are silently dropped.
The PR frames these adapters as the sensory layer for issue-driven agent workflows.
More from coding & agent
- First-ever Three.js Conference lands in Paris, with a panel on AI-shortened design workflows — OdinLovis · 2026-09-11
- Data engineering, not agent frameworks, is the real bottleneck for enterprise AI agents — dhruv2038 · 2026-09-11
- RTK Terminal Compression Cuts Tokens but Leaves Your AI Coding Bill Unchanged — Bartaseth · 2026-09-11
- GPT-6 Astra beats Factorio with enemies in 44 in-game hours at ~$4,500 API cost — liminal_bardo · 2026-09-11
- Investment Analyst Asks How to Build a Claude-Based Diligence Agent Stack — Careless_Tie2286 · 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