PytxoIntroduction
Pytxo is a reviewed commit layer for the coding agents you already use.
Pytxo is a reviewed commit layer for developers who already run multiple coding agents on substantial repos and are hitting collisions, unsafe writes, or vendor fragmentation.
It schedules the agents you already use (Claude Code, Codex, Cursor CLI, or any shell command). Overlapping path claims wait for a later wave. Eligible Orbit and Galaxy runs prepare isolated changes for Run Review before Apply.
Pytxo is not an IDE or a managed cloud workspace. Keep your editor. Connect through the local MCP hub, or use Pytxo Desktop for Work, History, and Setup.
Today the commit boundary is one repository root: Pytxo prepares exact bytes, checks affected-path state, and journals Apply. The longer-term direction is to extend the same contract to production effects with effect-bound authority, independent verification, and explicit recovery. Production API enforcement is not currently shipped.
The sixty-second story
- Three agents start one feature.
- Two would edit overlapping paths.
- Pytxo detects the conflict before execution.
- Independent work runs together in isolated copies.
- The conflicting task waits for the next wave.
- Pytxo prepares the exact changed bytes for review.
- You Apply that package, or refresh it if an affected path has moved.
At a glance
- Isolated copies until you approve (Blast)
- Overlapping path claims wait in later waves (Race)
- Structural code skeletons instead of whole files when Signal is on (fewer tokens; savings vary by repo)
- Mixed CLIs under one local scheduler (BYOK)
- Optional Desktop: what is running, what needs you, what is sandboxed
Who this is for
| You want to... | Start here |
|---|---|
| Install, then run one natural-language mission | Install → First mission |
| Apply a prepared package | Desktop setup → Run Review |
| Fix doctor / trust / MCP issues | Troubleshooting |
| Prove collisions are detected before agents run | Collision demo |
| Review and approve from a desktop UI | Desktop setup → History → Run Review |
| Drive Pytxo from Cursor later | MCP from Cursor |
| Look up commands and config | CLI reference, pytxo.toml |
Secondary surfaces (workspaces, fleets, Hypervisor Shell TUI) stay available once the mission loop is clear. Start with mission → collision dry-run → approve.
Quick mental model
Mission or pytxo.toml → wave plan (Race) → agents in isolated copies (Blast)
↓
you approve → flush to real repoRead What is Pytxo? for the full picture, or jump to Install.