Diffwright 0.14.0

Features

• Usage statistics and error reports, only if you want them: at setup, or once if you were already using Diffwright, you can choose to share how often each feature is used and scrubbed error reports, tied to a random ID for this installation, and never organization, project or repository names, code, comments, paths, URLs or tokens; nothing is sent without your consent, and you can change your mind, preview the next report or delete your data in Settings › Privacy.

Improvements

• Multi-key shortcuts: in Settings › Keyboard shortcuts, a shortcut can now be a sequence of two or three keys, like ⌘K then ⌘S or G then P. Type the keys one after another: Enter or a short pause saves, Backspace removes the last key, Esc cancels. When you type the first key of a sequence, a small hint waits for the next one.

Diffwright 0.13.0

Features

• Settings › Keyboard shortcuts: customize the shortcuts of the registry actions (one binding per
  action, or none). Each row resets on its own, and one button resets all shortcuts. Filter by
  keyword, All/Changed, and a help screen (⌘/) showing the effective bindings. The "Keys without a
  modifier" setting lives there too. Your shortcuts are exported with your settings and stay in sync
  across all windows.
• Update popup: when a new version is detected, the "Update available" window opens by itself,
  once per version, instead of only the dot in the activity bar. "Later" closes it; nothing is
  installed without your click.

Improvements

• Keyboard navigation between files: ⌘↓ and ⌘↑ jump to the next or previous change, and switch
  file when there are no more in the current one. Binary and deferred files are skipped. While the
  key is held down, it never switches file. At the last or first change of the Pull Request, it does
  not wrap around: a brief message says so. The "next/previous change in the file" actions remain
  available, without a shortcut, to stay within a single file.

Fixes

• Reserved editing shortcuts: ⌘←/→, ⌘⇧←/→, ⌘⌫, ⌦, ⌘Home/End and variants (Ctrl on Windows) can no
  longer be assigned to registry actions — they are the text editor's and the system's keys. Your
  existing bindings that used them go back to the default.
• Test window capture shortcut: the default changed from ⌘⇧S (often taken by macOS) to ⌘⇧C
  (Ctrl+Shift+C on Windows), editable in Settings. Capture works even when the tested page has focus,
  without duplicates, and does not trigger while the toolbar is expanded.
• AZERTY keys + ⌘: digit keys with ⌘ (e.g. ⌘&1) are read from the physical key; AltGr never
  triggers a shortcut on Windows.
• Update popup: it no longer appears over another window (Settings, command palette, wizard,
  confirmations…) but waits for it to close, as well as for "What's new" and any ongoing typing to
  finish; on automatic opening, focus is on "Later".
• ⌘↑, ⌘↓, ⌘⇧↑, ⌘⇧↓ and ⌘⇧Z shortcuts: they are no longer intercepted while you write in a text
  field (comment, suggestion); the cursor, undo and redo remain the system's.
• AI chat: the text of a cancelled question no longer slips into the next answer.
• Binary files: the diff no longer shows an endless loading state.
• Mentions: the closed list no longer reopens with old names, people search no longer mixes two
  organizations, and a network outage no longer disables it for the whole session (it retries after a
  few seconds).
• AI review: a small change in a file of more than 4,000 lines is no longer discarded.
• AI assistant not found from the Dock: claude is found even when the app is launched from the
  Finder or the Dock (Homebrew install on Apple Silicon, npm); when it is missing, the message
  prompts you to install it.
• Azure DevOps token: a disk write failure is reported instead of a false success, an unreadable
  credentials file is no longer overwritten (the tokens of other accounts are kept), and the file is
  created read-only for you from the start.
• Forgotten or replaced token: the old one is no longer used until restart, whatever the casing
  of the organization name.
• Automatic review: two Pull Requests with the same number in two organizations no longer block
  each other.
• Azure DevOps: a connection that hangs no longer blocks the following requests; if a change
  could not be confirmed (timeout after sending), Diffwright says so and asks you to check before
  retrying, instead of letting you believe nothing happened.
• Review overlaps: computing them no longer delays opening files.
• Translations: "unknown error", "Content unavailable" and "Couldn’t publish this comment." follow
  the interface language; so do the AI engine's error messages.

Diffwright 0.12.0

Features

• Interface in French and English: pick your language in Settings › General › Interface language
  (System, Français or English; the default follows your OS). The change applies instantly,
  everywhere in the app, and persists from one session to the next.
• Published text language: comments, test feedback and exports are written in the language you
  choose (Settings › General › Published text language: Same as interface, Français or English),
  independently of the interface language.
• AI replies in your language: the "AI reply language" setting gains a "Same language as the
  interface" option (new default) that produces replies in French or English depending on your
  current choice.
