how diffs work
the host watches your repo for changes. when an AI agent writes code, the host detects the diff, classifies it with tree-sitter (Go, Dart), and streams it to your phone as a diff card with a risk score. you accept or reject. accept stages the change; reject restores the original. undo reverses either decision.
troubleshooting
run pseudocoder doctor first -- it checks host health, TLS certs, and network reachability.
- can't connect: verify Tailscale is running on both devices, or that you're on the same LAN. run
pseudocoder host status. - pairing code expired: codes last 2 minutes. generate a new one with
pseudocoder pair --qr. - trust mismatch: re-pair from scratch.
- stale diff card: the file changed since the card was created. refresh and retry.
- TLS cert error: run
pseudocoder doctorto diagnose.
managing sessions
pseudocoder session list-- see active sessionspseudocoder session attach-tmux <name>-- attach to a running tmux sessionpseudocoder session detach <id>-- detach without stopping