Skip to content

chore(skills): sync generated skills #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
github-actions wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(skills): sync generated skills #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .agents/skills/nemoclaw-user-get-started/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -197,7 +197,7 @@ For example, if you picked an OpenAI-compatible endpoint, the summary looks like
Web search: disabled
Messaging: none
Sandbox name: my-gpt-claw
Note: Sandbox build takes ~6 minutes on this host.
Note: Sandbox build typically takes 5–15 minutes on this host.
──────────────────────────────────────────────────
Web search and messaging channels will be prompted next.
Apply this configuration? [Y/n]:
Expand Down
27 changes: 26 additions & 1 deletion .agents/skills/nemoclaw-user-reference/references/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -305,6 +305,23 @@ If neither is found, verify that Colima is running:
$ colima status
```

### Sandbox build is slow or hangs (under-provisioned container runtime)

Default Colima ships with 2 vCPU and 2 GiB of memory, which is not enough headroom for the BuildKit-driven sandbox image build.
On macOS Apple Silicon, the build can stall part-way through with no progress and no error, leaving the wizard waiting indefinitely.

Preflight inspects `docker info` for `NCPU` and `MemTotal` and prints a warning when the runtime falls below 4 vCPU or 8 GiB.
On Colima, raise the resources before re-running onboard:

```console
$ colima stop
$ colima start --cpu 6 --memory 12 --disk 100
```

On Docker Desktop, raise CPU and memory limits in *Settings → Resources*, then apply and restart.

To silence the warning when the host is intentionally small, set `NEMOCLAW_IGNORE_RUNTIME_RESOURCES=1` before running `nemoclaw onboard`.

### Re-onboard fails because port 18789 is held by SSH

After destroying a sandbox and gateway, the SSH port-forward process for the
Expand Down Expand Up @@ -608,7 +625,7 @@ This is expected.
The sandbox's OpenClaw configuration (`/sandbox/.openclaw/openclaw.json`) is baked into the container image at build time.
NemoClaw's sandbox entrypoint installs a guard that intercepts `openclaw config set` and `openclaw config unset` and prints an actionable error, because changes made inside the running sandbox do not persist across rebuilds.

To change your configuration, exit the sandbox and rerun onboarding:
For most configuration changes, exit the sandbox and rerun onboarding:

```console
$ nemoclaw onboard
Expand All @@ -617,6 +634,14 @@ $ nemoclaw onboard
If NemoClaw reports a resumable failed onboarding session, run `nemoclaw onboard --resume` instead.
This rebuilds the sandbox with your updated settings.

For advanced live edits, use the host-side config command instead of running `openclaw config set` inside the sandbox:

```console
$ nemoclaw <sandbox> config set --key <dotpath> --value '<json-or-string>' --restart
```

Host-side `config set` validates any HTTP or HTTPS URLs in the new value, including URLs nested inside JSON objects or arrays. NemoClaw rejects loopback, private, reserved, and internal hosts; DNS names must resolve successfully and must not resolve to private/internal addresses. HTTP URLs are written with the validated IP address pinned to reduce DNS-rebinding risk. Avoid putting credentials in config values; rotate provider credentials with `nemoclaw <sandbox> config rotate-token` instead.

### `openclaw doctor --fix` cannot repair Discord channel config inside the sandbox

This is expected in NemoClaw-managed sandboxes.
Expand Down