Use when the user wants to choose or change which model plans, implements or reviews Superwiki tasks (opus, sonnet, gpt and so on), add task areas, see the Superwiki configuration, or invokes sw-config or sw:config.
Installs into .claude/skills of the current project.
Are you the author of Sw Config?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/mhmtsrfglu-sw-config)
---
name: sw-config
description: Use when the user wants to choose or change which model plans, implements or reviews Superwiki tasks (opus, sonnet, gpt and so on), add task areas, see the Superwiki configuration, or invokes sw-config or sw:config.
---
# sw-config
Settings live in `docs/.sw/config.json`. Change them with the script, from the project root; it also writes the agent files that make a model choice take effect. `<skill-dir>` is this skill's directory.
```bash
node <skill-dir>/scripts/config.mjs show
node <skill-dir>/scripts/config.mjs model plan claude opus
node <skill-dir>/scripts/config.mjs model implement claude sonnet
node <skill-dir>/scripts/config.mjs model review codex gpt-6
node <skill-dir>/scripts/config.mjs model plan copilot --unset
node <skill-dir>/scripts/config.mjs areas "M=Mobile,B=Backend"
node <skill-dir>/scripts/config.mjs sync --tools claude,codex,copilot
```
## Models
A model is chosen per role and per tool, because each tool can only run its own models.
| Role | Does | Used by |
| --- | --- | --- |
| `plan` | writes the plan file for a task | sw-plan |
| `implement` | does the work of a task | sw-implement |
| `review` | reviews the implementation from a clean context, for tasks whose frontmatter has `review:` | sw-implement |
No tool lets a skill change the model of the running session, so the skills hand the work to a subagent, and the subagent's file carries the model. The script writes one file per role:
| Tool | Folder | Files |
| --- | --- | --- |
| Claude Code | `.claude/agents/` | `sw-planner.md`, `sw-implementer.md`, `sw-reviewer.md` |
| Codex | `.codex/agents/` | `sw-planner.toml`, `sw-implementer.toml`, `sw-reviewer.toml` |
| Copilot CLI | `.github/agents/` | `sw-planner.agent.md`, `sw-implementer.agent.md`, `sw-reviewer.agent.md` |
When the user asks to set a model:
1. **See what is set**: `show`.
2. **Settle role, tool and model.** Ask only for what is missing. If they name a model without a tool, infer the tool from the model family and say which you chose. Use the model name exactly as that tool spells it; do not translate names between tools.
3. **Change only what differs.** If the role already runs that model, change nothing and say so. A tool's short name and the full name of its current version (`opus` and the newest Opus) are the same model: do not rewrite one into the other.
4. **Run the `model` command** and show its output.
5. **Say when it takes effect**: a tool picks up new agent files when its next session starts.
After Superwiki itself is updated, run `sync` once: the roles' instructions are part of the agent files.
Do not edit the generated agent files or `config.json` by hand; the next `sync` overwrites agent files.
## Areas
`areas` adds prefixes or renames them. It never removes one: tasks keep their ids forever.
