signal insight

Qwen Code revives its Chrome extension through daemon-direct architecture

Qwen Code is reviving its Chrome extension as a thin client connected directly to the local `qwen serve` daemon over HTTP and server-sent events. The change replaces the older native messaging path and positions the daemon as Qwen Code’s universal local API surface.

Published Jun 28, 2026 Updated Jun 28, 2026 1 sources

QwenQwen Codeagentsfeature updatemedium impact

agentsbrowser-extensionai-coding-toolsdeveloper-toolsdaemonfeature_update

Impact: medium
Confidence: 84%
Change type: feature update
First seen: Jun 28, 2026
Last updated: Jun 28, 2026
Audience: developersAI agent buildersbrowser automation teams
Status: Ready

Summary

Qwen Code is reviving its Chrome extension as a thin client connected directly to the local qwen serve daemon over HTTP and server-sent events. The change replaces the older native messaging path and positions the daemon as Qwen Code’s universal local API surface.

What changed

Qwen Code PR #5777 proposes a daemon-direct Chrome extension architecture built on the qwen serve local daemon.

Why it matters

Browser integration is becoming a practical requirement for coding agents that need to inspect docs, apps, and web workflows. A daemon-direct design can reduce integration friction and make browser tools another client of the same agent runtime.

Evidence excerpt

Agents Radar highlighted PR #5777 as reviving the Chrome extension via a daemon-direct architecture, with side panel chat connecting to qwen serve over HTTP and SSE.

Sources

github.com