Review Nour privacy and recovery
Before every turn that may change files, Nour saves a snapshot of the work tree; Changes from this turn lists what changed, and Undo this turn puts the work tree back. A snapshot does not cover pushes or files outside the repository. Your messages go to the agent CLI you chose, under its own provider’s policy; GitTree never stores an API key or calls a model itself.
Needs GitTree Pro or a running trial; Free keeps every local Git feature. Compare the plans.
On this page
Before you start
- GitTree Pro or a running trial: Nour is part of Pro.
Where to find it
- Under each Nour reply that changed files: Changes from this turn.
| Action | macOS | Windows and Linux |
|---|---|---|
| Open or close Nour | ⌘⇧Space | Ctrl+Shift+Space |
Steps
See what changed
Under the reply, Changes from this turn lists the files; View diff shows each change and Open … opens the file.
Undo the turn
Press Undo this turn. If files changed after the turn, GitTree warns that they will be overwritten; press Restore … files to go ahead.
Check the result
GitTree says The work tree is back as it was before this turn. With several repositories, Undo this turn everywhere restores each one.
Expected result
Your files are exactly as they were before Nour’s turn.
What a snapshot cannot undo
- Pushes, pull request merges and other changes on a provider.
- Files outside the repository.
- A turn with no snapshot: GitTree says it cannot be undone. If a snapshot cannot be saved (for example with unresolved conflicts), the turn does not start.
If something goes wrong
“This repository ships agent settings that could run their own commands during the turn”
Look at the hooks, helpers or MCP servers the repository brings. If you trust them, Run anyway once.
Questions
Does GitTree send my code anywhere?
GitTree itself does not. The agent CLI you chose sends what it reads to its own provider, under that provider’s terms, as it would in your terminal.