fix: Qwen Coder responses not rendering — enhance stream-json parser

[algojogacor]

Summary

The Qwen Coder parser in parseLineWithState shared a minimal code path with opencode that only matched bare text/content/message string fields. Qwen Coder actually outputs a stream-json envelope like Claude (stream_event with content_block_delta/text_delta, assistant messages with tool_use, result with usage metadata). Every structured JSON line was classified as noise and never filled into the source panel — responses only appeared in the log pane.

Root Cause

The agent === "opencode" || agent === "qwen" condition in the parser meant Qwen got the same minimal parsing as opencode, which only handles flat string fields. Qwen Coder's default output format is stream-json with nested structured objects, so the parser's JSON.parse succeeded but none of the field checks matched, returning { kind: "noise" } for every line.

What was fixed

Separated Qwen into its own parser block that handles:

• stream_event → content_block_delta / text_delta (fine-grained streaming text)
• stream_event → content_block_delta / thinking_delta (thinking metadata)
• assistant message with tool_use rescue (HTML from Write/create_file tools)
• assistant message text content (fallback when no stream deltas seen)
• result with usage/duration_ms/total_cost_usd metadata
• Bare text/content/message fields as a last-resort fallback

Testing Done

• Verified the change compiles with the existing TypeScript configuration
• The parser now handles the same JSON envelope shapes as the Claude and Qoder parsers
• Falls back gracefully to bare field extraction when structured content is absent
• No changes to opencode parsing behavior (separated into its own condition)

Related

Fixes #58
Closes #58

[PerishCode]

Thanks for the PR. I checked the current main shape, and I am not going to patch this branch directly yet because this touches the agent stdout parser. That path is easy to regress across agents, so the rebase should land with focused fixtures rather than only a mechanical path move.

Suggested migration to current main:

• Move the parser change from src/lib/agents/argv.ts to next/src/lib/agents/argv.ts.
• Add Vitest coverage under the Next package, for example next/src/lib/agents/argv.test.ts or next/src/lib/agents/__tests__/argv.test.ts.
• Keep Qwen separate from opencode, and include fixtures for:
  • Qwen stream_event text deltas
  • Qwen assistant message text fallback
  • Qwen tool_use / file-write HTML rescue
  • Qwen result metadata
  • opencode flat text / content / message behavior staying unchanged

Recommended validation:

• pnpm install --frozen-lockfile
• pnpm exec tsx scripts/guard.ts
• pnpm -F @html-anything/next typecheck
• pnpm -F @html-anything/next test
• pnpm -F @html-anything/next build

Once the parser fixtures are in place, this should be much easier to review and safely rebase onto the new workspace shape.

[lefarcen]

Hey @algojogacor! 👋 Just checking in — it's been a few days since @PerishCode left their migration guidance, and we haven't heard back from you.

Are you still planning to work on the rebase and Vitest fixtures? To recap the key ask:

• Move the parser change from src/lib/agents/argv.ts → next/src/lib/agents/argv.ts
• Add test fixtures for the Qwen stream_event text deltas, assistant message fallback, tool_use HTML rescue, and result metadata
• Resolve the current merge conflicts with main

Totally fine if life got busy — just let us know if you want to keep this going or if we should re-open the door for someone else to pick it up. Happy to help with any questions about the next/ workspace shape. ❤️