Cloud session: 'Commit to main' button stays as unclickable 'Merged to main' after subsequent commits in same session

Resolved 💬 2 comments Opened Apr 6, 2026 by howardpark Closed May 17, 2026

Summary

In the Claude Code Windows desktop app (Code tab), when working in a cloud session, the \"Commit to main\" button above the prompt area does not reset properly after a merge when new commits arrive in the same session.

Steps to reproduce

  1. Open the Claude Code desktop app on Windows and navigate to the Code tab
  2. Open a cloud session on a feature branch (e.g. claude/find-gmail-filter-prd-JxpzN)
  3. Wait for a new commit to appear on the branch — a "Commit to main" button appears above the prompt area
  4. Click "Commit to main" — the button changes to "Merged to main" (non-clickable), as expected
  5. Stay in the same session and wait for another new commit to arrive on the same branch
  6. Observe: the button remains as the unclickable "Merged to main" state — it does not update to a new clickable "Commit to main" button

Expected behavior

After a new commit arrives on the branch (step 5), the button should reset and become a clickable "Commit to main" button again, just as it was initially.

Actual behavior

The button stays stuck in the "Merged to main" (non-clickable) state until the user navigates away from the session and returns — at which point the button correctly shows as "Commit to main" again.

Workaround

Browse to a different session and come back — the button state refreshes correctly on re-entry.

Environment

  • Platform: Windows desktop app
  • Tab: Code tab (cloud session)

Impact

Minor but disruptive UX issue — users must manually navigate away and back to be able to merge subsequent commits in the same session.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