Set ownership before dispatch
Turn one mission into explicit tasks, paths, owners, dependencies, execution waves, and verification.
Coordinate coding agents. Review one result.
Assign paths and dependencies, run agents in isolated workspaces, then approve the exact package prepared for one repository root.
npm i -g pytxo
Works with the tools you already use.
Review one prepared result before it reaches your repository
Set path ownership before dispatch. After the run, inspect the exact package, permission evidence, and Apply history in Flow.
Review the prepared package
Inspect the base revision, package digest, permission profile, enforcement receipt, ownership DAG, and exact additions, edits, and deletions.
Apply exactly what you reviewed
For an Orbit or Galaxy run, Pytxo revalidates affected paths and applies only the stored package within one execution domain and one repository root. A process crash is reconciled from its journal.
Real agent readiness
Keep the accounts you already trust
Pytxo coordinates agent processes without becoming another credential vault. Connect through each official CLI, recheck its redacted status, then choose a ready agent in Flow.
- Agent sessions stay vendor-ownedChatGPT connects through Codex. Claude, Cursor, Gemini, and OpenCode keep their own sessions.
- API billing stays separateDeepSeek and other direct providers use an explicit environment-variable reference for the selected run.
- Readiness checks are non-billablePytxo checks installed CLIs and redacted session state without sending a model request.
Controls around repository changes
Pytxo starts reads from syntax structure, isolates agent writes, assigns path ownership, and prepares one package for review.
Signal Core
Structure before source
Starts reads with AST skeletons (signatures, types, and imports) so agents pull full source only when the task needs it.
82.9%measured scaffold-byte reduction across 185 tracked production files; model-token and task impact are not measured
Learn moreBlast Shield
Prepared changes, one Apply
Orbit and Galaxy keep writes isolated. Within one execution domain and one repository root, Pytxo stores target blobs, validates affected paths, and journals Apply.
Race Shield
Schedule overlapping paths in order
Path claims and dependencies become execution waves, so tasks that touch the same area do not run as independent work.
Fits the tools you already use
Keep your editor, agent accounts, and provider keys. Add the coordination layer around them.
Mission planning with Flow
Compose a mission, review tasks, paths, permissions, agent assignments, and waves, then dispatch the approved plan.
Learn moreFlow and Run Review
Track active work and history in Flow. Run Review shows the package, exact file changes, policy evidence, recovery state, and Apply history.
Learn moreYour agents keep their sessions
Codex, Claude Code, Cursor, Gemini, OpenCode, and generic commands stay vendor-owned while Pytxo coordinates execution.
Learn moreWorkspaces and fleet runs
Coordinate folders for planning and execution, or order separate repositories in a fleet. Each repository root keeps its own Apply boundary.
Learn moreOne local orchestrator behind every surface
Desktop and the CLI read the same persisted run contract: plan, permission profile, enforcement receipt, prepared package, and Apply state.
Editor or terminal
Cursor, VS Code, or shell
MCP hub
Optional local IDE bridge
Orchestration
Rust: projects, permissions, waves
Execution yard
Claude Code, Codex, and other CLIs
Pytxo Desktop
OptionalFlow, Run Review, operations, and recovery
Install once. Run agents in parallel.
CLI for orchestration. Optional Desktop for Focus, Ops, approvals, and diffs.
npm i -g pytxo