What kind of problem?
Session or daily limit counted incorrectly
What you are seeing
Summary
The interface does not display an active hourly session status/countdown indicator, and Freebucks are not being deducted despite continuous usage and multiple tool executions for over 2 hours.
Description
While running multiple tasks and prompt executions across a 5+ hour period, the following anomalies were observed:
- No Hourly Session Indicator: There is no visible hourly session status, active session timer, or banner displayed in the sidebar or top bar.
- Quota / Freebucks Non-deduction: The Freebucks balance remains unchanged at
5 without any deductions or usage tracking being registered, even though multiple complex edits, test runs, and reasoning steps have completed.
Steps to Reproduce
- Launch the Freebuff client.
- Select model
GLM 5.3 Flash Max.
- Run continuous workflows across multiple threads/tasks for more than 2 hours.
- Check the left sidebar:
- Notice no hourly session timer/indicator is displayed.
- Notice the Freebucks balance remains static at
5.
Expected Behavior
- When an hourly session starts, a session status or countdown timer should clearly indicate the active window.
- Usage beyond the free hourly limits should either start deducting Freebucks or prompt session expiration as intended by the rate-limiting system.
Actual Behavior
- No session indicator is present.
- Workflows continue executing indefinitely without session tracking or Freebucks deduction.
Environment & Context
- Client: Freebuff / Codebuff UI
- Selected Model: GLM 5.3 Flash Max
- OS: Windows
- Freebucks Balance: 5 (Unchanged)
- Session Duration: > 5 hours
Screenshots
Model involved
glm-5.3-flash
What kind of problem?
Session or daily limit counted incorrectly
What you are seeing
Summary
The interface does not display an active hourly session status/countdown indicator, and Freebucks are not being deducted despite continuous usage and multiple tool executions for over 2 hours.
Description
While running multiple tasks and prompt executions across a 5+ hour period, the following anomalies were observed:
5without any deductions or usage tracking being registered, even though multiple complex edits, test runs, and reasoning steps have completed.Steps to Reproduce
GLM 5.3 Flash Max.5.Expected Behavior
Actual Behavior
Environment & Context
Screenshots
Model involved
glm-5.3-flash