Apothem vs raw Qwen Code config
Hand-maintaining Qwen Code settings, commands, skills, and agents versus rendering them from Apothem's shared profile.
Qwen Code reads settings, hooks, QWEN.md, native Markdown commands,
SKILL.md directories, and Markdown subagents. Apothem renders documented
settings keys from the shared profile and converts shared cohorts into the
Qwen-native filesystem shape where Qwen Code supports one.
Effort comparison
| Task | Raw hand-config | Apothem-managed |
|---|---|---|
| Author rules | Hand-maintain QWEN.md and supporting files | Rendered or referenced from the shared profile |
| Configure hooks | Hand-edit settings.json hook entries | Installed through Qwen Code's native hooks map |
| Author commands, skills, agents | Maintain each Qwen directory by hand | Converted from shared Apothem cohorts |
| Keep cohorts aligned with other harnesses | Manual, per tool | Automatic on apothem update |
| Install / remove the surface | Manual | apothem install / apothem uninstall |
| Verify the config is correct | Manual inspection | apothem verify --harness qwen-code |
What Apothem manages
The qwen-code adapter writes settings.json, installs QWEN.md, converts
Apothem slash commands to Qwen Markdown command files, copies skills into the
native skills surface, adapts helper definitions as Qwen subagents, and
registers Apothem hook dispatchers. Rules, templates, and hook source material
remain under Apothem's support subtree and are referenced from the native
context.
Migration path
- Run
apothem profile initto create the shared profile if you have not yet. - Move existing Qwen Code rules, commands, skills, and agents into the shared corpus.
- Run
apothem install --harness qwen-codeto render the native surface. - Run
apothem verify --harness qwen-codeto confirm the config landed. - Use
apothem update --harness qwen-codefor every later change.