From 6539c0286a5e1e53bb403b886fd96e1d2ed28da1 Mon Sep 17 00:00:00 2001 From: gavrielc Date: Sat, 9 May 2026 20:39:24 +0300 Subject: [PATCH] docs: explain that CLI config changes require restart Co-Authored-By: Claude Opus 4.6 (1M context) --- .../src/mcp-tools/cli.instructions.md | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/container/agent-runner/src/mcp-tools/cli.instructions.md b/container/agent-runner/src/mcp-tools/cli.instructions.md index 6a4f72e..63a8674 100644 --- a/container/agent-runner/src/mcp-tools/cli.instructions.md +++ b/container/agent-runner/src/mcp-tools/cli.instructions.md @@ -71,6 +71,27 @@ ncl groups config add-package --npm some-package 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 - Use `ncl help` to see all available fields, types, enums, and which fields are auto-filled.