Problem (one or two sentences)
After switching to a free model, the Zoo Code extension still shows the old model name in the settings UI and displays credit notifications, as if the user is on a paid plan. The model actually changes (confirmed by responses), but the billing system treats it as a paid model, creating a UI sync + billing mismatch.
Context (who is affected and when)
Any user who switches from a paid model to a free one in the Zoo Code extension will see this issue. The problem appears right after switching the model — the UI still shows the old paid model’s name, and the system starts asking for credits, even though the user is now on a free plan.
Reproduction steps
- Open Zoo Code extension in your editor.
- Go to settings and select a free model (e.g., minimax/minimax-m3-free).
- Notice that the UI still shows the previously selected paid model name in the settings field — it does not update.
- Go to your profile and check the active model — the profile shows it has been updated.
- Send a request using the selected model.
- Observe that the system asks for credits (credit notification appears), even though you are on a free model.
- The model actually works (responses change), but the billing system treats it as a paid plan.
Expected result
The selected free model name should immediately appear in the settings UI. The system should not request or show credit notifications for a free model. The billing behavior should match the selected plan — free models must work without any credit or payment prompts.
Actual result
After switching to a free model, the settings UI still shows the old model name (it does not update). The profile shows the model has been updated. However, when sending a request, the system displays a credit notification and behaves as if the user is on a paid plan, even though the selected model is free.
Variations tried (optional)
I tested this only with Zoo Code's built-in provider. No other browsers or devices were used. The issue appeared when switching from a paid model to a free model within the same Zoo Code environment.
App Version
latest
API Provider (optional)
None
Model Used (optional)
minimax/minimax-m3-free, poolside/laguna-s-2.1-free
Zoo Code Task Links (optional)
No response
Relevant logs or errors (optional)
Date/time: 2026-09-02T12:15:09.357Z
Extension version: 3.80.1
Provider: zoo-gateway
Model: anthropic/claude-sonnet-4 (I chose the free model; as of writing this, it’s a new bug—already the third or fourth one, I’ve lost count.)
Request timed out.
Date/time: 2026-09-02T12:41:24.645Z
Extension version: 3.80.1
Provider: zoo-gateway
Model: anthropic/claude-sonnet-4
402
402 "Insufficient credits"
Zoo Gateway: недостаточно кредитов. Добавьте кредиты, чтобы продолжить.
Problem (one or two sentences)
After switching to a free model, the Zoo Code extension still shows the old model name in the settings UI and displays credit notifications, as if the user is on a paid plan. The model actually changes (confirmed by responses), but the billing system treats it as a paid model, creating a UI sync + billing mismatch.
Context (who is affected and when)
Any user who switches from a paid model to a free one in the Zoo Code extension will see this issue. The problem appears right after switching the model — the UI still shows the old paid model’s name, and the system starts asking for credits, even though the user is now on a free plan.
Reproduction steps
Expected result
The selected free model name should immediately appear in the settings UI. The system should not request or show credit notifications for a free model. The billing behavior should match the selected plan — free models must work without any credit or payment prompts.
Actual result
After switching to a free model, the settings UI still shows the old model name (it does not update). The profile shows the model has been updated. However, when sending a request, the system displays a credit notification and behaves as if the user is on a paid plan, even though the selected model is free.
Variations tried (optional)
I tested this only with Zoo Code's built-in provider. No other browsers or devices were used. The issue appeared when switching from a paid model to a free model within the same Zoo Code environment.
App Version
latest
API Provider (optional)
None
Model Used (optional)
minimax/minimax-m3-free, poolside/laguna-s-2.1-free
Zoo Code Task Links (optional)
No response
Relevant logs or errors (optional)