claude-code - 💡(How to fix) Fix [Feature Request] Add blanket permission allow option to reduce repeated prompts [1 comments, 2 participants]

[{"error":"Error: console.error: [bun] Warning: ws.WebSocket 'unexpected-response' event is not implemented in bun\n at K (B:/~BUN/root/src/entrypoints/cli.js:547:10765)\n at emitWarning (ws:43:42)\n at #onOrOnce (ws:170:18)\n at KQ8 (B:/~BUN/root/src/entrypoints/cli.js:3246:4680)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-08T11:47:56.800Z"},{"error":"Error: Tool mcp__plugin_vercel_vercel__authenticate not found\n at glK (B:/~BUN/root/src/entrypoints/cli.js:2012:30437)\n at SA (B:/~BUN/root/src/entrypoints/cli.js:498:20987)\n at bA (B:/~BUN/root/src/entrypoints/cli.js:498:39525)\n at MX (B:/~BUN/root/src/entrypoints/cli.js:498:50218)\n at wCH (B:/~BUN/root/src/entrypoints/cli.js:498:86889)\n at YCH (B:/~BUN/root/src/entrypoints/cli.js:498:86860)\n at K78 (B:/~BUN/root/src/entrypoints/cli.js:498:86698)\n at $78 (B:/~BUN/root/src/entrypoints/cli.js:498:82030)\n at IH (B:/~BUN/root/src/entrypoints/cli.js:498:6360)\n at Mh6 (B:/~BUN/root/src/entrypoints/cli.js:491:6386)","timestamp":"2026-04-08T11:59:41.148Z"},{"error":"McpToolCallError: MCP error -32602: Input validation error: Invalid arguments for tool get_deployment_build_logs: [\n {\n "code": "invalid_type",\n "expected": "string",\n "received": "undefined",\n "path": [\n "idOrUrl"\n ],\n "message": "Required"\n }\n]\n at gkK (B:/~BUN/root/src/entrypoints/cli.js:1622:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-08T12:01:05.673Z"},{"error":"McpToolCallError: API error occurred: Status 401 Content-Type "application/json; charset=utf-8". Body: {"error":{"code":"unauthorized","message":"You are not allowed to access this endpoint."}}\n at gkK (B:/~BUN/root/src/entrypoints/cli.js:1622:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-08T12:01:12.864Z"}]

TL;DR

The issue can be mitigated by addressing the "Input validation error" and "unauthorized" errors, possibly by providing required arguments and authenticating correctly.

Guidance

• Verify that all required arguments, such as "idOrUrl", are provided when calling the "get_deployment_build_logs" tool.
• Check authentication credentials and ensure that the user has the necessary permissions to access the endpoint.
• Review the error messages for any specific details about the missing permissions or invalid arguments.
• Consider checking the documentation for the "get_deployment_build_logs" tool to ensure that the correct arguments are being passed.

Notes

The provided error messages suggest that there are two main issues: an "Input validation error" due to missing required arguments, and an "unauthorized" error due to insufficient permissions. Addressing these two issues may resolve the problem.

Recommendation

Apply workaround: Provide required arguments and authenticate correctly, as the errors suggest that these are the primary causes of the issue.