Skip to content

docs: update Qwen daemon Mode B roadmap#131

Merged
wenshao merged 3 commits into
wenshao:mainfrom
chiga0:codex/update-qwen-daemon-mode-b-roadmap
May 15, 2026
Merged

docs: update Qwen daemon Mode B roadmap#131
wenshao merged 3 commits into
wenshao:mainfrom
chiga0:codex/update-qwen-daemon-mode-b-roadmap

Conversation

@chiga0

@chiga0 chiga0 commented May 15, 2026

Copy link
Copy Markdown
Contributor

Summary

  • resets the Qwen daemon roadmap around Mode B (qwen serve) as the mainline and moves Mode A (qwen --serve) into a parking lot
  • updates stage status with the latest upstream state: #3889, #4113, #4160 merged; #4156 held; #4132 still a web/debug validation surface; remote-control stack deferred
  • clarifies that clients connect to the daemon HTTP/SSE API, while EventBus remains an internal fan-out primitive behind a typed event contract
  • reprioritizes client adaptation as TUI → channels → web/debug → IDE, with remote-control after primary clients converge
  • adds compatibility/merge principles: each PR must be independently mergeable, additive, feature-gated where needed, and non-breaking for existing TUI/channels/IDE/CLI paths
  • aligns overview, architecture, HTTP API, deployment/client, permission, roadmap, and README docs with the same stage model

Validation

  • git diff --check
  • Attempted npm ci / docs build, but this environment does not have npm in PATH; only bundled node is available.

@chiga0

chiga0 commented May 15, 2026

Copy link
Copy Markdown
Contributor Author

Follow-up after checking the latest upstream 06-roadmap.md on wenshao/codeagents@3bf3d92 and the latest comments on QwenLM/qwen-code#3803.

The earlier version of this PR had the same mainline direction, but the execution order could be read differently from upstream's newest P0/P1/P2 roadmap. I pushed d7d51be to make the relationship explicit:

  • Same mainline: Mode B first, remote-control deferred, Mode A not part of the current active Mode B client-convergence path.
  • Aligned execution priority: P0 is the remaining production must-haves plus daemon-side state CRUD; P1 is shared contract / bridge primitives and behind-flag client adapters; P2 is remote-control / Mode A revisit.
  • Clarified that this PR's 1.5b / 1.5c / 1.5d / 1.5e labels are workstreams, not a strict serial order.
  • Downgraded TUI/channels/web/IDE adapter work from “P0 migration” to behind-flag trials; default client switching must wait for P0/P1 foundation.
  • Updated README / overview / deployment / permission docs so they no longer conflict with the latest #3803 status or the upstream roadmap.

This should make the PR additive to the upstream roadmap instead of replacing it with a competing stage plan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants