claude-code - 💡(How to fix) Fix [Bug] Session limit blocks access despite available credits and low usage percentage [2 comments, 2 participants]

[{"error":"Error: Failed to delete keychain entry: security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.\n at wIq (/$bunfs/root/src/entrypoints/cli.js:256:288468)\n at async j49 (/$bunfs/root/src/entrypoints/cli.js:409:898)\n at async gr6 (/$bunfs/root/src/entrypoints/cli.js:409:796)\n at async $z_ (/$bunfs/root/src/entrypoints/cli.js:2740:2259)\n at async FGH (/$bunfs/root/src/entrypoints/cli.js:2766:6041)\n at async <anonymous> (/$bunfs/root/src/entrypoints/cli.js:2791:3443)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T20:40:24.417Z"},{"error":"Error: Not enough messages to compact.\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:5622:1117)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T20:42:05.775Z"}]

TL;DR

The issue may be related to a session limit or keychain entry problem, and checking the keychain configuration or session management could help resolve the issue.

Guidance

• Review the keychain settings to ensure that the necessary entries are correctly configured and not causing the "SecKeychainSearchCopyNext: The specified item could not be found in the keychain" error.
• Investigate the session management system to understand why the session limit is being reached despite having unused credits and a low usage percentage.
• Check the documentation for any specific requirements or limitations related to session limits and keychain configuration.
• Consider reaching out to support with the provided Feedback ID (a530c7a2-dabd-42bb-b510-68256a2cd445) for further assistance.

Notes

The provided error messages suggest a potential issue with keychain configuration or session management, but without more information about the specific system or application, it's difficult to provide a more detailed solution.

Recommendation

Apply workaround: Given the uncertainty around the root cause, it may be best to try to work around the issue by adjusting keychain settings or session management configurations, rather than attempting a specific fix.