Pytxo

Permission tiers

DeepSpace, Orbit, Galaxy, and Supernova capability ladder.

Pytxo uses local permission profiles to gate filesystem, network, and tool capabilities per agent. Set globally, per [[agent]], or per modular project root.

ProfileIntent
deep_spaceMost restrictive: air-gapped bubble, minimal host access
orbitDefault: balanced local development with isolated copies
galaxyHost tools plus human approval for risky commands and merges
supernovaHighest local capability (use deliberately)
permission_profile = "orbit"

[[agent]]
name = "scout"
permission_profile = "deep_space"

Capability matrix (shipping)

CapabilityDeepSpaceOrbitGalaxySupernova
Read repoAgent cwd focusFull repoFull repoFull repo
WritesEphemeral / denied flushWorktree or overlay; approve flushPhysical writes; HITL for destructive / flushUnrestricted cwd = repo
Network at spawnDeniedDefault deny for fetch toolsLocal service ports + HITL on egress toolsAllowed
Host secrets (.ssh, global .env)StrippedFiltered child envPartial inheritFull inherit
Docker / git push / rm -rfNoLimited / spawn policyAllowed with HITLAllowed
Max Signal fidelityLowConfig defaultConfig defaultConfig default

Shipping enforcement is spawn-time policy, env sanitization, worktree/overlay isolation, and Galaxy HITL queues. It is not a full syscall sandbox on every platform.

Galaxy in practice

When you trust a folder as Galaxy:

  • Risky spawn commands (rm -rf, git push, docker, network tools) pause until you approve
  • Merging agent changes into your real tree requires approval
  • Pending requests persist across restarts (hitl.json under .pytxo/data/)
pytxo hitl list
pytxo hitl approve hitl-0

Folder trust

The first time you open a repo in the Hypervisor Shell, you pick a tier. See Folder trust.

Permission profiles are not the same as signal_fidelity (context compression tier).

Ultra metering ([billing] with mode = "ultra") is a separate commercial layer. BYOK remains the default. See Ultra.

On this page