claude-code - 💡(How to fix) Fix [Bug] Claude Code corrupts local .env file during operation [1 comments, 2 participants]

[{"error":"McpToolCallError: Input Error\n\nThere was an HTTP 404 error with your request to the Sentry API.\n\nAPI error (404): API request failed: Not Found\n. Please verify the parameters are correct.\n\nYou may be able to resolve the issue by addressing the concern and trying again.\n at iF5 (/$bunfs/root/src/entrypoints/cli.js:4892:63)\n at QB7 (/$bunfs/root/src/entrypoints/cli.js:4892:1409)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-30T23:18:02.816Z"},{"error":"McpToolCallError: Input Error\n\nThere was an HTTP 404 error with your request to the Sentry API.\n\nAPI error (404): API request failed: Not Found\n. Please verify the parameters are correct.\n\nYou may be able to resolve the issue by addressing the concern and trying again.\n at iF5 (/$bunfs/root/src/entrypoints/cli.js:4892:63)\n at QB7 (/$bunfs/root/src/entrypoints/cli.js:4892:1409)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-30T23:18:18.661Z"},{"error":"McpToolCallError: Input Error\n\nThere was an HTTP 400 error with your request to the Sentry API.\n\nAPI error (400): Error parsing search query: Boolean statements containing "OR" or "AND" are not supported in this search\n\nYou may be able to resolve the issue by addressing the concern and trying again.\n at iF5 (/$bunfs/root/src/entrypoints/cli.js:4892:63)\n at QB7 (/$bunfs/root/src/entrypoints/cli.js:4892:1409)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-30T23:19:36.209Z"}]

TL;DR

Verify the parameters and search query in the Sentry API request to resolve the HTTP 404 and 400 errors.

Guidance

• Check the Sentry API documentation to ensure the request parameters are correct and supported.
• Review the search query to ensure it does not contain unsupported Boolean statements with "OR" or "AND".
• Verify the API endpoint URL and version to ensure it is correct and not deprecated.
• Consider checking the API request headers and authentication to ensure they are valid and properly configured.

Notes

The issue seems to be related to incorrect or unsupported API requests to the Sentry API. Without more information about the specific request being made, it's difficult to provide a more detailed solution.

Recommendation

Apply workaround: Verify and correct the API request parameters and search query to ensure they are valid and supported by the Sentry API.