Document ncl config changes require restart

features/customization.mdx

@@ -10,7 +10,7 @@
 1. **Code changes** — for behavior baked into the orchestrator (trigger pattern, polling, timeouts)
 2. **Wiring settings** — per-messaging-group config stored in the central DB (engage mode, sender scope, session mode)
 3. **Skills** — for features and integrations (install via `/add-<name>`, uninstall via `git revert`)
 4. **Mount allowlist** — for which host directories an agent can see
 
 ## Philosophy
 
@@ -99,7 +99,7 @@
 MAX_CONCURRENT_CONTAINERS=10 systemctl --user restart nanoclaw
 ```
 
 Or persist in your systemd / launchd service definition.
 
 ## Per-wiring behavior (engage mode, sender scope, session mode)
 
@@ -150,9 +150,9 @@
 
 `CLAUDE.md` is composed at session start — a shared base plus the per-group fragment. Per-group changes don't affect other agent groups.
 
 ## Mount allowlist
 
 Agents only see what you mount. The allowlist lives at `~/.config/nanoclaw/mount-allowlist.json` (outside the project root, never mounted into containers):
 
 ```json
 {
@@ -168,13 +168,33 @@
       "description": "Development project"
     }
   ],
   "blockedPatterns": [],
   "nonMainReadOnly": true
 }
 ```
 
 Per-agent-group mount requests live in `groups/<folder>/container.json`. The host validates each request against the allowlist before mounting. See [Security model](/advanced/security-model) for the full picture.
 
+## Container config changes require a restart
+
+Container config edits made through the agent's admin CLI (`ncl groups config update`) — model, provider, effort, packages, MCP servers — are written to the central DB but do **not** apply to the running container. Restart the agent group for the new config to take effect:
+
+```bash
+ncl groups config update --model claude-sonnet-4-5-20250514
+# After approval: config is saved, container still runs the old model
+ncl groups restart --message "Applying config update."
+# After approval: container restarts with the new config
+```
+
+For package changes (`config add-package`), pass `--rebuild` so the derived image is rebuilt before the container comes back up:
+
+```bash
+ncl groups config add-package --npm some-package
+ncl groups restart --rebuild --message "Installing new package."
+```
+
+Without `--message`, the container is killed but only respawns on the next user message. Use `--message` to force an immediate respawn so the new config is exercised right away.
+
 ## The `/customize` skill
 
 For guided changes without memorizing file paths:
@@ -235,6 +255,6 @@
 ## Related
 
 - [Messaging](/features/messaging) — inbound routing and engage evaluation
 - [Scheduled tasks](/features/scheduled-tasks) — task model and cron
 - [Security](/concepts/security) — sender policies, user roles
 - [Architecture](/concepts/architecture) — two-DB session model