Quickstart
Install the CLI, connect a repository and land your first change, in about five minutes.
Before you start
- A git repository on GitHub whose tests run on Linux, in any language.
- Claude Code, Codex or any agent that can run a command. You can also run every step yourself.
- Your first day is free with no card. After that you need a plan from your dashboard.
1. Install and sign in
On the machine your agents run on. The installer signs you in with GitHub and gives Claude Code and Codex the land skill.
curl -fsSL https://useland.dev/install | sh land login
The installer puts land in ~/.local/bin. If your shell says land: command not found, add export PATH="$HOME/.local/bin:$PATH" to your shell profile and open a new terminal. On a server with no browser, see signing in over SSH.
2. Connect the repository
Tests run on plain Debian with no network, so first commit a .land/setup.sh that installs what they need. land runs it once with the network on, and whatever it leaves is the environment.
#!/bin/sh # .land/setup.sh runs once, on plain Debian, with the network on. # Install what the tests need. The tests then run offline. set -e apt-get update -qq && apt-get install -y -qq python3-pip pip3 install --break-system-packages -r requirements-dev.txt
Then, in the repository, name the command that runs your tests. --dry-run shows what would upload, which is committed files only, with no history and never .env.
land add --dry-run --test 'python -m pytest -q' land add --test 'python -m pytest -q'
land runs the tests once and records which already fail, so they never block a merge. More on both steps in Tests and environment.
3. Merge and push
When work on a branch is committed, merge it onto main.
git fetch origin main land merge my-branch --onto main --json
land answers with a verdict. If the branch landed, run the local.push command it prints. It pushes the result together with land's signature, using your own git access.
git push --atomic origin 9e1b…:refs/heads/main refs/land/attestations
If the branch was refused, the verdict names the failing test and a command that reproduces it. Fix the code, commit, and run the same merge again. See Reading a verdict.