Skip to content
DiffwrightBeta

why

Why Diffwright exists

Code review is one of the most decisive moments in a team’s work. Diffwright has one goal: make it faster, safer and more thorough, without ever taking the decision away from the person doing the review.

  1. the problem

    Review deserves better than a chore

    Code review is a key moment in a team’s life. It’s where the team shares what it knows, where a mistake gets caught before it reaches production, where a way of working gets passed on. Day after day, it’s also a large share of developers’ time, and even more so for lead developers.

    In Azure DevOps, that time is spent in the web interface. It does the job, but it’s sometimes slow, and it doesn’t render some files: a changed image, a PDF or a Word document shows up as raw content that you have to download and open elsewhere just to see what changed.

    Those frictions add up. You jump from tab to tab, lose the thread of a noisy diff, and your attention fades a little more with each pull request. That’s exactly when an important detail slips through. Diffwright starts from there: review decides much of a project’s quality, so it deserves a tool built for it.

  2. first version

    A first version, proven on macOS

    The first answer took the form of a macOS app, used every day on real reviews. It did most of the work locally and showed files the way they actually look: images, PDFs and Word documents instead of their raw content.

    More than anything, that first version established what matters. That speed truly changes how you review: when the tool responds instantly, you’re willing to open one more file, check one more call. That AI can help, as long as it stays in its place. And that one rule has to be set from day one: nothing gets published to the platform without an explicit action from the reviewer.

    Two limits shaped what came next. The app only ran on macOS, while teams also work on Windows. And some parts of its interface, like multi-line selection, the minimap or the Word document preview, were reaching the limits of their technical foundation.

  3. turning point

    Rebuilt for macOS and Windows

    So Diffwright was rebuilt from the ground up, with one clear requirement: stay as fast as the first version, on macOS and Windows alike.

    Nothing was lost along the way. The first version became the behavioral reference for the new one: its tests describe what Diffwright is supposed to do, and they settle any doubt. The heavy lifting (talking to Azure DevOps, GitHub or GitLab, computing diffs, driving the AI) runs in the background so the interface stays responsive. Diffs are displayed in a full-fledged code editor.

    The interface was rethought rather than copied. Diffwright is laid out like a code editor, with panels you can resize and collapse, so the pull request, its files and your review all fit in a single workspace.

  4. convictions

    Four principles that aren’t negotiable

    Four principles have guided Diffwright since its first version. They aren’t options tucked away in the settings: they govern every new feature, and an idea that would require giving one of them up gets dropped.

    When it comes to AI, they fit in a single sentence.

    The AI suggests, you decide.

    1. Every write is a click

      Posting a comment, voting, merging, resolving a thread: none of it reaches Azure DevOps, GitHub or GitLab without an explicit click on that very item. Never from a background task, never from a pre-checked batch, never through an automatic retry. Whoever does the review is the one who signs off.

    2. An AI you choose, that helps

      By default, AI runs through the claude CLI you installed yourself, or a local model through Ollama. Codex CLI and pay-per-use engines (Anthropic, OpenAI-compatible) are possible, but opt-in only: with your own key, stored on your computer, and explicit consent for each service. Automatic review never turns on with a paid engine. Every suggestion can be accepted, edited or ignored. And when no AI is available, or you turn it off, its features disappear from the interface instead of sitting there grayed out.

    3. Repository content stays untrusted

      Configuration files, review guidelines, tested pages: they all come from the repository, which means they may come from any contributor. Diffwright never runs them without confirmation, never renders them as HTML, and guards the instructions it sends to the AI against injection attempts.

    4. Speed is a feature

      Moving from one pull request to the next, from one file to another, should be instant. No animation holding navigation back, no loading screen when the information is already there. A fast review is a review that actually gets done.

  5. testers

    Giving testers a voice

    A pull request isn’t only about developers. Testers, who are often less at home with technical tools, play a decisive role, and their feedback deserves better than a quick message with no context that’s hard to reproduce.

    Diffwright gives them a tool that matches the job: test feedback published right in the pull request, complete and actionable for whoever fixes the issue.

    The Test tab lets a tester annotate a screenshot and attach it to the review, along with the errors caught on the tested page when needed. As with everything else, nothing is sent until that person publishes their feedback themselves.

  6. today

    Diffwright today

    Diffwright is a desktop app for macOS and Windows, dedicated to reviewing Azure DevOps pull requests. Support for GitHub and GitLab is available in beta, and the app itself is a public beta.

    The beta follows a strict rule: a feature only counts as verified once it has been exercised against a real organization or account. Until then, it stays flagged as unverified.

    The interface will keep evolving from release to release. The principles above stay fixed.

  7. what’s next

    What comes next

    Diffwright keeps moving in the same direction: less friction for the reviewer, an AI that stays an assistant, and test feedback that genuinely helps the team.

    If you review pull requests in Azure DevOps, GitHub or GitLab, install Diffwright and run your next review with it. A question, or a feature you’re missing? Write through the Contact page: every message is read.