API error and than get rate limit error without any work output

Resolved 💬 1 comment Opened Apr 29, 2026 by sanjaymandadi Closed May 31, 2026

Bug Description
API error and than limit issue Continue ⎿  API Error: Stream idle timeout - partial response received ✻ Churned for 16m 52s ❯ What is latest status? ⎿  API Error: Stream idle timeout - partial response received ✻ Churned for 44m 31s ❯ continue ⎿  You've hit your limit · resets 7:30am (America/Chicago)

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 2.1.119
  • Feedback ID: 9775fa15-f84b-42e0-a410-6334c162f665

Errors

[{"error":"AxiosError: timeout of 5000ms exceeded\n    at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:119:13291)\n    at emit (node:events:92:22)\n    at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:118:3321)\n    at request (/$bunfs/root/src/entrypoints/cli.js:121:2467)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-28T14:27:02.417Z"},{"error":"Error: Error normalizing tool input: ZodError: [\n  {\n    \"expected\": \"string\",\n    \"code\": \"invalid_type\",\n    \"path\": [\n      \"new_string\"\n    ],\n    \"message\": \"Invalid input: expected string, received undefined\"\n  }\n]\n    at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:5082:1010)\n    at map (native:1:11)\n    at BO6 (/$bunfs/root/src/entrypoints/cli.js:5082:556)\n    at NMq (/$bunfs/root/src/entrypoints/cli.js:8838:9510)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-28T17:41:12.213Z"},{"error":"Error: 429 {\"type\":\"error\",\"error\":{\"type\":\"rate_limit_error\",\"message\":\"This request would exceed your account's rate limit. Please try again later.\"},\"request_id\":\"req_011CaWfBavmPMFkxUBZhgVSG\"}\n    at generate (/$bunfs/root/src/entrypoints/cli.js:11:55343)\n    at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:4943)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-28T18:41:03.858Z"}…

Note: Content was truncated.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