A desktop app for Qwen Code
AgentVera opens the qwen command in a real terminal and binds each Qwen Code agent to its own session. The role is appended to Qwen’s system prompt, and AgentVera’s MCP servers come along on every launch.
Qwen Code in AgentVera
- Command
qwen- Install
npm i -g @qwen-code/qwen-code- Sign-in
- Qwen Code uses its own login (Qwen OAuth or an API key); the agent’s terminal asks on first launch.
- Model
- Left empty, Qwen Code’s default model is used; a chosen model is passed with --model.
- Effort
- Qwen Code has no effort levels.
- Role
- The role is appended to Qwen Code’s system prompt (--append-system-prompt).
- Session resume
- Each agent starts with a session id from AgentVera (--session-id); a saved session opens with --resume.
- MCP and browser
- AgentVera’s MCP servers and browser are passed with --mcp-config.
What every agent gets
Side-by-side panes
The agent opens in the same grid as the project’s other agents; the layout is remembered per project.
Flows
When the agent finishes a turn, its reply goes through a template to another agent; turn limits stop loops.
Automatic code review
When a turn ends, the code it wrote is reviewed by the Claude model you pick, with findings linked to file:line.
Telegram notifications
Finished turns, errors and flows waiting for approval reach your phone; reply to message the agent.
Queue and broadcast
Queue a message while the agent is busy, or send one message to the agents you pick.
Picks up where it left off
An agent that has received a message returns to its conversation when the app reopens.
Questions
Can each Qwen Code agent have its own role?
Yes. Each agent’s role is appended to its own system prompt.
Can Qwen Code use the AgentVera browser?
Yes. The AgentVera browser and MCP servers are added to Qwen Code on every launch.
Other agents
All agentsBring your Qwen Code agents into one window.
Download AgentVera, add a project folder and pick Qwen Code under New agent.