Quickstart
Install ivar, create a hall, and open your first discovery session in Claude Code or OpenCode.
Install ivar, create a hall, and open your first discovery session on a repo you own. Fifteen minutes, one repo, nothing to undo afterwards.
Before you start
- git, and read access to at least one repo you can clone.
- A harness — Claude Code or OpenCode. Pick the one you already work in; the steps below are the same either way.
- Remote auth.
ivar repo addclones through your existing git remotes. For GitHub it reads a token from the GitHub CLI, so rungh auth loginfirst, or export$GITHUB_TOKEN/$GH_TOKEN.
Nothing leaves your machine
ivar is a single binary that never talks to a server. It clones from the
remotes you already use and writes only inside the hall directory.
Install
Fetches the release binary for your platform and verifies its checksum.
curl -fsSL ivar.run/install | shVerify
ivar --versionIf the shell cannot find ivar, the install directory is not on your PATH.
Start a new shell, or add it.
Pick a harness
Choose the agent you work in. The steps are the same either way; only the harness and the init flag differ.
Claude Code
Create a hall and open your first discovery session in Claude Code.
OpenCode
Create a hall and open your first discovery session in OpenCode.
What you will end up with
A directory that is itself a git repo, holding a committed ivar.json and an
.ivar/ working area. Commit the hall and a teammate gets the same repos on the
same branches with git clone and ivar sync — no second setup document to
keep current.
One hall, or several?
A hall is cheap: it is a directory with a manifest. Teams usually keep one per product area, holding the repos that change together — not one per developer, and not one for the whole company.