From 82ffce14742e2d5b4771a2d7c2ab044764a3ca10 Mon Sep 17 00:00:00 2001 From: chengyongru Date: Tue, 30 Jun 2026 14:17:07 +0800 Subject: [PATCH] docs: move restart mode docs to gateway config --- docs/configuration.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/configuration.md b/docs/configuration.md index 5e030da7..8ef04260 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -191,8 +191,6 @@ These variables are process-level switches. Set them in the same terminal, servi Internal variables such as `NANOBOT_RESTART_*` and `NANOBOT_PATH_*` are set by nanobot itself and are not a supported user configuration surface. -For Windows service wrappers such as WinSW or nssm, set `gateway.restartMode` to `exit` so `/restart` exits and lets the service manager perform the restart. The default `auto` uses `spawn` on Windows foreground runs and `exec` elsewhere. - ## Langfuse Observability nanobot can trace OpenAI-compatible provider calls through Langfuse's OpenAI SDK wrapper. This is configured with environment variables, not `config.json`. @@ -1976,6 +1974,7 @@ The heartbeat job is backed by the same cron service as user-created reminders. | `gateway.heartbeat.enabled` | `true` | Register the built-in heartbeat cron job on gateway startup. | | `gateway.heartbeat.intervalS` | `1800` | Seconds between heartbeat checks. | | `gateway.heartbeat.keepRecentMessages` | `8` | Number of recent heartbeat-session messages to retain after each run. | +| `gateway.restartMode` | `auto` | Restart strategy for `/restart`: `auto` uses `spawn` on Windows foreground runs and `exec` elsewhere. Use `exit` with Windows service wrappers such as WinSW or nssm so the service manager owns the restart. | ## Subagent Concurrency