Qwen Code
Make a project follow an instruction in Qwen Code: one command writes its hooks, and a new version arrives at your next prompt. The same setup for other tools, and how each one takes a new version, is on Other coding agents.
At a glance
| How it follows | hooks |
|---|---|
| A new version arrives | at your next prompt |
| Set up | one command |
| Checked against | Qwen Code v0.28.1-preview.0, against its source |
| Systems | Wherever the tool and Node.js 20.19 or later run |
What you need: Node.js 20.19 or later, the instruction.md package
(npm i -g instruction.md, 0.11.0 or later) and @instruction.md/agents 0.4.1 or later, which
instruction agents … runs. Every instruction agents … command also runs, without installing
anything, as npx -y @instruction.md/agents …, and every instruction … command as
npx -y instruction.md ….
Set up
In your project's folder, signed in (instruction login), run:
instruction agents follow instruction://acme/support-agent@stable --host qwen-code --write It writes, merged into what is already there:
.instruction/follow.json: the instruction the project follows. Commit it..instruction/.gitignore: keeps the fetched copy (current.md),state.jsonandgiven/out of git..qwen/settings.json: the hooks. Commit it.
{
"hooks": {
"SessionStart": [
{
"matcher": "startup|resume|clear|compact",
"hooks": [
{
"type": "command",
"command": "npx -y @instruction.md/agents hook qwen-code",
"timeout": 10
}
]
}
],
"UserPromptSubmit": [
{
"hooks": [
{
"type": "command",
"command": "npx -y @instruction.md/agents hook qwen-code",
"timeout": 5
}
]
}
]
}
} Qwen Code runs a project's hooks once you approve them or trust the folder.
What happens
Qwen Code runs hooks the way Claude Code does: the instruction's whole text when a session starts (also after a compaction), and a new version at your next prompt.
Qwen Code escapes < and > in what a hook adds, so the text arrives between plain marker lines (--- instruction … ---) instead of tags.
The MCP server
Qwen Code reaches instruction.md through the instruction command's stdio server. instruction connect --host qwen-code <uri> prints:
// .qwen/settings.json — Qwen Code reaches instruction.md through this CLI's stdio server
{
"mcpServers": {
"instruction-md": {
"command": "npx",
"args": [
"-y",
"instruction.md",
"mcp",
"--follow",
"instruction://acme/support-agent@stable",
"--url",
"https://instruction.md/mcp"
]
}
}
}
// sign the bridge in once: npx -y instruction.md login
// to give every session this instruction, and a new version at the next prompt: npx -y @instruction.md/agents connect --host qwen-code instruction://acme/support-agent@stable --with-hooks --write Caveats and what isn't verified
- What a hook adds reaches the model in the conversation, not in the system prompt.
Check it worked
Run the hook by hand, as the tool would at that event. It prints what the tool receives: the instruction's whole text the first time, and nothing when you run it again right away, because a session gets each version once.
echo '{}' | npx -y @instruction.md/agents hook qwen-code --event SessionStart --dir . Then start a new session and ask which instructions it follows. Once a session has read it, .instruction/current.md holds the copy the hooks keep, and the instruction's Agents card counts the follower under this tool.
Stop following
- Remove the entries that run
@instruction.md/agents hook qwen-codefrom.qwen/settings.json. - Delete
.instruction/follow.json, or the whole.instruction/folder.
If it doesn't work
| What you see | Why | What to do |
|---|---|---|
| Running the hook by hand prints nothing | No .instruction/follow.json in the folder or above it, up to the repository's root; or it gave this version moments ago | Run the setup in the project's folder, or pass --dir. A version the session already has isn't given again: nothing is wrong |
instruction.md: couldn't read …; this session goes on without it | Offline, not signed in, or the address is wrong, and there is no copy yet | instruction login, then check the address in .instruction/follow.json |
instruction.md: a newer version of … is held (…) | The new version's signature doesn't check out, and the follow file asks for one | Nothing to do on this machine: the session keeps the version it has. See How following works |
| A private instruction isn't read | The command isn't signed in | instruction login (--device on a machine without a browser) |
| Still stuck | Ask us |
Related
- Other coding agents: every tool at a glance
- How following works: the follow file, the hooks, offline behaviour
- Gemini CLI
- Antigravity
- GitHub Copilot CLI
- Live updates