Installation
Install Asagiri and prepare a repository for orchestrated AI workflows.
Installation
Asagiri is a Go CLI that ties together specs, local investigation, git worktrees, external coding agents, and validation commands. The installation path is deliberate: you get a single binary, point it at a repository, and the tool owns the lifecycle of runs, worktrees, and state on disk. This page walks through building or placing that binary, initializing .asagiri/ in a project, and confirming that git, config, and agent commands line up before you run work.
Requirements
| Requirement | Notes |
|---|---|
| Go 1.25+ | Build from source or use a released binary |
| Git | Required for worktrees, status checks, and diffs |
| Configured agents | At minimum, commands referenced in .asagiri/config.yaml (cursor-agent, kiro, ollama, etc.) |
Optional: Ollama for local enrichment or routing, and a Notion token for sync (NOTION_TOKEN).
Homebrew (macOS / Linux)
brew tap LaProgrammerie/tap
brew install asa
asa versionThe formula is published from LaProgrammerie/homebrew-tap when a release tag is pushed.
Manual install (released binary)
Download archives and checksums from GitHub Releases. Archive names follow GoReleaser conventions, for example asa_Darwin_arm64.tar.gz, asa_Linux_x86_64.tar.gz, or asa_Windows_arm64.zip.
VERSION=v0.1.0
curl -LO "https://github.com/LaProgrammerie/asagiri/releases/download/${VERSION}/checksums.txt"
curl -LO "https://github.com/LaProgrammerie/asagiri/releases/download/${VERSION}/asa_Darwin_arm64.tar.gz"
sha256sum -c checksums.txt
tar -xzf asa_Darwin_arm64.tar.gz
sudo install -m 755 asa /usr/local/bin/asa
asa versionReplace VERSION, the archive name, and the install path for your OS and CPU architecture.
Install from source
Clone the repository, build with the project Makefile, and use the binary under bin/:
git clone https://github.com/LaProgrammerie/asagiri.git
cd asagiri
make build
./bin/asa versionAdd bin/ to your PATH, or copy bin/asa into any directory that is already on PATH.
Initialize a repository
From your project root, run asa init. The command scaffolds the local Asagiri surface area so later commands share one config file and one SQLite database.
asa initThis creates:
.asagiri/— config, SQLite state, runs, worktrees.asagiri/config.yaml— copied fromconfig.yaml.examplewhen missing.asagiri/state.sqlite— run and task bookkeeping
Ensure .asagiri/state.sqlite and .asagiri/worktrees/ are listed in .gitignore. init prints a reminder because those paths must not be committed.
Verify setup
After any install path (Homebrew, release binary, or make build), run asa doctor. Doctor exercises git, checks that config exists, confirms agent commands resolve on PATH, and surfaces common misconfigurations before you spend time on a failing work run.
asa doctorFix anything it reports before running work.
Configuration
Copy and edit the example when you need custom agents, budgets, or routing:
cp .asagiri/config.yaml.example .asagiri/config.yamlFor every YAML block and default, see Configuration file.
Next steps
Continue with Quickstart, then walk an end-to-end run in First workflow.