Error: Claude Sonnet 4.5 - 500

[lunarguide-bijit]

Error Details

Model: Claude Sonnet 4.5
Provider: anthropic (continue-proxy)
Status Code: 500

Error Output

"{\"type\":\"error\",\"error\":{\"type\":\"invalid_request_error\",\"message\":\"You have reached your specified API usage limits. You will regain access on 2026-04-01 at 00:00 UTC.\"},\"request_id\":\"req_011CZFkuF59CzfxJQBRmeDer\"}"

Additional Context

Even after I have the credits it's giving error

[lunarguide-bijit]

Error logs

Error handling webview message: {
  "msg": {
    "messageId": "a82298f7-cc49-4c8a-a077-b68fc09ab516",
    "messageType": "llm/streamChat",
    "data": {
      "completionOptions": {
        "reasoning": true,
        "reasoningBudgetTokens": 2048
      },
      "title": "Claude Opus 4.5",
      "messages": [
        {
          "role": "system",
          "content": "<important_rules>\n  You are in chat mode.\n\n  If the user asks to make changes to files offer that they can use the Apply Button on the code block, or switch to Agent Mode to make the suggested updates automatically.\n  If needed concisely explain to the user they can switch to agent mode using the Mode Selector dropdown and provide no other details.\n\n  Always include the language and file name in the info string when you write code blocks.\n  If you are editing \"src/main.py\" for example, your code block should start with '```python src/main.py'\n\n  When addressing code modification requests, present a concise code snippet that\n  emphasizes only the necessary changes and uses abbreviated placeholders for\n  unmodified sections. For example:\n\n  ```language /path/to/file\n  // ... existing code ...\n\n  {{ modified code here }}\n\n  // ... existing code ...\n\n  {{ another modification }}\n\n  // ... rest of code ...\n  ```\n\n  In existing files, you should always restate the function or class that the snippet belongs to:\n\n  ```language /path/to/file\n  // ... existing code ...\n\n  function exampleFunction() {\n    // ... existing code ...\n\n    {{ modified code here }}\n\n    // ... rest of function ...\n  }\n\n  // ... rest of code ...\n  ```\n\n  Since users have access to their complete file, they prefer reading only the\n  relevant modifications. It's perfectly acceptable to omit unmodified portions\n  at the beginning, middle, or end of files using these \"lazy\" comments. Only\n  provide the complete file when explicitly requested. Include a concise explanation\n  of changes unless the user specifically asks for code only.\n\n</important_rules>\n\n# CLAUDE.md\n\nThis file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.\n\n## Build and Run Commands\n\n```bash\n# Development (with hot reload using entr)\nfind src/ | entr -r mvn compile exec:java\n\n# Development (single run)\nmvn compile exec:java\n\n# Production build (creates fat JAR)\nmvn clean package\n\n# Run production JAR\njava -jar target/admission-1.0-SNAPSHOT.jar\n\n# Run tests\nmvn test\n\n# Docker build\ndocker build -t admission-backend .\ndocker run -p 8080:8080 admission-backend\n```\n\n## Architecture Overview\n\nThis is a **custom lightweight Java backend** (NOT Spring Boot) with embedded Tomcat and LibSQL/SQLite.\n\n### Technology Stack\n- Java 16, Maven build\n- Embedded Tomcat 9.0.73 (async servlet pattern)\n- LibSQL/SQLite database with HikariCP connection pooling\n- Gson for JSON, JWT for authentication, GitHub OAuth\n- SLF4J + Logback for logging\n\n### Layered Architecture\n```\nHTTP Request\n    → JwtAuthFilter (validates JWT, sets userId attribute)\n    → CORSFilter\n    → ApiServlet (async, thread pool)\n    → WebServerAPI implementations (BoardAPI, AuthAPI, etc.)\n    → Service layer (business logic)\n    → Repository layer (SQL/JDBC)\n    → DatabaseManager (HikariCP)\n    → LibSQL database\n```\n\n### Key Packages\n```\nxyz.bijit.admission/\n├── config/          # AppConfig (singleton), AppConstants (table/column names), ThreadPoolConfig\n├── db/              # DatabaseManager (HikariCP connection pool)\n├── di/              # Container (simple singleton DI container)\n├── server/          # TomcatServer, ApiServlet (async handler)\n├── auth/            # GitHub OAuth + JWT authentication\n├── kanban/          # Kanban board module (boards, lists, tasks)\n│   ├── api/         # REST controllers implementing WebServerAPI\n│   ├── service/     # Business logic interfaces and implementations\n│   ├── repository/  # SQL-based data access\n│   ├── model/       # Entity POJOs\n│   └── utils/       # HATEOAS links, pagination helpers\n└── notes/           # Example notes module (legacy)\n```\n\n### Dependency Injection\nThe `Container` class is a simple singleton that manually registers and retrieves services. Services are registered at startup and retrieved via `Container.getInstance().get(ServiceClass.class)`.\n\n### Authentication Flow\n1. `GET /api/auth/github/login` → redirects to GitHub OAuth\n2. GitHub redirects to `/api/auth/github/callback?code=xxx`\n3. Server exchanges code for access token, creates/updates user, generates JWT\n4. JWT can be passed via cookie (`kanban_auth_token`) or `Authorization: Bearer <token>`\n5. `JwtAuthFilter` validates token and sets `userId` request attribute\n\n### Adding a New Feature\n1. Create model in `model/` package (POJO with getters/setters)\n2. Add table/column constants to `AppConstants.java`\n3. Create schema in `db/CreateXxx.java` and register in `DatabaseManager.initializeSchemaStatements()`\n4. Create repository interface and SQL implementation in `repository/`\n5. Create service interface and implementation in `service/`\n6. Create API controller implementing `WebServerAPI` in `api/`\n7. Register all components in `Container.configure()`\n\n### Response Format\nREST responses use HATEOAS with `_links` for navigation. See `kanban/utils/HateoasUtils.java` for link generation.\nAll APIs must be HATEOAS compliant: every successful resource or collection response must include a `_links` object with discoverable navigation/action links.\n\n## Configuration\n\nKey settings in `src/main/resources/application.properties`:\n- `db.*` - Database connection (remote LibSQL/Turso)\n- `server.port` - Default 8080\n- `client.address` - Frontend URL for CORS (http://localhost:5173)\n- `oauth.github.*` - GitHub OAuth credentials\n- `oauth.jwt.*` - JWT secret and expiration\n\n## Important Patterns\n\n- Use constants from `AppConstants` for all table/column names\n- Use try-with-resources for all JDBC operations\n- Any ownership column like `user_id` must be a real SQL foreign key to `users(id)` (for example `FOREIGN KEY (user_id) REFERENCES users(id) ON DELETE CASCADE`)\n- Services use `ThreadLocal` for collections to avoid contention in async context\n- All API handlers must be thread-safe (async servlet model)\n- Use `HateoasUtils` to add navigation links to responses"
        },
        {
          "role": "user",
          "content": [
            {
              "type": "text",
              "text": "hi"
            }
          ]
        }
      ],
      "messageOptions": {
        "precompiled": true
      }
    }
  }
}

Error: HTTP 500 Internal Server Error from https://api.continue.dev/model-proxy/v1/chat/completions

{"error":"{\"type\":\"error\",\"error\":{\"type\":\"invalid_request_error\",\"message\":\"You have reached your specified API usage limits. You will regain access on 2026-04-01 at 00:00 UTC.\"},\"request_id\":\"req_011CZKRZeTZYmtHETbNyVkwV\"}","code":"INTERNAL_ERROR"}

[at-the-prime]

The error still exist

@RomneyDa

[RomneyDa]

Thanks for the bump! will get this fixed asap

[RomneyDa]

Back up! Thanks for the report