Use Landing locally¶

Run a task against your own checkout with Python 3.12 or later, uv, and a POSIX host. You provide the project dependencies and checks. From a Landing source checkout:

uv sync
export LANDING_MODEL="openai:gpt-4.1"
export LANDING_API_KEY="your-provider-api-key"

For another provider or endpoint, see Configuration.

Explain a failure¶

Use an existing UTF-8 failure log and select the project workspace:

uv run landing explain "Explain the failure and suggest the next useful check." --workspace ../project --input check.log

Read whether the answer establishes a cause or proposes a hypothesis. Use triage when you need reproduction evidence and acceptance criteria for a work item. Without a configured platform capability, results stay in the terminal.

Delegate a fix¶

Prepare a disposable checkout or branch you can inspect. State the expected user behavior and supply the check that establishes it:

uv run landing fix "Fix the missing-name behavior: print usage to stderr and exit 2. Preserve valid greetings." --workspace ../candidate --input check.log --check "python acceptance.py" --json --output fix.json

Replace the instruction and check with your actual problem. Fix changes the workspace, then Landing runs the required check. A successful action returns status: completed; failed execution or validation preserves partial changes and any explanation. Inspect the diff and the recorded check before accepting it. Ordinary local execution does not automatically commit or publish.

Review the candidate¶

uv run landing review "Review the candidate against the issue's acceptance criteria." --workspace ../candidate --check "python acceptance.py" --json --output review.json

Landing runs the check before review. A failed check forces block; missing evidence can produce inconclusive. The command exits zero only for a completed review with allow. Review guidance asks the agent to leave the candidate unchanged; configured tool lists filter capabilities but are not a sandbox.

Inspect and continue¶

uv run landing action list
uv run landing action view act_example --json
uv run landing action logs act_example

Replace act_example with an ID from the list. Use the same database as the task; --db or LANDING_DB selects it. Workspace edits remain in the selected checkout. See CLI reference for piping input, cancellation, retries, and exit codes.