Install
Homebrew (macOS and Linux)
The recommended path — pre-built binaries for both platforms:
brew tap mrgeoffrich/bacio
brew install bacioUpgrade later with:
brew upgrade bacioAfter upgrading, re-run bacio install-skill in any repo you use bacio in so the bundled agent skill picks up doc updates.
Scoop (Windows)
The recommended path on Windows — pre-built bacio.exe, no admin required:
scoop bucket add bacio https://github.com/mrgeoffrich/scoop-bacio
scoop install bacioUpgrade later with:
scoop update bacioAfter upgrading, re-run bacio install-skill in any repo you use bacio in so the bundled agent skill picks up doc updates.
From source (any platform)
bacio is a pure-Go binary — no CGO, no native SQLite dependency:
go install github.com/mrgeoffrich/bacio/cmd/bacio@latestMake sure $(go env GOPATH)/bin is on your PATH.
Verify
bacio --versionAnything that prints a version is fine. If the command isn't found, your shell's PATH doesn't include the install location — brew puts the binary at /opt/homebrew/bin/bacio (Apple Silicon) or /usr/local/bin/bacio (Intel macOS, Linux); go install uses $(go env GOPATH)/bin.
What gets installed
Just one binary — bacio. Everything else (the SQLite database, per-repo skill files) is created on first use:
- The database is created at
~/.bacio/db.sqlitethe first time you run anybaciocommand that needs it. Override with--db <path>. - The canonical agent skill is installed per-repo by
bacio install-skill, which dropsSKILL.mdinto<repo>/.claude/skills/bacio/. - The sync config is created per-repo by
bacio sync initat<repo>/.bacio/config.yaml— only if and when you opt into sync.
Uninstall
brew uninstall bacio # if installed via brew
scoop uninstall bacio # if installed via scoop (Windows)
rm "$(go env GOPATH)/bin/bacio" # if installed via go installTo remove your data as well:
rm -rf ~/.bacio # the database
rm -rf <repo>/.claude/skills/bacio # the agent skill, per repo
rm -rf <repo>/.bacio # sync config, per repoHeads up
~/.bacio/db.sqlite is the only place your kanban data lives. Back it up the same way you back up anything else on your laptop. If you've enabled git-backed sync, the sync repo is a second copy.
