wangjunxiao/nanoclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: explain that CLI config changes require restart

Browse Source 
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
gavrielc
2026-05-09 20:39:24 +03:00
parent 5ba9d23ea8
commit 6539c0286a
1 changed files with 21 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
container/agent-runner/src/mcp-tools/cli.instructions.md
View File

@@ -71,6 +71,27 @@ ncl groups config add-package --npm some-package
ncl members add --user telegram:jane ncl members add --user telegram:jane
``` ```
### Config changes require a restart
Changes made via `ncl groups config update` (model, provider, effort, etc.) are saved to the DB but do **not** take effect on the running container. You must restart for them to apply:
```bash
ncl groups config update --model claude-sonnet-4-5-20250514
# After approval: config is saved but container still runs the old model
ncl groups restart --message "Applying config update."
# After approval: container restarts with the new config
```
Package and MCP server changes (`config add-package`, `config add-mcp-server`) also require a restart. For packages, use `--rebuild` since they're baked into the image:
```bash
ncl groups config add-package --npm some-package
# After approval:
ncl groups restart --rebuild --message "Installing new package."
```
Without `--message`, the container is killed but only comes back on the next user message.
### Tips ### Tips
- Use `ncl <resource> help` to see all available fields, types, enums, and which fields are auto-filled. - Use `ncl <resource> help` to see all available fields, types, enums, and which fields are auto-filled.