claude-code - 💡(How to fix) Fix [Bug] Billing charge applied to failed Claude Code session [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/macabeus/.local/share/claude/versions/2.1.123 (expected in multi-process scenarios)\n at x86 (/$bunfs/root/src/entrypoints/cli.js:2769:2177)\n at Jw8 (/$bunfs/root/src/entrypoints/cli.js:2769:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-29T20:14:44.998Z"},{"error":"Error: CreateSession 400: {"error":{"message":"GitHub repository access check failed — re-authorize GitHub in settings","reason":"github_repo_access_denied","type":"invalid_request_error"},"request_id":"req_011CaYggiV7r62dCLAeGmxSK","type":"error"}\n at xqH (/$bunfs/root/src/entrypoints/cli.js:2824:2506)\n at async kN8 (/$bunfs/root/src/entrypoints/cli.js:6530:739)\n at async r93 (/$bunfs/root/src/entrypoints/cli.js:6620:49)\n at async <anonymous> (/$bunfs/root/src/entrypoints/cli.js:6622:400)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-29T20:21:57.152Z"},{"error":"Error: CreateSession 400: {"error":{"message":"GitHub repository access check failed — re-authorize GitHub in settings","reason":"github_repo_access_denied","type":"invalid_request_error"},"request_id":"req_011CaYgphMsRFfFybxedVUw4","type":"error"}\n at xqH (/$bunfs/root/src/entrypoints/cli.js:2824:2506)\n at async kN8 (/$bunfs/root/src/entrypoints/cli.js:6530:739)\n at async r93 (/$bunfs/root/src/entrypoints/cli.js:6620:49)\n at async <anonymous> (/$bunfs/root/src/entrypoints/cli.js:6622:400)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-29T20:23:45.423Z"}]

TL;DR

Re-authorize GitHub in the settings to resolve the "GitHub repository access check failed" error.

Guidance

• The error messages indicate a "github_repo_access_denied" error, suggesting a permissions issue with GitHub repository access.
• Check the settings to ensure GitHub authorization is up-to-date and valid.
• Try re-authorizing GitHub in the settings to resolve the issue.
• If the issue persists, verify that the GitHub repository access permissions are correctly configured.

Notes

The provided error messages are consistent and point to a specific issue with GitHub repository access. However, without more information about the settings or the authorization process, it's difficult to provide more detailed guidance.

Recommendation

Apply workaround: Re-authorize GitHub in the settings, as this is the most direct solution implied by the error messages.