First mission

You do not need to hand-write [[task]] rows to try Pytxo. One mission becomes an owned task plan, isolated agent work, and an immutable package for review.

Who this is for

You already run more than one coding agent on a real repo and care about write collisions, unsafe merges, or scattered logs. If you only ever use a single agent session, start with Install and skip ahead only when that pain appears.

Prerequisites

• pytxo on PATH (npm i -g pytxo@1.2.1 or a release binary)
• At least one coding agent CLI on PATH (Claude Code, Codex, Cursor CLI, or OpenCode)
• A git repo you are willing to trust at Orbit (or higher)

cd my-project
pytxo trust orbit
pytxo agents

Run a mission

pytxo mission "Add input validation to the public API and update unit tests"

Pytxo will:

1. Detect available agents
2. Propose tasks, paths, and execution stages (waves)
3. Show predicted path overlaps and isolation mode in plain language
4. Ask Approve mission? [Y/n] (use --yes to skip)
5. Run agents in isolated copies of the repo (Blast)
6. Keep overlapping path claims in separate waves (Race)
7. Run any suggested verify commands
8. Persist the run contract and prepare an immutable review package

Preview only (no dispatch):

pytxo mission "…" --json

After the run

Open Pytxo Desktop → History, select the run, and Review package. Run Review is the reviewed-package Apply surface for Orbit and Galaxy. It shows the exact prepared additions, modifications, and deletions. Before Apply, Pytxo checks the current preimage of every affected path; unrelated dirty files are allowed. A changed affected path marks the review stale.

The hitl command manages Galaxy approval requests only:

pytxo hitl list
pytxo hitl approve <id>
# or use Pytxo Desktop → History → Review package → Apply

These commands do not initiate Apply. Orbit has no Galaxy HITL step; Orbit users review and Apply the prepared package in Run Review.

Reviewed Apply covers Orbit and Galaxy in one execution domain and one repository root. DeepSpace is non-flushable. Supernova writes directly to the host tree.

Without agent CLIs

Prove scheduling and isolation with the collision demo using --cmd echo (no paid model keys).

Learn more

• Collision demo
• CLI reference
• Three moats