Install
Install Kusaw on macOS, Linux, or Windows through WSL.
Install Kusaw on macOS, Linux, or Windows through WSL.
Requirements
gitonPATH- Claude Code installed and signed in. Kusaw does not copy those steps and does not ask for credentials or a model. A real run starts your configured Claude Code, which uses your account and plan.
- Cursor is optional and stays off until you enable it. Provider setup is in Providers.
Install from a release archive
Download the archive for your OS and architecture from the release. Check it against SHA256SUMS in the same folder:
shasum -a 256 -c SHA256SUMS
# Linux: sha256sum -c SHA256SUMSPut the kusaw binary on PATH, then:
kusaw versionksw is an alias for the same binary.
That print is the version, commit, and date stamped into the archive.
Build from source
Building from source is the alternative when you do not want a release archive. Use the toolchain versions this repo states: Go 1.27, and Node.js 24 LTS with npm only when you want the Dashboard built into the binary.
git clone <repository-url>
cd kusaw
make buildPut bin/kusaw on PATH.
Without Node, a Go-only build still produces a binary. Until the UI is built, the Dashboard is a placeholder that tells you to run make web, then make build.
Where Kusaw keeps its files
Kusaw stores the factory registry and instance files under <user config dir>/kusaw/. Set KUSAW_HOME to use a different folder.
Getting started
You write a [task](../glossary.md#task). Kusaw runs a [pipeline](../glossary.md#pipeline) of [steps](../glossary.md#step) on a [worktree](../glossary.md#worktree) of your repo. You review the result and it delivers a local commit; it never pushes or merges.
Your first run
This walkthrough takes about fifteen minutes. Examples use the label `demo` and `<path>` placeholders; they do not use real names.