If your project's budget resets every month, the figure on the project page was wrong, and it got worse the longer the project ran.
A 20 hour monthly retainer three months old reported "-43.08 remaining (0%)". The allowance was one month's; the spend charged against it was every hour the project had ever had. A project comfortably inside its budget looked catastrophically over.
It now counts only the month you are looking at. The project page opens on the current month, with arrows either side and Return to this month once you have left it. Stepping back to a month that genuinely ran over shows that month over, without affecting the one you are in.
Nothing about your budgets changed — no setting, no number, no alert threshold. What changed is the arithmetic underneath the display. If you have been ignoring a red budget figure on a retainer, it is worth another look; and if you had raised a budget to stop it reading negative, you can put it back.
Projects on a fixed budget are unaffected: their budget is one running total for the life of the project, and they still open on all time.
On reports, a monthly budget is still per month. The Budget vs actual
table and the project-budget API compare a budget against whatever date range
you asked for, and narrowing that range would answer a different question than
the one you asked. So instead those rows now say budget is per month, and
the API returns budget_resets_monthly beside them — a 20 hour retainer over a
quarter shows 20 against 60, which is a project exactly on plan. For a
like-for-like figure, ask about a single calendar month, or read the project
page, which does the windowing for you.
The assistant knows this too, and will no longer tell you a retainer is over budget because you asked about a quarter.