• 8-step setup wizard: instead of the simple welcome onboarding, a real guided setup: after the
  first sign-in, the following steps (profile, project, settings) stay locked until you connect, and
  you cannot continue without validating your token. If the token is rejected or expired, the wizard
  goes back to "connection only" mode so you can try a new one.
• Multiple saved Azure DevOps accounts: a new Settings › Accounts section lists your
  organizations (status checked on open), and for each one you can make it active, replace its token,
  or forget it. No automatic merging and no custom labels.
• Switch accounts from the keyboard: the rail's avatar menu and the ⌘K palette's "Switch to {org}"
  change organization without reloading, keeping your open tab and screen.
• Pinned PR windows and account changes: the windows show the Accounts section read-only (no
  Remove or Use) and close automatically if their account is removed elsewhere — the storage event
  notifies them without restarting the app.

Improvements

• Resizable setup wizard: the welcome screen, header and footer stay visible even when the window is
  shrunk to its minimum (900×600 on macOS, 900×540 on Windows); steps appear in 3 columns on large
  screens and as numbered pills on small ones.
• Redesigned language picker: a dropdown in the wizard header and in Settings › General shows the
  current language and the available ones (System, Français, English), with the language detected from
  macOS/Windows shown as a subtitle.

Fixes

• What's new is translated: the « What's new » screen now shows in English when the interface is
  in English, and follows a language switch without closing.

Diffwright 0.11.0

What's new

• Built-in updates: Diffwright checks on its own, at startup and then every 6 hours, whether a new
  version is available and flags it in the activity bar. Updates are signed and are only downloaded and
  installed after you click; you can also run the check by hand or turn off the startup check in
  Settings › Updates.
• Usage profiles: tell Diffwright your role — Reviewer, Tester, Author or Team lead — and it only
  shows what is useful to you. A tester sees neither the Code space nor the Team space, and a Pull
  Request opens directly on the Test tab ("Show code" stays one click away, and a banner takes you back
  to your profile's view). The role is chosen in the setup assistant or in Settings › Usage profile,
  where each space and each tab can also be adjusted one by one. Nothing is removed: everything comes
  back when you switch profile.
• A Test tab to test a Pull Request end to end: a dedicated tab of the Review panel (⌘6) brings the
  test session together — preview environment or local address, window state, live page errors, and
  feedback already filed in your review. The page opens in an isolated window with no access to
  Diffwright, topped by a toolbar: navigation, address, page errors, and capture (⌘⇧S) without leaving
  the test window.
• Run the PR's project on your machine (macOS and Windows): a launch profile describes how to start
  the application. "Run" fetches the PR's code, first shows every exact command with the required tools,
  the variables to provide (secrets stay on your machine) and any warnings, then follows the run live —
  status, steps with their duration, log, stop — and opens the test window as soon as the application
  responds. Nothing runs without your approval, and a trusted profile can be relaunched in one click as
  long as its commands don't change.
• A real launch workflow, with a visual editor: each profile chains its steps — command, background
  process, waiting for an address, a log message or a delay, opening the test window — and a "On stop"
  list. "Configure" opens a visual builder (or the raw text); existing files are still read and trust
  already granted is kept. A launch script that returns control (for example by running in the
  background) is no longer mistaken for a failure.
• AI prepares the launch for you: "Suggest with AI" reads the repository (docker compose,
  Dockerfile, README, launch scripts…) and suggests a profile, which you review before saving it
  through a commit. It reuses the repository's scripts instead of rewriting their steps, and "Analyze
  the failure" points to the likely cause of a failed launch (port in use, image not found, missing
  variable…) without running or changing anything.
• Local files and ports checked before launch: git-ignored files the project needs (an environment
  file, for example) are detected, then copied into the test folder on every launch without ever being
  sent anywhere. Ports that are already in use are reported along with what is using them — a container
  to stop in one click, a process, or another PR's stack — instead of letting the launch fail along the
  way.
• Test folders under control: a single folder per PR, automatic cleanup of unused folders (14 days
  by default) and a total space cap (10 GB by default). Settings › Tests lists each folder (size, last
  use) so you can show or delete it, and also gathers local files and test accounts.
• Test feedback with an annotated screenshot: capture an area of the screen (Diffwright steps aside
  during the selection), paste an image or pick a file, annotate it — rectangle, arrow, pencil,
  ellipse, highlighter, numbered markers, text, blurring of sensitive data, 9 colors readable
  everywhere — then publish it as a Pull Request comment, along with the iteration and commit tested.
  On Windows, press Win+Shift+S then paste the capture.
• Enrich a test feedback: attach the page's errors (console, exceptions, failed requests) or the
  latest errors from the local stack's log, unchecked by default and reviewable before sending; record
  the page under test (30 s at most, macOS) to attach a video, published as a link.
