PytxoWhat is Pytxo?
Pytxo coordinates the coding-agent CLIs you already use. It assigns task paths and dependencies, runs agents in isolated workspaces, records the effective permission boundary, and prepares exact repository changes for review.
This is Pytxo's first commit layer: a controlled boundary between an agent proposal and a real repository mutation. The broader product direction applies the same idea to production systems, but external effect gateways and adapters are not shipping features.
The problem
Many agent products put the UI first: grids of terminals, heavy local resource use, and platform-held credits. Vendor control centers (for example GitHub Copilot's agent app) solve supervision inside one ecosystem. If you care about mixed CLIs on your machine, you need coordination, isolation, and clear logs more than another IDE surface.
How Pytxo works
Pytxo schedules headless agents in the background on your machine. Each agent works in an isolated workspace. For an eligible Orbit or Galaxy run, Pytxo stores an immutable package for one repository root. Run Review shows that package, and Apply reads only its stored target blobs. Your IDE stays your IDE. You connect through MCP and, optionally, Pytxo Desktop.
| Typical agent workspace UI | Pytxo | |
|---|---|---|
| Primary UI | Multi-pane terminal grid | Your existing IDE |
| Execution | Remote containers / heavy webviews | Local agents + isolated copies |
| Parallelism | Visual panes | Scheduled waves + write registry |
| Telemetry | Streamed terminal text | Structural logs + optional Desktop |
| LLM keys | Often platform-held | Your keys (BYOK) |
Ways to scale up
- Many projects at once. Each repo gets its own logs and permission tier (default Orbit). See Execution domains.
- Workspaces. One workspace can attach several folders for coordinated planning and execution. Each repository root keeps its own Apply boundary. See Modular projects.
- Fleet runs. Cross-repo plans can order work across separate Git roots; they do not provide a cross-root Apply transaction. See Fleet runs.
What Pytxo does not do
- Multi-pane embedded terminal walls in the product UI
- Store provider API keys in plaintext
- Become an LLM vendor (Pytxo Cloud is BYOK-only)
- Claim production API enforcement, cross-system atomicity, or universal rollback
Next
- Three moats: smarter context, safe sandbox, no write collisions
- Pytxo Desktop: optional control UI
- Galaxy approvals: you approve risky actions