[GH-ISSUE #12] Add Qwen Code #6

Closed
opened 2026-03-04 01:39:10 +03:00 by kerem · 3 comments
Owner

Originally created by @karatechopping on GitHub (Feb 21, 2026).
Original GitHub issue: https://github.com/yigitkonur/cli-continues/issues/12

Is it possible to add Qwen Code as a supported model?

Originally created by @karatechopping on GitHub (Feb 21, 2026). Original GitHub issue: https://github.com/yigitkonur/cli-continues/issues/12 Is it possible to add Qwen Code as a supported model?
kerem closed this issue 2026-03-04 01:39:10 +03:00
Author
Owner

@yigitkonur commented on GitHub (Mar 2, 2026):

hey @karatechopping — qwen code is now supported as of #27 🎉

the parser reads sessions from ~/.qwen/tmp/*/chats/*.jsonl (the standard qwen-code JSONL storage). you can hand off sessions to/from qwen code with all 15 other tools.

after updating (npm i -g continues), try:

continues list --source qwen-code
continues resume

let me know if it works for you!

<!-- gh-comment-id:3986772337 --> @yigitkonur commented on GitHub (Mar 2, 2026): hey @karatechopping — qwen code is now supported as of #27 🎉 the parser reads sessions from `~/.qwen/tmp/*/chats/*.jsonl` (the standard qwen-code JSONL storage). you can hand off sessions to/from qwen code with all 15 other tools. after updating (`npm i -g continues`), try: ``` continues list --source qwen-code continues resume ``` let me know if it works for you!
Author
Owner

@yigitkonur commented on GitHub (Mar 2, 2026):

hey @karatechopping — pushed a follow-up fix in #31 that addresses some critical bugs found during a deep audit against the actual qwen-code source:

  • storage path was completely wrong — was looking in ~/.qwen/tmp/<sha256> but real sessions live at ~/.qwen/projects/<sanitized-cwd>/chats/. parser would've found zero sessions on a real machine
  • resume now uses --resume <sessionId> instead of always --continue (supports specific session resume)
  • added all qwen-code tool names to classification (run_shell_command, grep_search, edit, etc)
  • thought/reasoning extraction, pending tasks, error tracking, diff stats — full feature parity with gemini parser

would you mind giving it a spin and letting us know if sessions are picked up correctly now? 🙏

<!-- gh-comment-id:3986869234 --> @yigitkonur commented on GitHub (Mar 2, 2026): hey @karatechopping — pushed a follow-up fix in #31 that addresses some critical bugs found during a deep audit against the actual [qwen-code source](https://github.com/QwenLM/qwen-code): - **storage path was completely wrong** — was looking in `~/.qwen/tmp/<sha256>` but real sessions live at `~/.qwen/projects/<sanitized-cwd>/chats/`. parser would've found zero sessions on a real machine - **resume now uses `--resume <sessionId>`** instead of always `--continue` (supports specific session resume) - added all qwen-code tool names to classification (`run_shell_command`, `grep_search`, `edit`, etc) - thought/reasoning extraction, pending tasks, error tracking, diff stats — full feature parity with gemini parser would you mind giving it a spin and letting us know if sessions are picked up correctly now? 🙏
Author
Owner

@yigitkonur commented on GitHub (Mar 2, 2026):

update: all review feedback from #27 has been addressed in #32 (merged). qwen code parser now uses zod validation, defensive timestamps, dedup, and proper tree path reconstruction. @karatechopping let us know if you hit any issues

<!-- gh-comment-id:3986993017 --> @yigitkonur commented on GitHub (Mar 2, 2026): update: all review feedback from #27 has been addressed in #32 (merged). qwen code parser now uses zod validation, defensive timestamps, dedup, and proper tree path reconstruction. @karatechopping let us know if you hit any issues
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cli-continues#6
No description provided.