Editor, diffs, and the file tree
Reviewing what an agent changed before it lands, and editing files directly in NALA.
NALA includes a file tree, an editor, and a diff view. They exist for one job above all others: seeing what an agent changed before you accept it.
IMPORTANT
Review generated changes before relying on them. An agent that produces a confident, well-structured, wrong change is the normal failure mode, and the diff view is where you catch it.
The diff view
Opens on any file an agent has modified, showing the change against what was there before.
- Per-file, not per-run. A run that touches twelve files gives you twelve diffs to look at rather than one wall of changes.
- Reverting is a file operation. Discarding a change writes the old content back; it does not undo anything else the agent did — commands it ran, files it created elsewhere, or messages it sent to other agents.
If a run is working inside a worktree, the diff is against that worktree, not your main checkout.
The file tree
Scoped to the workspace directory. It shows what is on disk now, including files an agent created while you were reading something else.
The tree does not hide files that are ignored by git. That is deliberate: an agent writing to a git-ignored path is exactly the case you want to notice.
The editor
A working editor for direct changes, not a replacement for your usual one.
It is useful for the small correction you want to make immediately — fixing a name an agent got wrong, adjusting a value before re-running. For sustained work, keep using the editor you already know.
Changes you make are ordinary file writes. An agent running concurrently can overwrite them, and will not know you were editing.
WARNING
There is no locking between your edits and a running agent. If an agent is actively working on a file, either let it finish or stop it before editing.
What these surfaces do not do
- No approval gate. Viewing a diff does not hold the agent. Work continues while you read unless you stop it. See Permissions and approvals.
- No history beyond the current change. For anything older, use git.
- No conflict resolution. Two agents writing the same file produce a last write wins result, not a merge.