• Test feedback in "Finish my review": "Add to my review" sets a feedback aside instead of
  publishing it; the whole session is reviewed and then sent at once, like code comments. Screenshots
  stay on your machine until publication.
• Follow up on your test feedback: the Test tab lists published feedback with its status — pending,
  author replied, resolved, new push since your feedback. "Re-test" brings the test window back, then
  "Confirmed fixed" or "Still present" posts your answer in the thread. Nothing is sent without your
  click.
• Test verdict: "Finish the test" gives your verdict — Approved, Approved with reservations or
  Rejected — with a comment and an automatic summary (version tested, feedback published, page errors)
  that you review before publishing, and a suggested vote that you can change or remove. "Save without
  publishing" keeps it on your machine.
• "To test" on Home: a tile lists the Pull Requests you review that haven't been tested since their
  last push, and a badge — Approved / Reservations / Rejected / To re-test — accompanies them in the
  lists (tile shown for the Tester profile, or as soon as you've run your first test).
• A test stack is never forgotten: as long as a project launched on your machine is running, a
  "Stack · #PR" badge stays in the title bar (amber if it serves a PR other than the one open) to
  reopen the PR or stop the stack, and leaving a PR whose stack is running offers "Stop" or "Keep
  running". If the PR receives a new push, the Test tab and the test window bar say so and offer
  "Relaunch on iteration N"; a stack from another PR that holds the port can be stopped in one click
  when launching this one.
• Test window tools ("⋯" button): page screen size (Desktop, Small screen, Tablet, Mobile or Fit),
  session reset, and test accounts saved per repository, copyable in one click (the password leaves the
  clipboard a minute later).
• Test tools on Windows: the test window can be captured and picks up page errors, and launch
  profiles also run on Windows, without a console window.

Improvements

• A more consistent app from one screen to the next: the Code, Repositories, Team and Pull requests
  spaces share the same header (title and context on the left, data freshness and actions on the right,
  filters below), and the detail panels — Review, branch, repository, contributor — share the same
  layout and the same tabs.
• A Pull Request looks the same everywhere: same information in the same place on Home cards, the
  sidebar, the inbox, ⌘⇧P search, the bell and popovers, and the same gestures: click to open it,
  ⌘-click for a new window, ⋯ button or right-click for its actions.
• Action menus everywhere: ⋯ button and right-click on Pull Requests, repositories, files, threads
  and branches, with the same actions as the ⌘K palette (copy the link, open in Azure DevOps, open in
  the Code space, blame, resolve a thread…).
• AI looks the same everywhere: same button, same indicator while it works, same "Suggested by AI"
  frame and same reminder that nothing is published without your click — from the AI review to chat,
  reply drafts, descriptions, commit, test launch and team summary.
• Uniform wording and states: the same words for the same actions ("Refresh", "Publish", "Save",
  "Remove"…), one loading indicator, an error that offers "Retry" when possible, and "Refreshed … ago" /
  "Live" wherever data updates.
• Calm, consistent animations: switching tabs, screens or Pull Requests is instant — only the
  selection pill slides. Motion is reserved for what really happens (a list loading, a folder
  expanding, a box being checked, a counter changing), always subtle and quick, and nothing replays when
  you return to a screen or during refreshes. The line marker after navigating in the diff finally
  shows up. "Reduced motion" turns everything off.
• Loading that no longer flickers: each screen holds its place while loading, with skeletons of the
  same shape everywhere (PR files, branches, history, repositories, comments, review feed, test). An
  indicator doesn't appear for a quick read and doesn't vanish right after showing, no list appears
  "empty" before it has loaded, and a refresh keeps the content. The branch list arrives complete and
  sorted, and Pull Requests you've already opened (30 per session) reopen instantly.
• No more hover tooltips: the bubbles that appeared on buttons and the activity bar are gone.
• Settings reorganized and searchable: "Search settings" (⌘F) finds a setting by name and jumps to
  it. Sections are grouped (You, Display, Work, Tracking, System); "General" only keeps startup and
  keyboard, refresh rates have their own "Synchronization" section, and caches, history, export and
  reset are under "Local data". Pull requests settings are arranged by moment, and the tab opened by
  default is now set in one place only, in Usage profile.
• Tester view uses the full width: without code, the Review panel takes the whole main column. The
  Test tab switches to two columns — the application and its run on the left, the verdict and feedback
  on the right —, Summary cards spread across columns, and threads keep a comfortable reading width.
• A more guided tester journey: the Test tab walks you through the first setup ("Set up launch",
  AI suggestion first), offers to resume after a setting change, shows test feedback with clickable
  thumbnails in "Finish my review", confirms publication and suggests a commit message for the launch
  file and the checklist.
• Faster relaunch: relaunching a Pull Request on the same commit reuses its test folder instead of
  downloading the code again; only your local files are copie...