PytxoArchitecture
Pytxo follows a three-tier model:
Presentation -> Orchestration -> Execution
(Pytxo Desktop) (pytxo-orchestrate) (pytxo-runner + PTY)
^ ^
passive telemetry MCP / CLICrates
| Crate | Role |
|---|---|
pytxo-cli | User-facing commands |
pytxo-orchestrate | Scheduling, hypervisor, doctor |
pytxo-runner | Agent execution, worktrees, PTY |
pytxo-core | Config, tasks, billing types, moat interfaces |
pytxo-store | SQLite schema and event log |
pytxo-mcp | MCP server for IDE integration |
Data flow
- CLI or MCP submits a run plan from
pytxo.toml - Orchestrator computes waves (path conflicts +
depends_on) - Runner spawns agents in worktrees, streams events to SQLite
- Optional Pytxo Desktop reads store for topology UI
Moat routing
All new orchestration features should route through Signal Core, Blast Shield, and Race Shield. Do not bypass them.
See repo layout for directory map.