Desktop (Windows): 'Auto-fix CI and address comments' checkbox is a silent no-op since 1.22209.0 (worked in 1.21459.3)
Environment
- Claude Code desktop, Windows 11 Pro (10.0.26200), MSIX / Windows Store install
- Broken on: 1.22209.0 and 1.22209.3 (current)
- Last working: 1.21459.3
Bug
In a local session with an attached PR, opening the CI dropdown and clicking the "Auto-fix CI and address comments" checkbox does nothing — the checkbox never gets marked, no error is shown, and nothing is logged.
This feature previously worked for local desktop sessions (it is event-driven: the AutoFixEngine wakes the session on new CI failures / review comments).
Evidence from %APPDATA%\Claude\logs\main.log
Working, on 1.21459.3 (July 16) — clicking the checkbox produced the IPC call and armed the engine:
2026-07-16 18:10:25 [info] LocalSessions.setAutoFixEnabled: sessionId=local_ff8e9da6-..., enabled=true
2026-07-16 18:10:25 [info] [AutoFixEngine] auto-fix enabled; kicking local_ff8e9da6-...
2026-07-16 18:17:47 [info] [AutoFixEngine] Waking local_ff8e9da6-...: 0 new failure(s) + 4 comment(s)Update timeline:
2026-07-17 09:53:27 [info] [updater] Version changed since last launch: 1.21459.3 -> 1.22209.0
2026-07-19 10:06:00 [info] [updater] Version changed since last launch: 1.22209.0 -> 1.22209.3Since the 1.22209.0 update: zero LocalSessions.setAutoFixEnabled entries despite repeated checkbox clicks in multiple sessions, and no renderer/main errors correlated with the clicks. The CI dropdown itself still works (LocalSessions.getPrChecks entries appear with the correct PR number when opening it), so the regression is specifically the checkbox → setAutoFixEnabled wiring.
Additional observations:
- Session state files (
%APPDATA%\Claude\claude-code-sessions\...\local_*.json) written by 1.22209.x contain"autoFixEnabled": null(and"branch": null) — the key exists but a click never flips it. The old working session's file has"autoFixEnabled": true. - The pre-update session that had the flag set kept receiving AutoFixEngine wake events across both updates (last on July 19) — so the engine itself still works in 1.22209.x; only enabling it from the UI is broken.
- Colleagues on older builds report the checkbox still works for them.
Expected
Clicking the checkbox toggles it, invokes LocalSessions.setAutoFixEnabled, and arms the AutoFixEngine for the session, as in 1.21459.3.
Showing cached comments. Read the full discussion on GitHub ↗
10 Comments
I confirm this used to works and is not anymore on mac app as well :(
Confirming on macOS — the label should be cross-platform.
"Could not enable PR auto-fix. Update the desktop app to use it." — misleading, since 1.22209.3
is already the latest build.
entries in ~/Library/Logs/Claude/main.log. The last successful "setAutoFixEnabled … enabled=true"
Same UI→IPC regression as #79358, so not Windows-only (see @JoeyNovais above).
Broken for me as well on macOS (26.5.2, 1.22209.3)
Another macOS confirmation, with a clean regression boundary from the logs.
Environment
1.20186.1 → 1.22209.0on 2026-07-16 18:27:59, then1.22209.0 → 1.22209.3on 2026-07-18 23:40:00Regression boundary
~/Library/Logs/Claude/main.loghas 87LocalSessions.setAutoFixEnabledentries total. The last one:That is the day before the
1.20186.1 → 1.22209.0update. Zero entries since, despite repeated clicks across multiple sessions and PRs. No renderer or main-process errors correlate with the clicks.Matches the OP's isolation
The CI dropdown itself still works —
LocalSessions.getPrChecksentries appear with the correct PR number when the panel is opened — so the panel is binding the PR fine and only the checkbox →setAutoFixEnabledwiring is dead. Consistent with @eddieyanez's trace on #79221 showing the click never reaches the main-process IPC handler, i.e. the control is rendered disabled in the renderer bundle. My bundled claude-code (2.1.215) is also the upper end of the2.1.209 → 2.1.215window noted there.[AutoFixEngine]lines are likewise absent after the update; my last ones are from 2026-07-07 on a session that had the flag armed pre-update.Ruled out user-side: latest build already installed, restarts don't help,
ghauthed, PRs open and non-draft.Same here.
v1.22209.3, still broken as of 2026-07-21.Tooltip on my end reads a bit different from @christopherlhart's: "Auto-fix isn't available in this version of the desktop app. Update the app to use it." Same misleading gist though, there's no newer version to update to.
That's six of us now across Windows and macOS, same regression boundary, same dead click handler in the traces. No maintainer response on this or #79221. Worth reopening and actually triaging, or commenting if this is already fixed internally and already in a near-term release.
@codebytere-ant I am still seeing this issue as well, why was the thread closed?
Confirming this stopped working as of 7.20.2026 on Mac as well.
Seems to be working as of
Claude 1.24012.0 (44be96) 2026-07-21T16:43:51.000ZConfirmed. Latest update fixed it for me on macOS. @mathop @christopherlhart @iangcarroll @JoeyNovais @kvgusto
Confirmed working for me too thank you!