From 1c032eeb08a2e2d2340ac7d3e218fa7a3a96773a Mon Sep 17 00:00:00 2001 From: Ivo Stoynovski Date: Sun, 3 May 2026 09:00:28 +0000 Subject: [PATCH] fix: update existing CLI instead of re-installing during setup - check if openkbs CLI is already installed before running install.sh - run openkbs update to sync CLI binary and skill files when pre-installed Co-Authored-By: Claude Opus 4.6 --- SETUP.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/SETUP.md b/SETUP.md index 5368240..9d26f77 100644 --- a/SETUP.md +++ b/SETUP.md @@ -182,13 +182,17 @@ Tell the user: Run each step and report the result before moving on: -1. Install the OpenKBS CLI: +1. Install or update the OpenKBS CLI: ```bash - curl -fsSL https://openkbs.com/install.sh | bash + if command -v openkbs &>/dev/null; then + openkbs update + else + curl -fsSL https://openkbs.com/install.sh | bash + fi ``` - This downloads a single binary to your PATH — no sudo, no system - changes. It's from the same `openkbs.com` domain you'll be deploying - to, so it's the same trust boundary. + If the CLI is already installed, `openkbs update` refreshes the + binary and project skill files. Otherwise, `install.sh` downloads a + single binary to your PATH — no sudo, no system changes. 2. Authenticate: ```bash openkbs login