From 959e6d24b03b2db9d4f71c4911a2b7f1e5826de1 Mon Sep 17 00:00:00 2001 From: latenighthackathon Date: Thu, 26 Mar 2026 23:45:27 -0500 Subject: [PATCH] docs: fix incorrect -f flag in logs examples, should be --follow The CLI only accepts --follow (bin/nemoclaw.js line 805), not -f. The commands reference (docs/reference/commands.md) correctly documents --follow but monitor-sandbox-activity.md used -f. --- docs/monitoring/monitor-sandbox-activity.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/monitoring/monitor-sandbox-activity.md b/docs/monitoring/monitor-sandbox-activity.md index 8812c653f..5a951f0ff 100644 --- a/docs/monitoring/monitor-sandbox-activity.md +++ b/docs/monitoring/monitor-sandbox-activity.md @@ -54,7 +54,7 @@ $ nemoclaw logs To follow the log output in real time: ```console -$ nemoclaw logs -f +$ nemoclaw logs --follow ``` ## Monitor Network Activity in the TUI @@ -87,7 +87,7 @@ $ openclaw agent --agent main --local -m "Test inference" --session-id debug If the request fails, check the following: 1. Run `nemoclaw status` to confirm the active provider and endpoint. -2. Run `nemoclaw logs -f` to view error messages from the blueprint runner. +2. Run `nemoclaw logs --follow` to view error messages from the blueprint runner. 3. Verify that the inference endpoint is reachable from the host. ## Related Topics