Install or refresh OneCLI as NanoClaw's gateway provider. Use when setup selects OneCLI, an existing OneCLI-backed install is migrated to the gateway seam, or its runtime, approval bridge, setup, and agent guidance must be restored from the in-tree package.
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
This skill owns the full OneCLI integration. NanoClaw core supplies the generic gateway seam and existing skill engine.
Copy the package's native adapter, tests, and agent guidance into their normal NanoClaw paths. NanoClaw core owns the approval workflow.
payload/src/gateway-providers/onecli-files.ts -> src/gateway-providers/onecli-files.ts
payload/src/gateway-providers/onecli-files.test.ts -> src/gateway-providers/onecli-files.test.ts
payload/src/gateway-providers/onecli-chatgpt-stub.ts -> src/gateway-providers/onecli-chatgpt-stub.ts
payload/src/gateway-providers/onecli-chatgpt-stub.test.ts -> src/gateway-providers/onecli-chatgpt-stub.test.ts
payload/src/gateway-providers/onecli.ts -> src/gateway-providers/onecli.ts
payload/src/gateway-providers/onecli-provider-credentials.ts -> src/gateway-providers/onecli-provider-credentials.ts
payload/src/gateway-providers/onecli-provider-credentials.test.ts -> src/gateway-providers/onecli-provider-credentials.test.ts
payload/src/gateway-providers/onecli.test.ts -> src/gateway-providers/onecli.test.ts
payload/src/gateway-providers/onecli-install.test.ts -> src/gateway-providers/onecli-install.test.ts
payload/container/skills/onecli-gateway/SKILL.md -> container/skills/onecli-gateway/SKILL.md
payload/container/skills/onecli-gateway/instructions.md -> container/skills/onecli-gateway/instructions.md
payload/docs/onecli-upgrades.md -> docs/onecli-upgrades.mdThe provider file makes the only product registration call. It translates OneCLI sessions and native approval events into the generic contract.
import './onecli.js';@onecli-sh/sdk@2.2.1The setup script safely reuses a healthy existing installation, installs the pinned local gateway when absent, or uses NANOCLAW_ONECLI_API_HOST and NANOCLAW_ONECLI_API_TOKEN for a remote gateway.
This integration supports exactly the gateway version pinned in .claude/skills/add-onecli/versions.json (onecli-gateway, today 1.45.0; not the versions.json at the project root). It uses the agent grants API, which OneCLI added in 1.44; older gateways do not have it, and OneCLI 2.x is not supported. Setup reuses an existing gateway without checking its version: follow Upgrading the OneCLI gateway to check it and to move it to the pin. The CLI (onecli-cli, which needs 2.9 or later for onecli agents grants) and SDK (onecli-sdk) have their own pins.
pnpm exec tsx .claude/skills/add-onecli/scripts/setup.tsProvider skills such as /add-opencode store model credentials here through the
gateway seam. An agent group's OneCLI agent holds only the secrets attached to it.
NanoClaw records the id of each model credential its provider setup saves (setup's
Claude key, /add-codex, /add-opencode, /add-cursor) in data/onecli/provider-credentials.json,
by provider. On every spawn it attaches the recorded credentials for the provider
the group runs, if the agent does not hold them yet; this also covers a new group,
a group that switched provider, and a login saved after the group existed. For
an install that saved credentials before ids were recorded, the first spawn per
provider also adopts, once, the secrets NanoClaw's setup saves, by name
(Anthropic, Codex, OpenCode …, Cursor). After that only recorded ids count: a
re-run of the provider's login records a credential it finds or saves.
Every other secret and every app connection is opt-in: the skill that adds it
attaches it to the groups you choose, and new groups do not get it. To grant one
by hand: onecli agents grants attach-secret --id <agent-id> --secret-id <secret-id>
(onecli agents list --max 0 maps the group id, shown as identifier, to
<agent-id>). Attaching adds one secret and leaves the agent's other grants alone;
detach-secret takes it away. Verify with onecli agents grants list --id <agent-id>;
the gateway can take up to a minute to apply a change. Do not put a key in .env,
command arguments, or the container environment.
ONECLI_URL and ONECLI_API_KEY.pnpm run buildpnpm exec vitest run src/gateway-providers/onecli-files.test.ts src/gateway-providers/onecli-chatgpt-stub.test.ts src/gateway-providers/onecli-install.test.ts src/gateway-providers/onecli-provider-credentials.test.ts src/gateway-providers/onecli.test.ts src/gateway-providers/gateway-provider-registry.test.ts src/gateway-approval-coordinator.test.tsThe setup consumer writes NANOCLAW_GATEWAY_PROVIDER=onecli only after every directive above succeeds. Claude authentication is then completed through scripts/auth.ts; credentials never enter an agent container.
During an atomic NanoClaw upgrade, scripts/detect.ts identifies an older implicit OneCLI installation so the generic updater can preserve that choice before the service restarts.
A gateway on another host must hand agents its own address in GATEWAY_BASE_URL. OneCLI 1.45 defaults it to host.docker.internal:10255, the agent's own machine, so with a remote gateway every model call hangs with no reply. When setup was pointed at a remote gateway (NANOCLAW_ONECLI_API_HOST), this check reads the proxy address the gateway hands agents. It never fails the install.
pnpm exec tsx .claude/skills/add-onecli/scripts/proxy-check.ts || echo '{"warn":"no","hint":"none"}'When that address is host.docker.internal, a loopback address or a wildcard address, show the user the exact GATEWAY_BASE_URL=<host>:<port> line to set on the gateway host, and point them at "Remote gateway" in Upgrading the OneCLI gateway:
{{proxy_hint}}nanocoai/nanoclaw
dad1aad
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.