RepoBeam
Releases Download

Coding Sessions

Review AI-assisted work with a Coding Session

A Coding Session remembers your files when it starts and shows every change made since, as it happens. Undo what you don’t want, then keep or commit the rest.

  • 4 min read
  • RepoBeam 1.8
  • Windows & Linux
A running Coding Session listing four changed files, one undone file, and the diff of App.tsx

In short

  • Starting a session saves a private restore point. No branch is created and nothing is committed.
  • Every file that changes afterwards appears in the session within seconds, with its diff.
  • Undo single files, bring them back, edit them, then keep, commit or undo the rest.

A session is a restore point and a review, not a security sandbox. Agents and editors still run with your normal permissions; the session shows what changed in the repository.

Step by step

  1. Start a session

    Click Session in the toolbar. Say what you are working on if you like, then click Start session. RepoBeam saves every file as it is now, uncommitted work included.

    Start a coding session dialog with the three steps and a name for the session

  2. Work, or let an agent work

    Use Claude Code, Codex, Cursor, Copilot or your own editor as usual. A bar under the toolbar shows that the session is recording, for how long, and how many files changed.

    The session bar under the toolbar: Export notes as PDF, recording for 1 min, 4 files changed, with Review and Finish

  3. Review what changed

    Click Review. Every file changed since the start is listed with its diff. Click Edit file to change it in place, or Undo file to put it back exactly as it was when the session started.

  4. Bring back anything you undid

    Undone files move to Undone · can be brought back. Changed your mind? Use Bring back the changes on the file.

  5. Finish

    Click Finish session and choose Keep the changes to commit them later from Local Changes, Commit the changes to commit only the session’s files under your own Git name, or Undo the changes to put every file back.

    Finish session dialog with Keep the changes, Commit the changes and Undo the changes

Good to know

  • Stays on your computerThe restore point and the session list live inside your repository’s .git folder. Normal Git operations don’t push them.
  • Commits during a sessionCommits you or an agent make while a session runs are listed with it, and stay in history whatever you choose when finishing.
  • Works with any toolSessions look at the files in the repository, so there is nothing to install in your agent or editor.
  • Tidy up laterFinished sessions can be removed from the list. That doesn’t touch your files or commits.