Bug spotted? (first post, sorry)

Hey, thanks for the detailed report. Let’s break it down, there are a few different things here, and none of them is a bug where usage gets lost.

About the usage that “isn’t” in the dashboard. Your run is recorded correctly on the backend, no usage was lost. The fact that the Usage page shows 0% or doesn’t update is a known display bug on the Usage page itself. The data exists on the backend, the frontend just doesn’t show it. Thread here: High Load, and usage percentage shows 0% and does not update

Small note: on July 8 there was a broader incident. Along with the display bug, there were also issues with limit enforcement, but it was fixed the same day. Your run was on July 13, so it’s outside that window, so it most likely doesn’t apply here. Also, on a free-tier account you’re not billed in dollars. If you hit your included limit, you’d just get blocked, not charged. If you still have concerns about spend for a specific period, email [email protected] and they can check your exact account. We don’t handle account-specific spend checks on the forum.

Why the HTML used ~9%, but a PNG yesterday was only 2%. That’s expected. Generating a full single-file website is a multi-step agent loop with a lot of output tokens. You ended up with ~37k output tokens, plus the model rendered and screenshotted the result to self-check. One PNG image is just one call. Fable 5 High is a premium model, and on the free-tier included pool it gets used up quickly. For large generations I’d suggest Auto or a simpler model, it’ll be noticeably cheaper.

About msedge --headless --screenshot and the Chromium ERROR. That’s normal behavior. The agent rendered its HTML and took a screenshot to verify the result. The fallback_task_provider.cc line is harmless stderr from Edge, not a Cursor defect.

“Taking longer than expected” is a standard message on long turns, not an error.

Request ID for next time, it’s helpful for AI bugs: top-right chat menu > Copy Request ID (with Privacy Mode off).

Let me know if the Usage page still doesn’t start updating after some time.