Integration · Qwen Code · T4

Qwen Code as a T4 Handoff Destination | Reinstate

Qwen Code is T4: a read-only local index, a handoff source, a handoff destination, and same-vendor native resume through the vendor's own CLI. A handoff into Qwen starts a new session and is never a cross-agent resume. Reinstate does not sync Qwen sessions.

Last verified
Current release
v0.6.0-rc.6
Release status
v0.6.0-rc.6 candidate · stable remains v0.5.1 · v0.6.0-rc.5 tagged Windows run (plus two same-artifact rechecks) ended FAIL (211/4/0/0 of 215), zero product defects, grok:E1-E3 live-backend-connectivity plus a grok version drift to 1.0.13 and an H7 digest-equality-unmeasurable gap the four PARTIAL rows · this candidate widens the verified Grok Build range to 1.0.13 and refines the H7 live-home check to per-file listing with attribution · native Windows tagged-artifact acceptance pending, macOS deferred

Qwen Code support at a glance

Tier
T4 Handoff destination
Storage family
F1 home tree
Verified version range
0.21.12 – 0.23.0
Encrypted sync (T5)
Not supported

T4 means rein handoff <session> --to qwen starts a new Qwen Code session with qwen --session-id <uuid>, on top of the T3rein resume qwen:<id> (qwen --resume <id>) and the T2rein handoff --from qwen. Qwen Code is not a T5 sync agent.

What T4 includes

  • T1 read-only discovery, search, and inspect of local Qwen Code sessions.
  • T2 structured handoff from Qwen Code into a new Claude Code or Codex session.
  • T3 same-vendor rein resume (qwen --resume <id>) andrein fork (qwen --resume <id> --fork-session).
  • T4 structured handoff into Qwen Code via qwen --session-id <uuid>. That starts a new session and is never a cross-agent resume: Reinstate does not reconstruct source history in Qwen.
  • A bounded qwen --version probe with a fail-closed range of 0.21.12 – 0.23.0.
  • Fail-closed behavior on an unrecognized layout or version (exit code 5).

What T4 excludes

  • No rein push / rein pull of Qwen sessions.
  • No write into Qwen Code's session store.
  • No resume of an id Qwen does not recognize: an unknown --resume id exits1 with the vendor's own "No saved session found" message rather than opening a picker.

Native resume is same-vendor: it launches Qwen's own CLI (qwen --resume) against Qwen's own session.

A handoff starts a new destination session in either direction. It does not reconstruct vendor history or translate a transcript between vendors.

Qwen Code ships a managed self-updater, so one machine can answer --versiondifferently depending on which install root is in scope; the verified range spans the bundled and the self-updated build observed on this host. A newer self-update outside that range reports UNTESTED rather than being assumed compatible.

Evidence

Committed fixtures live under testdata/sessionindex/qwen andtestdata/handoff/qwen, and the version range was measured from the real binary. The resume journeys T3 rests on and the destination journey T4 rests on are both recorded, on macOS and on native Windows (2026-08-22). See theQwen storage pageand the tier matrix.