The command failed. The branch was gone, the changes lost, and the clock ticked forward with no undo button. You needed to see exactly what happened during that Git rebase. Not just logs. Not just commit history. A full rebase session replay.
Git rebase session replay is the way to reconstruct and analyze every step in a rebase workflow. It captures the sequence of commands, conflicts, resolutions, and resulting commits in order. Unlike simple git log or git reflog, a replay view shows the actual state transitions. This is critical for debugging, auditing, and training teams on complex branching strategies.
When developers run git rebase, they rewrite history. That history includes choices made during conflict resolution, commit ordering, and squash decisions. These choices are often invisible later because rebasing replaces commit IDs and discards intermediate states. A session replay rebuilds that timeline. It allows you to pinpoint the moment a bug was introduced or see why a merge took longer than expected.
Modern tools can hook into Git’s plumbing commands to record each phase of a rebase: