Qwen Code issue tracks landing the 1.0 Preview event-driven loop kernel onto main, one surface at a time
qqqys · ghdev · 2026-11-12
A tracking issue in QwenLM/qwen-code (#17045) lays out the plan to land the event-driven agent loop kernel from the v1.0.0-preview line onto main in slices, gradually switching each surface (headless, ACP, Ink TUI, OpenTUI, AgentCore) to run its model rounds and tool batches on the kernel by default.
- Today only headless fully runs on the kernel; other surfaces still call runModelRound/runToolBatch separately, and four events (loop.output, loop.cancelled, etc.) are never published
- Workflow: modules are claimable via comments, the loop contract (AgentLoopHost/runAgentLoop) has one owner at a time, and plan changes are recorded in the issue description
- Deadlines: checkboxes can be added until 2026-11-21; target-dated work needs an owner by 2026-11-14 or gets rescheduled/moved to a follow-up issue
More from coding & agent
- New research tackles the agent experience problem: knowledge trapped in weights — khademinori · 2026-11-13
- YC F26's Acyclic Labs open-sources infra to run 10,000-agent swarms in one session — ycombinator · 2026-11-13
- Floci: free local AWS emulator with 31.6k GitHub stars for faster integration tests — JeremyCMorgan · 2026-11-13
- Open-source REM tool reverse-engineers competitors' ads, SEO and social playbook from one URL — moeinteractive · 2026-11-13
- Codex agent shrinks a 27M-param transformer to 11.46M with equal loss via weight sharing — yoshiyama_akira · 2026-11-13
- Google open-sources Harness²: Agent = Model + Harness, recursive agent harnessing framework — 2C_ornot2C · 2026-11-13