Land branches from any agent tool

Agent workspaces such as Orca, Conductor, Superset, the Codex app or Claude Code give each agent its own branch. Each branch can pass its own checks and still break when merged with the others. pytxo land checks the combination before any of it reaches your branch.

It needs Pytxo 1.3 or later, Git, and the tools your checks use. It works on Windows, macOS and Linux and does not call any model.

Check a set of branches

From your repository, with the target branch checked out:

pytxo land agent/cart agent/discount --check "npm ci && npm test" --per-input

Pytxo:

1. Resolves each branch and records the files it changed since it split from your branch.
2. For files that more than one branch changed, maps the changes to functions, methods and types with Signal Core. Two branches that changed the same function are reported even when Git merges them cleanly.
3. Merges the branches in the order you gave, in a separate worktree, with Git hooks turned off. A textual conflict blocks the combination.
4. Runs each --check on the combined result, in a fresh worktree where nothing is installed. With --per-input, it first runs the same checks on each branch alone, which shows when every branch passes but the combination fails, and when the check fails everywhere. If every branch passes a check alone and the combination fails it, the check runs on the combination once more: Pytxo blames the combination only when it fails twice, and calls the check flaky when the second run passes. A flaky check still blocks. The receipt records both runs.
5. Decides: ready, blocked or stale, and writes a receipt.

By default this is shadow mode: your branch and working tree do not change. The combined commit is kept at refs/pytxo/land/<receipt id> so you can inspect it:

git log --oneline --graph refs/pytxo/land/<receipt id>

Name the agents

Prefix a branch with a label to record which agent wrote it. Labels appear in the output, the receipt and shared receipts:

pytxo land codex:agent/cart claude:agent/discount -c "npm test"

A pattern expands to matching local branches: pytxo land 'agent/*' -c "npm test".

Land it

When the result is ready, add --apply:

pytxo land codex:agent/cart claude:agent/discount -c "npm test" --apply

• If the target branch is checked out, Pytxo fast-forwards it only if it still points at the commit that was checked. Git refuses if your local changes would be overwritten.
• If it is not checked out (--into release), Pytxo moves it with a compare-and-swap: the update succeeds only if the branch still points at the checked commit.

If the branch moved while the gate ran, the decision is stale and nothing changes. Run the gate again on the new tip.

The landed history contains one merge commit per input, made by your Git identity (or "Pytxo Land" if none is configured). Commits are not signed, even when your Git config signs commits; sign or squash afterwards if your repository requires it.

Read the result

A failed check prints its error lines under it (1.3.1 and later), and a blocked or stale decision ends with the next step. pytxo receipts show <id> has the last 40 lines of each check. --json prints the full receipt. --markdown prints a summary for a pull-request comment.

Options

Checks run in a fresh worktree, so install dependencies inside the check when needed, for example --check "npm ci && npm test".

In a pull request

The repository ships a composite action that runs the gate in shadow mode and prints the Markdown summary to the job log. See Land in GitHub Actions.

Limits

• Pytxo checks what your commands check. Passing checks do not prove the code is right.
• Symbol mapping covers Rust, TypeScript, JavaScript, Python, Go, Java, C/C++ and Ruby. Other files are compared by path only.
• Inputs are merged in the order given; a different order can produce a different result when files overlap.
• The gate does not rebase, squash or resolve conflicts for you.

Every decision leaves a receipt.