fix: address critical issues with Cursor, MiniMax, and OpenCode #280
Conversation
…ders - Fix Cursor plan limit detection for Pro_Student plans - Use region-specific API endpoint for MiniMax usage fetch - Improve OpenCode error message parsing for HTTP 500 errors
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f0674f2ae0
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| } | ||
|
|
||
| var request = URLRequest(url: self.apiRemainsURL) | ||
| var request = URLRequest(url: region.remainsURL) |
There was a problem hiding this comment.
In MiniMaxUsageFetcher.fetchUsage(apiToken:) the request now targets region.remainsURL, which resolves to the platform host (platform.minimax.io/platform.minimaxi.com) and the cookie “openplatform” remains path. The MiniMax docs in this repo specify the API token endpoint as https://api.minimax.io/v1/coding_plan/remains (different host and path) and reserve the platform host for cookie-based fetches (GET {host}/v1/api/openplatform/coding_plan/remains). This change will cause API-token-only users (especially global region) to hit the cookie endpoint and likely receive 404/401 responses, so usage fetch will fail for the API-token flow.
Useful? React with 👍 / 👎.
|
I need this PR merged, can we prioritize this? |
|
@steipete Thank you for fix this! |
2 participants
This PR addresses several critical issues reported in the repository:
These changes improve the reliability and accuracy of usage tracking for these providers.