Live sessions on every surface
Watch every Qwen Code prompt, tool call, and diff stream in real time — desktop, web portal, iOS and Android. The session runs on your machine; the view follows you.
Your agents. Your environment.
Alibaba's Qwen coding assistant. Glueprint runs Qwen Code over the Agent Client Protocol it already speaks — adding live sessions on every device, approvals from your phone, parallel worktrees, schedules, and memory.
Your provider account. Your code. A workspace to bring them together.
Qwen Code is an agentic coding tool developed by Alibaba's Qwen team that lives in the terminal. It edits code, runs commands, creates commits, analyzes codebases, and implements features from natural language descriptions. It offers IDE integrations for VS Code, Zed, and JetBrains, surfaces in Telegram, WeChat, DingTalk, and GitHub Actions, and provides an Agent SDK in TypeScript, Python, and Java. The tool is model-flexible via provider configuration, supporting Qwen models and OpenRouter, with MCP integration for external tools.
Alibaba's Qwen coding assistant.
Qwen Code connects over the open Agent Client Protocol. One generic adapter implements the protocol's client side, so Qwen Code gets the same surfaces as every other harness.
Everything below works with the Qwen Code CLI you have today — no migration, no new account for the model, no lock-in. Uninstall Glueprint and your terminal workflow is exactly as it was.
Note
Best forTerminal-centric developers building on Qwen models with broad IDE and SDK reach.
Set up the integration on each machine where the agent will run.
On each execution host, open Settings -> Agents -> Browse ACP catalog and choose Qwen Code.
Glueprint installs the registry distribution for Qwen Code, starts it, and completes the ACP initialize handshake.
Choose Qwen Code from a project or worktree and use the capabilities reported by that installed build.
The process stays on its host. Remote access follows your Glueprint plan and the capabilities of the installed agent.
Help with agent setupGlueprint adds the workspace around the agent. Its provider account and configuration stay with the CLI.
Glueprint finds the Qwen Code binary you installed and spawns it, then speaks the Agent Client Protocol — JSON-RPC 2.0 over stdio — to drive it. Same CLI, same authentication; Glueprint just wraps the session.
Message chunks, tool calls, and tool-call updates from Qwen Code arrive as protocol notifications and render as the same live, typed timeline every Glueprint session gets — watchable from desktop, browser, or phone.
When Qwen Code asks to write a file or run a command, the protocol's permission request surfaces as an inline approval card on whatever device you're holding. Approve, deny, or auto-allow per tool.
Because Qwen Code speaks ACP, adding it is a catalog entry, not an engineering project — the same adapter runs every other agent in the registry, so you can tile them side by side.
Some features come from Glueprint. Others depend on what the installed agent supports or reports when it connects.
| Capability | Status | Behavior |
|---|---|---|
| Terminal agent from Alibaba's Qwen team | Runtime | Confirmed when the installed agent connects. |
| Edits code, runs commands, creates commits | Runtime | Confirmed when the installed agent connects. |
| Agent SDK in TypeScript, Python, and Java | Runtime | Confirmed when the installed agent connects. |
| MCP integration and OpenRouter provider support | Runtime | Confirmed when the installed agent connects. |
| IDE extensions for VS Code, Zed, and JetBrains | Runtime | Confirmed when the installed agent connects. |
Check the connected agent for its available models, modes, and permissions. Learn about ACP
Credentials and model access follow the provider. Glueprint brings the surrounding work into one place.
Glueprint surface
Watch every Qwen Code prompt, tool call, and diff stream in real time — desktop, web portal, iOS and Android. The session runs on your machine; the view follows you.
Glueprint surface
Permission prompts arrive as approval cards wherever you are. Kick off a refactor at your desk, approve the file writes from the couch.
Glueprint surface
Run several Qwen Code sessions side by side, each in its own git worktree, with diffs, history, and a three-pane conflict resolver alongside.
Glueprint surface
Tile Qwen Code next to Claude Code, Codex, and the rest of the ACP fleet in the Command Center. The protocol differs; the surface doesn't.
Glueprint surface
Promote it to an assistant: persona, constitution, long-term memory, and a daily journal on disk, loaded into every wake.
Glueprint surface
Wake it on cron: triage the inbox every 30 minutes, sweep PRs at 9am, run the nightly cleanup. Quiet hours and watermarks prevent re-fires.
Glueprint surface
Messages, sessions, and output tokens computed from session logs — compare Qwen Code against Claude Code, Codex, and your other ACP agents.
Glueprint surface
Remote viewing rides AES-256-GCM envelope encryption. The relay routes; it cannot read.
Yes. Qwen Code is registered in the official Agent Client Protocol registry, and Glueprint implements the protocol's client side. It spawns the Qwen Code CLI you already installed and drives it over JSON-RPC 2.0 — adding live sessions, inline approvals, worktrees, and remote control.
No. Glueprint doesn't resell model access. Qwen Code authenticates exactly the way its vendor designed — its own login, subscription, or API key. Glueprint spawns the binary and speaks the protocol; it doesn't sit between you and the model provider.
Sessions always run on your machines — a laptop, a desktop, or a server with the headless daemon. The iOS and Android app streams Qwen Code sessions live, lets you send follow-ups, and handles permission approvals from anywhere.
Yes — that's the point. Each harness is an adapter; sessions from all of them tile into the same Command Center, share the same task boards, and roll up in the same per-harness analytics.
Yes. Remote viewing routes AES-256-GCM-encrypted envelopes through the relay, which stores a wrapped key it cannot open — decryption happens on your devices. On the free local tier, session content never leaves your machine at all. See security.
Qwen Code · Registry version 0.25.3; Apache-2.0; capabilities are validated on the execution host.
Agent information is sourced from Qwen Code's official site.
AG-409 The local tier is free
Download once, run on your hardware, scale up to teams when you're ready. No credit card.