Help

Troubleshooting

The problems people hit most, and what fixes each one.

land: command not found

The installer puts land in ~/.local/bin. Add export PATH="$HOME/.local/bin:$PATH" to your shell profile and open a new terminal.

Signing in on a server or over SSH

Run land login, open the link it prints on any device, and if the page shows a code, finish with land login --paste CODE. In CI use a token instead, see CI and GitHub Actions.

The push was rejected

Main moved, or another agent pushed first. Nothing changed on GitHub. Run git fetch origin main, the same land merge, and the new local.push. Never force push either ref.

GitHub blocks direct pushes to main

Allow the account your agents push with, or have them push the result and refs/land/attestations to a branch and open a pull request with it.

The first merges are slow

land records what each test command reads in the background after land add. Until that finishes, every merge runs every command. See Making checks fast.

A test fails only on land

Tests run offline on Linux in a fresh machine, so a test that downloads something, needs a service or depends on your own machine fails there. Install what it needs in .land/setup.sh, and use the repro command from the verdict to run the same check yourself.

dirty in the verdict

A branch's worktree has uncommitted or untracked files. Commit them, then run the same merge again.

no_plan in the verdict

Your free day is over and nothing was checked. Pick a plan on your dashboard and run the same merge again.

It keeps saying running

Run the same command again, that is how you wait. A big suite's first check can take several minutes. If it still says running after much longer than your tests take, tell us.

Still stuck

Write to us from the contact page with the command you ran and the JSON it printed.