Usage limit cooldown extends after the limit is exhausted

Description

Issue: Usage limit cooldown extends after the limit is exhausted

I’m experiencing an issue where the usage-limit cooldown appears to reset or extend unexpectedly.

Environment

• OpenCode: 1.18.31
• Model: Muse Spark 1.3 FREE
• OS: Ubuntu 24.04 LTS

Timeline

• September 19, ~1:30 PM: I exhausted my usage limit.
• Initially, the UI indicated that I should try again after ~19 hours.
• On September 20, instead of the cooldown expiring as expected, the same warning appeared again, but now it said to try again after ~22 hours.

This suggests that the cooldown may be restarting or being recalculated after the limit is reached, rather than counting down from the original exhaustion time.

Expected behavior

Once the usage limit is exhausted, the cooldown should have a fixed reset time. The remaining time should continuously decrease until the limit resets.

For example, if the limit is exhausted at 1:30 PM on September 19 and the cooldown is 19 hours, the reset should occur at approximately 8:30 AM on September 20, rather than changing to a new ~22-hour cooldown.

Actual behavior

The cooldown appears to increase/reset after the initial warning:

19 hours remaining → next day → 22 hours remaining

This makes the limit effectively unavailable for significantly longer than the initially reported cooldown period.

Additional information

The issue occurs while using OpenCode 1.18.31 with Muse Spark 1.3 FREE on Ubuntu 24.04 LTS.

I’m not sure whether this is caused by OpenCode, the model/provider, or the usage-limit service, but the reported cooldown time appears inconsistent.

Plugins

dcp

OpenCode version

1.18.31

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Start by reproducing the reported 19-hour-to-22-hour cooldown change with OpenCode 1.18.31, Muse Spark 1.3 FREE, Ubuntu 24.04, and the dcp plugin. Trace whether the reset time comes from OpenCode, the model/provider, or the usage-limit service; no source file, test, or reproduction steps are named. Done means the cooldown has a fixed reset time and continuously decreases after exhaustion.