Undoing a turn, and seeing what changed
| Command | Does |
|---|---|
/undo | puts back the files the last turn changed |
/redo | re-applies them |
/changes (or /diff) | summarizes everything different in the working tree: each file with its status and lines gained and lost, plus a total |
- Nothing to set up. Houston snapshots every write before it happens.
- Best with auto-approve modes, where edits land without a prompt: "that was wrong, put it back" is one word rather than a hand revert.
- Limits.
/undocovers the last turn's file writes only. It doesn't undo shell commands, and it doesn't touch git history. /changesis the natural question after a long autonomous run.
Shipping changes (desktop app)
When the working tree has changes, the bar above the composer and the Changes panel offer one button that fits the repository:
| Button | When |
|---|---|
| Create PR | it has commits and a GitHub remote (github.com, or a GitHub Enterprise host your gh is signed in to) |
| Publish to GitHub | it has no remote yet (commit, create the repository, push) |
| Push first commit | a remote exists but nothing is committed |
| Commit & push | the remote isn't on GitHub |
Each one hands the work to the agent as a normal turn, so every git and network step goes through your approvals.
Prompts Houston writes for you
/review, /agent, the shipping buttons, and a session another chat handed off each send the agent a detailed prompt. The chat shows what you did (for example "/review" or "Create PR") instead of that prompt. Open Instructions sent to the agent under it to read the exact text. The terminal prints a one-line summary in its place.