Install the CLI
Install the pipeline-kit command once on each developer machine. Then initialize a project in each repo.
From the repository URL
uv tool install git+<this-repo-url>
# or
pipx install git+<this-repo-url>
Replace <this-repo-url> with the git remote for this kit.
From a local clone
git clone <this-repo-url>
cd pipeline-kit
./install.sh
install.sh selects uv or pipx and installs the same pipeline-kit command.
Check it
pipeline-kit --version
Choose a kit before you init
The CLI is the same. The project is one kit or the other.
| Kit | Init | Then |
|---|---|---|
| Kit mode (default) | pipeline-kit init --ide cursor | Work in the IDE via run-workflow |
| Orchestrator mode | uv tool install -e ".[orchestrator]" then pipeline-kit init --mode orchestrator --ide cursor | pipeline-kit run --request "…" |
| Assessment (either kit) | uv tool install -e ".[assess]" and an assess license | pipeline-kit knowledge extract, then pipeline-kit scan |
| Memory bank (either kit, free) | uv tool install -e ".[memory]" from the kit checkout | In the product: memory link, memory index. See Memory |
Read Two kits before you initialize a customer repo. You should not mix modes in one project.
Common commands after that
pipeline-kit init [project] # install/update a project pack
pipeline-kit setup # install/update the user pack
pipeline-kit update [project] # refresh while preserving config.json
pipeline-kit doctor [project] # verify the active pack
pipeline-kit workflows [project] # list available workflows
pipeline-kit uninstall [project] # remove files managed by the kit
The old python3 install.py flags remain for compatibility and for the maintainer-only --sync-kit operation.
Next
- Where you can install — project vs user
- IDE adapters
- First project