claude-code - 💡(How to fix) Fix [Feature Request] Add support for creating GitHub issues via Claude Code [1 comments, 2 participants]

[{"error":"Error: Failed to delete keychain entry: security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.\n at RNq (/$bunfs/root/src/entrypoints/cli.js:259:287050)\n at async E_9 (/$bunfs/root/src/entrypoints/cli.js:412:898)\n at async MQ6 (/$bunfs/root/src/entrypoints/cli.js:412:796)\n at async xO_ (/$bunfs/root/src/entrypoints/cli.js:2712:2252)\n at async $WH (/$bunfs/root/src/entrypoints/cli.js:2737:5940)\n at async <anonymous> (/$bunfs/root/src/entrypoints/cli.js:2761:3410)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T07:18:35.019Z"},{"error":"Error: EISDIR: illegal operation on a directory, read '/Users/julien.cruau/dev2/wolfgangparis-v2/src/app/robots.txt'\n at kOH (/$bunfs/root/src/entrypoints/cli.js:1678:144)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T07:59:16.484Z"},{"error":"Error: File does not exist. Note: your current working directory is /Users/julien.cruau/dev2/wolfgangparis-v2.\n at call (/$bunfs/root/src/entrypoints/cli.js:4802:7647)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T08:00:32.497Z"}]

TL;DR

Check keychain settings and file permissions to resolve errors preventing issue creation on GitHub.

Guidance

• Verify keychain entry existence and permissions to resolve the "SecKeychainSearchCopyNext" error.
• Check file system permissions and directory structure to address the "EISDIR: illegal operation on a directory" error.
• Ensure the current working directory is correct and the required files exist to fix the "File does not exist" error.

Example

No code snippet is provided as the issue seems to be related to environment and file system configuration rather than code.

Notes

The provided errors suggest issues with keychain settings, file permissions, and directory structure. Resolving these environment-related problems should allow the auto feature to create issues on GitHub.

Recommendation

Apply workaround: Check and adjust keychain settings, file permissions, and directory structure to resolve the errors, as the issue seems to be environment-specific rather than a version-related problem.