Changes and rewind

Every message you send is a request with its own record:

• files created, modified, deleted and renamed, including the ones a shell command touched;
• the commands that ran, with their exit codes;
• what each tool returned.

The request’s card

When a request changed files, a card closes its turn: one file shows its name with +N and −N; more show Edited 4 files with the first three. Undo (Undo this request’s file changes) puts those files back as they were before the request, and the card says Undone.

Snapshots

At the start of each turn Newen snapshots the folder into a shadow git repository in its own data folder, one per folder (~/.local/share/newen/snapshots/ on Linux), never in your project’s .git. With Claude Code it also snapshots after each tool that writes, so changes are attributed to the tool that made them; the other agents’ changes are attributed per turn.

Snapshots follow .gitignore. Folders no session works in any more can be cleared from Storage.

The changes pane

Ctrl+Shift+D, or /diff, opens the changes: the folder’s working tree against its branch (main → working tree), or one request’s (Changes in this request). A unified diff with file headers and +N −M counts, refreshed after each step, turn and undo. Newen uses your git binary, so your config, attributes and LFS behave as usual, and it never stages, commits or pushes by itself: see Git and pull requests.

Rewind and fork

Hover any of your messages for its actions:

• Rewind to here takes the conversation back to before that message: the agent goes on from there with your next message. It is not available while the agent works. Until you send a message, Undo rewind brings the conversation back as it was.
• Fork from here starts a new session that carries the conversation up to that message. Fork in a session’s menu, or /fork, carries all of it.
• Copy and Read aloud are there too.

Note

Rewinding the conversation leaves the files alone. To put files back, use Undo on the card of the request that changed them.