Skip to content

fix: update existing CLI instead of re-installing during setup #18

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

Merged
ivostoynovski merged 2 commits into from
May 12, 2026
Merged

fix: update existing CLI instead of re-installing during setup #18

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1c032ee
fix: update existing CLI instead of re-installing during setup
ivostoynovski May 3, 2026
3159f00
Merge branch 'main' into fix/handle-existing-cli
ivostoynovski May 12, 2026
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
14 changes: 9 additions & 5 deletions SETUP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down