Rank, 14 days: 281 on the Claude Code sheet
2 people reported

All time, since Oct 18.

Stop hook unpushed commit warning

“It repeats on every turn, and following it would create a branch we explicitly do not want.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/19221/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Stop hook reports unpushed commits after pushing to main. Hook compares HEAD only to origin/<session branch>, so commits already on main are reported as unpushed each turn and it asks for a push to the session branch.

Is this your bug?

File my report
Where
Cloud session stop hook
Error text
There are N unpushed commit(s) on branch 'claude/<session-branch>'. Please push these changes to the remote repository.
Versions
2.1.302
Platforms
Linux, macOS
How bad
Breaks a normal workflow.

Original reports2, newest first

  1. Cloud session Stop hook (stop-hook-git-check.sh) demands push to session branch, conflicts with main-only workflow; no way to disable#106023
  2. Cloud session stop hook only checks origin/<session-branch>, creating unwanted branches in the user’s repo#103232

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.