Galaxy approvals

On the Galaxy permission tier, Pytxo pauses high-risk agent actions until you approve or deny them. That covers destructive shell commands and merging isolated copies back into your real tree.

At a glance

Approvals queue is per repo (execution domain)
Pending requests survive restarts (hitl.json under .pytxo/data/)
Approve from CLI, Hypervisor Shell, or Pytxo Desktop
Orbit and lower tiers skip spawn gates; Galaxy enforces them

What triggers approval

Examples of commands that require approval under Galaxy:

Recursive deletes (rm -rf ...)
git push
Docker invocations
Network fetches (curl, wget)
Merge / flush of agent changes into the physical repo

CLI

List pending requests:

pytxo hitl list

Approve or deny:

pytxo hitl approve hitl-0
pytxo hitl deny hitl-1

Hypervisor Shell

When approvals are pending, the board highlights them. With an empty prompt:

Tab: cycle selection
a: approve
x: deny

Pytxo Desktop

The Approvals panel lists pending actions with the domain they belong to. Tap Approve or Deny without switching repos manually when multiple domains have open requests.

Troubleshooting

pytxo doctor

Look for the hitl_persistence check. It verifies the domain can write approval state to disk.

Permission tiers: when to use Galaxy vs Orbit
Blast Shield: isolated copies and approve-to-merge
Folder trust: pick a tier when you first open a repo