[BUG] auth failure shouldn't burn a credit. session ID from earlier (session_01Rr3qaPW5KccdYCnNww2zXM)

Status Fixed / completed
Reported on v2.1.112
Maintainer reply None cached
Activity 4 comments · opened Apr 17, 2026 · closed Apr 17, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

ultrareview token burned due to auth failue

What Should Happen?

token should not have been burned

Error Messages/Logs

Something went wrong
Authentication failed while accessing the git_repository source. Check that your GitHub token or credentials have read access to this repository. If using a private repo, verify the integration is authorized for it.

Steps to Reproduce

run ultrareview with auth not configured in org of repo. auth was configured for account

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.112

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

_No response_

View original on GitHub ↗

4 Comments

fichtld23 · 6 months ago

please refund me a ultra review

fichtld23 · 6 months ago

duplicate

Tracy625 · 6 months ago

+1 — same billing fairness bug, different trigger.

In our case /ultrareview failed with a 30-minute remote session timeout on a large PR (+4710/-424, 59 commits), delivering zero findings. Free run count still decremented from 3/3 to 2/3.

After retrying, a second session also timed out — burning 2 of 3 free runs with no output delivered.

Environment:

  • Claude Code v2.1.112
  • Max 5x plan
  • PR: Tracy625/cq-collab#44
  • Sessions:
  • session_014tuJwbYUNHRRornrL6vJV5 (first failure — 30min timeout)
  • session_01B4qAupJzBGGhJ86ScFzghA (second failure — also timed out)

Agree with @ThatDragonOverThere's framing: "Crediting a session on failed launch is a billing fairness bug regardless of the root cause."

Two additional asks specific to the timeout case:

  1. Surface an up-front PR size check before consuming a free run, so large PRs can fall back to /review early
  2. Document the 30-minute hard cap in /ultrareview docs (currently only states 10-20 min typical)

Please refund both consumed free runs for session IDs above.

github-actions[bot] · 5 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.