Native Qwen lifecycle reporting alongside session restore #2757
yiliang114
started this conversation in
Ideas
Replies: 1 comment
|
The Qwen-side implementation is now available as Draft PR QwenLM/qwen-code#9047. It is intentionally limited to TUI state/session reporting and graceful release, and remains Draft while the paired-owner contract here is unresolved. I did not open a Herdr implementation PR under the contributor policy. A local end-to-end run with the minimal contract change observed |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Herdr now recognizes Qwen Code and persists its session identity through #2743. #2756 shows the remaining lifecycle gap: localized working and approval UIs can still be classified as idle.
Qwen Code has authoritative TUI state for working, blocked, and idle. A native reporter could remove the locale dependency, but the current ownership contract makes session restore and lifecycle reporting mutually exclusive when they use separate sources. Reusing one source would also couple two independent sequence producers and remove screen fallback for prompts not represented by the first reporter version.
Would Herdr support a paired Qwen integration contract with these properties?
This is the only Herdr-side prerequisite for a narrow Qwen TUI reporter. Orchestration and heterogeneous agents stay outside Qwen and continue through Herdr.
All reactions