GOOD TO KNOW

Your files stay safe

Updated October 22, 2026 · 2 min read
When DevFlow changes or reads code on its own, it works in a separate private copy of your repository — a worktree — so your folder and uncommitted changes stay where they are.

01How it works

There’s no screen for this — DevFlow Desktop handles it behind the scenes.
1
A private copy
When auto-fix starts, DevFlow fetches the PR’s branch and creates a worktree for it in your computer’s temporary folder.
2
Fixes are committed there
Each fix is committed inside that copy, then pushed to the PR’s branch once, if Push fixes when finished is on.
3
The copy is removed
At the end of the run DevFlow deletes the worktree, even after a failed push.

02Good to know

AI review reads, never writes
For an AI review DevFlow prepares a read-only copy of the PR branch, so the AI can read the whole codebase without switching your folder.
Your files are never staged for you
When an agent or the CLI commits in your own folder, DevFlow commits only what you’ve already staged.
Push fixes turned off?
Then fixes are committed to your local branch for you to push, and the run is skipped while that branch is checked out in your folder.
Local disk only
Worktrees work only for repositories on your computer’s own disk, not inside WSL on Windows.