From 7f6298a1bbc0d9354cd0d584f6e573d54e159e33 Mon Sep 17 00:00:00 2001 From: NanoClaw Setup Date: Thu, 19 Mar 2026 12:00:03 +0000 Subject: [PATCH] fix: add onecli CLI to PATH if not found after install Co-Authored-By: Claude Opus 4.6 (1M context) --- .claude/skills/setup/SKILL.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/.claude/skills/setup/SKILL.md b/.claude/skills/setup/SKILL.md index b83cf61..2f8d821 100644 --- a/.claude/skills/setup/SKILL.md +++ b/.claude/skills/setup/SKILL.md @@ -69,7 +69,16 @@ curl -fsSL onecli.sh/install | sh curl -fsSL onecli.sh/cli/install | sh ``` -Verify both installed: `onecli version`. If the command is not found, the install script may have printed a path — add it to PATH or use the full path. +Verify both installed: `onecli version`. If the command is not found, the CLI was likely installed to `~/.local/bin/`. Add it to PATH for the current session and persist it: + +```bash +export PATH="$HOME/.local/bin:$PATH" +# Persist for future sessions (append to shell profile if not already present) +grep -q '.local/bin' ~/.bashrc 2>/dev/null || echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc +grep -q '.local/bin' ~/.zshrc 2>/dev/null || echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc +``` + +Then re-verify with `onecli version`. Point the CLI at the local OneCLI instance (it defaults to the cloud service otherwise): ```bash