Docs
Getting started
Install Anvil, open a project, and take one issue round: a thread works on it, opens a change, and the change lands. About ten minutes, most of it the agent's.
1. Install
Download Anvil for your platform from the download page, or run the install line. It's the same on macOS and Linux:
curl -fsSL https://anvil.nate.rip/install.sh | sh
and in PowerShell on Windows:
irm https://anvil.nate.rip/install.ps1 | iex
Either way you get the app, the anvil command, and a node: the part of Anvil that runs threads and checks, and keeps running when the window is closed.
2. Sign in to an agent
Threads run an agent you already use. Anvil finds Claude Code, Codex and Copilot CLI where they're installed and signed in; if none is, it says which to install. Each project can pick its default, and each thread can pick its own.
3. Open a project
Anvil lists every git repository in the folders you tell it about, ~/code/* for example. Open one, or clone from your team's forge:
anvil clone team/harbor
A project you open for the first time gets a Lead: a thread that reads the project and its history, and is there to ask what's going on in it.
4. File an issue
Write what's wrong, as you would for a colleague. The Lead reads it, finds where it lives in the code, and says what it would do:
anvil issue new --project harbor "Upload retries give up after one 503"
Tell the Lead to go ahead, or start the thread yourself from the issue. The thread works on a branch of its own, on this machine or another one with room (see Machines).
5. Review the change
When the thread is done, its change opens with its proof: what's true now, screenshots, the checks that ran, and a link to try it. Read that, comment on any line you want different (the thread answers with a commit), and merge when you're happy. The issue closes with it.
Next
Set up your forge so your team shares the project, add checks, and cut a release.