Back to rankings

Claude Code Web Lets You Diff Against Any Branch

Claude CodeView original changelog

Claude Code 2.1.274 added a "Compare against" branch picker to the diff view of a cloud session on Claude Code on the web, letting a user diff a session's changes against any branch instead of only the repository's base branch. Previously, the diff view always compared a working branch against the repository's default branch, which buried a feature branch's real changes under unrelated history whenever that branch was cut from something other than the default.

Key Takeaways

  • Cloud session diffs are no longer locked to the base branch; a new "Compare against" picker lets a user choose any branch to diff a session's changes against.
  • The change addresses a real pain point for teams that branch off something other than main, where diffs previously buried real changes under unrelated history.
  • The feature ships in Claude Code 2.1.274, released September 17, 2026, alongside a cluster of MCP, reliability, and VS Code fixes.
  • It is scoped to Claude Code on the web; the desktop app's diff viewer is not mentioned as changed in this release.
  • The same release also improved other cloud-session behaviour, including routines retrying for up to 72 hours when a GitHub connection is missing rather than switching off at the first failed check.

Cloud Sessions Can Now Diff Against Any Branch

Claude Code 2.1.274 added a "Compare against" branch picker to the diff view of a cloud session on Claude Code on the web, letting a user diff a session's changes against any branch instead of only the repository's base branch.

Why the base-branch limit was a problem

Previously, a cloud session's diff view always compared the current working branch against the repository's base branch, typically main. For a feature branch created off something other than the default, such as a release branch, that meant the diff view showed the entire delta between the release branch and main, burying the user's actual changes under unrelated history.

What changed

With the new picker, a user reviewing a cloud session's changes can select any branch to diff against, not just the one the environment defaulted to. That makes it practical to review a change in the context it was actually built for, whether that is a shared release branch, a long-lived feature branch, or anything else the repository uses instead of a single default branch.