"Auto-fix CI & address comments" checkbox unresponsive in PR CI monitoring panel

Status Fixed / completed
Maintainer reply None cached
Activity 4 comments · opened Jul 19, 2026 · closed Jul 20, 2026

Description

The "Auto-fix CI & address comments" checkbox in the CI monitoring panel (PR sidebar) cannot be checked. "Auto-merge when ready" in the same panel is also greyed out.

Steps to reproduce

  1. Open a PR's CI monitoring panel in Claude Desktop.
  2. Try to check "Auto-fix CI & address comments".

Expected behavior

Checkbox should be checkable and enable auto-fix behavior, as it did previously.

Actual behavior

Checkbox appears disabled/unresponsive with no visible tooltip or error explaining why.

Scope of reproduction

  • Reproduces across multiple sessions and multiple PRs, not just one.
  • Reproduces even when the PR is out of draft status (marked ready for review) — not gated on draft state.
  • Restarting Claude Desktop did not resolve it.
  • This worked previously — appears to be a regression, not a feature I've never had access to.

Environment

  • Claude Desktop, latest version at time of filing (2026-07-19)

Example

PR where this reproduces: https://github.com/chingu-voyages/V61-tier3-team-99/pull/141

View original on GitHub ↗

4 Comments

eddieyanez · 1 month ago

Confirming this independently on macOS – same symptom, same control. Adding log-level evidence that should help narrow it down.

Below is the summary of what I've been able to debug with Claude's help locally. The issue breaks my Claude Code workflow when running locally, and polling Github manually is not the best workaround.

Regression window. Last working toggle: 2026-07-16 23:22:39 (~20 successful toggles between 06-30 and 07-16). Nothing since. claude-code 2.1.209 → 2.1.215 across that window; app.asar rebuilt 2026-07-19 02:16.

The click never reaches the main-process IPC handler. Clicked 3× on a session with a correctly bound OPEN PR; zero LocalSessions.setAutoFixEnabled lines in ~/Library/Logs/Claude/main.log. That handler logs unconditionally on entry, so the renderer isn't invoking the IPC at all.

Everything below the UI is intact (traced in the shipped bundle):

  • IPC handler registered: …LocalSessions_$_setAutoFixEnabled
  • LocalSessions.setAutoFixEnabledgithubPr.setAutoFixEnabledemitSessionUpdatedt.autoFixEnabled = r; config.saveSession(t)
  • GitHubPrManager binds the PR correctly — session JSON shows prs: [{prNumber: …, state: "OPEN", …}]
  • autoFixEnabled is simply absent — nothing ever wrote it
  • getPrChecks polls normally at click time; no errors in main.log or the renderer log

So the defect is isolated to the renderer. A silent no-op with no error is consistent with the control being rendered disabled.

Likely a web-bundle regression. The desktop UI is the claude.ai web app in Electron (IPC namespace claude.web), so the checkbox markup is served, not local — consistent with this appearing with no user-side change, a restart not helping, and cloud sessions being unaffected.

Possible lead: https://github.com/anthropics/claude-code/issues/76685 (closed 2026-07-13) covered the same control's re-arming behaviour. If its fix changed the toggle's enabled/disabled state handling, that would sit at the head of this regression window. Speculative, but a cheap bisect target.

@dhoepp's note that "Auto-merge when ready" is also greyed out suggests a shared gating condition on the panel rather than anything auto-fix specific.

Ruled out user-side: clean settings.json/settings.local.json, no enterprise managed-settings.json, gh CLI authed, Anthropic OAuth healthy at click time, PR open + non-draft + correctly bound.

Also submitted via /bug, reference ID 08d73566-9358-4022-85e6-dd471f745e4b — the transcript attached there has the full evidence chain.

dhoepp · 1 month ago

@codebytere-ant was this resolved? just wanted to follow up, perhaps a patch i missed. #76685 is similar but not the same issue. mine has only started for me yesterday. ive tried updating and restarting claude code desktop but the issue persists.

eddieyanez · 1 month ago

@dhoepp the fix is live - just update the app. Glad this was a quick fix after all.

dhoepp · 1 month ago

Beautiful! It works again! ☺️