third/nanoclaw
1
0
Fork 0
mirror of https://github.com/qwibitai/nanoclaw.git synced 2026-06-04 10:14:47 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: move restart guidance into config help descriptions

Browse Source 
One-liner in cli.instructions.md pointing to `ncl groups config help`.
Each config operation's description now says whether restart or rebuild
is needed — agent discovers it via progressive disclosure.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
gavrielc
2026-05-09 20:40:54 +03:00
parent 05906e4b6a
commit 0287d71595
2 changed files with 12 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
container/agent-runner/src/mcp-tools/cli.instructions.md
+2 -19
View File
@@ -71,26 +71,9 @@ ncl groups config add-package --npm some-package
ncl members add --user telegram:jane
```
### Config changes require a restart
### Important
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.
Config changes via `ncl groups config update` do not take effect until `ncl groups restart`. Run `ncl groups config help` for details.
### Tips