What happened
Bug: Freebucks are consumed after automatic update even though my usage limit was not reached
Description
I was using the DeepSeek V4 model with my 25 freebucks. After around 4 minutes, Freebuff detected an update and automatically restarted:
𐙚 max · ~/D/h/pyclaw · ↑ 4h 47m · cpu 39% · main●
╰─❯ freebuff
Update available: 0.0.173 → 0.0.174
Download complete! Starting Freebuff...
After Freebuff reopened, my 25 freebucks had already been completely consumed.
This is unexpected because I had not reached my 1-hour usage limit. The update/restart appears to have happened while I was actively using the model, and immediately afterward my remaining freebucks were reduced to 0.
Honestly, this feels pretty bad from a user perspective because it looks like the automatic update consumed my entire freebucks balance.
Expected behavior
Updating/restarting Freebuff should not consume freebucks that were not actually used.
The freebucks balance should accurately reflect actual model usage, regardless of whether an application update happens during the session.
Actual behavior
After the automatic update/restart, my freebucks balance went from 25 → 0, despite having used the service for only around 4 minutes and not reaching the 1-hour limit.
Environment
- Model: DeepSeek V4
- Freebucks before update: 25
- Approx. usage before update: 4 minutes
- Freebuff version: 0.0.173 → 0.0.174
- Usage limit: 1 hour
- Freebucks after restart: 0
Possible issue
It seems possible that the usage/freebucks accounting is incorrectly handling an active session when Freebuff automatically updates and restarts.
Please check whether the update/restart can cause the current session to be incorrectly charged or whether the usage state is being persisted incorrectly.
Steps to reproduce
Steps to reproduce
- Start Freebuff with a balance of 25 freebucks.
- Use the DeepSeek V4 model.
- Continue using it for a few minutes.
- Have Freebuff automatically detect and install an update.
- Freebuff restarts.
- Check the freebucks balance.
Where does this happen?
CLI (terminal client)
Operating system
Linux
Version
0.0.174
Model
deepseek-v4.1-flash
Logs or screenshots
What happened
Bug: Freebucks are consumed after automatic update even though my usage limit was not reached
Description
I was using the DeepSeek V4 model with my 25 freebucks. After around 4 minutes, Freebuff detected an update and automatically restarted:
After Freebuff reopened, my 25 freebucks had already been completely consumed.
This is unexpected because I had not reached my 1-hour usage limit. The update/restart appears to have happened while I was actively using the model, and immediately afterward my remaining freebucks were reduced to 0.
Honestly, this feels pretty bad from a user perspective because it looks like the automatic update consumed my entire freebucks balance.
Expected behavior
Updating/restarting Freebuff should not consume freebucks that were not actually used.
The freebucks balance should accurately reflect actual model usage, regardless of whether an application update happens during the session.
Actual behavior
After the automatic update/restart, my freebucks balance went from 25 → 0, despite having used the service for only around 4 minutes and not reaching the 1-hour limit.
Environment
Possible issue
It seems possible that the usage/freebucks accounting is incorrectly handling an active session when Freebuff automatically updates and restarts.
Please check whether the update/restart can cause the current session to be incorrectly charged or whether the usage state is being persisted incorrectly.
Steps to reproduce
Steps to reproduce
Where does this happen?
CLI (terminal client)
Operating system
Linux
Version
0.0.174
Model
deepseek-v4.1-flash
Logs or screenshots