Qwen Code security on your Mac
Excellent for Mac is free to scan. It reads Qwen Code's logs and shows what it did. With Pro, it checks each action in sessions started after that. A session started with --safe-mode or --bare isn't checked.
Works with Qwen Code
Trademarks belong to their owners; no endorsement implied.
What Excellent sees
Excellent reads Qwen Code's session logs in ~/.qwen on your Mac, with the folder each session worked in.
It shows what was done: your email sent to websites or typed into forms, keys sitting in logs, secrets files read, history overwritten, checks skipped. Each finding says which agent and where.
With Pro, while the app runs, it reads Qwen Code's logs as they grow, and sends you a notification when something new needs you.
Its key finder checks Qwen Code's settings and .env for keys.
What it can stop Pro
This needs Excellent Pro. Free and Pro says what each does.
Turn on protection, and Excellent adds one entry to ~/.qwen/settings.json, keeping every other setting, after backing the file up. Qwen Code runs it before each action.
It blocks your email on its way to a website, an API key typed into a command, deleting a folder you marked never-delete, and switching Excellent off.
It asks you first before a force push to main, skipping git hooks, typing your email into a web form, or writing over a file you marked never-delete.
Two more rules are off until you turn them on: asking before reading keys and .env files, and asking before breaking a rule you wrote in CLAUDE.md or AGENTS.md.
You can stop a Qwen Code session from Excellent's menu. Its actions are refused until you press Continue or End. End stops its process and the commands it was running.
Excellent can also pause a session by itself when it breaks one of four rules: sending your email to a website, deleting or moving a never-delete folder, reading a never-open file, or overwriting history on main. Setup asks about this, with all four ticked.
Tested in Qwen Code 0.27.4 on a Mac: the check Turn On adds ran there, refused what it should, and let a harmless command through.
Your rules
Sharing works between Claude Code and Codex. Qwen Code doesn't get your rules from it.
With Pro and Remind agents of my rules on, the check refuses an action that would break a rule you wrote in CLAUDE.md or AGENTS.md once, and quotes your rule. Reminders are off by default.
The sandbox Pro
Excellent's sandbox covers Claude Code and Codex. Qwen Code gets the live check only.
What isn't covered
- Qwen Code reads its hooks when a session starts. A session that was running when you turned protection on isn't checked until you restart it.
- A session started with
--safe-modeor--bareruns without hooks, and Excellent can't tell. - Excellent's sandbox doesn't cover Qwen Code, so nothing backs the check up there.
- The check reads what a command says. An agent set on getting around it sometimes can.
- A script file run by an interpreter, like
python3 cleanup.py, isn't read by the check.
Set it up
- Get the Mac app. It needs an Apple silicon Mac and macOS 14 or later. Protection needs Pro.
- With Pro, open it and press Protect My Agents. It lists what it will change first, then adds its check to
~/.qwen/settings.json. Turn On in the menu does the same later. - Restart any Qwen Code session that was already running.
Install the Mac appTurn on protectionStop or pause an agentThe agents it supports
The other agents
Protect Qwen Code on your Mac
Get the Mac app