The Vendor Removed the Cost Column
A number your vendor stops showing you is a number your vendor has decided you should not act on.
लपविलें तें उघड होय · What Is Hidden Comes to Light
नव्हे जाब देणें तुम्हां हें दुर्बळा । परि या गोपाळा सांगतसें ॥ १ ॥
लपविलें तें उघड होय शेवटीं । आपुली आपणा तुटी करूं नये ॥ २ ॥
तुका म्हणे खरें कळों येतें अंतीं । वरिवरी माती लोटूं नये ॥ ३ ॥
I am in no position to demand answers from you, but I will say this plainly: what is covered up surfaces in the end. Do not cut yourself off from your own reckoning by shovelling loose earth over the top of it.
The person at the spreadsheet
She has closed the books on engineering tooling for eleven straight months. Forty engineers, one Cursor subscription line, a per-person breakdown she rebuilt by hand in January because the vendor's export did not group the way her finance system needed. She is good at this. On the first Friday of every month she opens the usage dashboard, copies the dollar figures, and the column fills.
This Friday the dollar column is gone. Where it stood there are token counts, tens of millions of them, in a unit with no fixed relationship to rupees and no stable meaning across a model swap. She exports the CSV, because that is what you do. The chargedCents field comes back zeroed. Not only for August. For every historical event, including the eleven months she had already reconciled and signed off.
She has not lost this month's number. She has lost the eleven she thought she owned.
What she is actually up against
The obvious reading is that a vendor did something hostile, and the Hacker News thread took that reading to 321 points. The duller reading is worse for her.
Cursor's explanation is on the record and it is not stupid. Kevin Neilson wrote that the change was deliberate, driven by the difference between pooled enterprise usage and individual plans with included usage, and that displayed dollar amounts were often higher than what the user actually paid. A number that overstates what you owe generates support tickets all day.
Notice the shape of the repair. The confusing number was not corrected, annotated, or given a second column showing effective cost. It was replaced with a unit that cannot mislead anyone because it cannot be read at all. Tokens never overstate your bill. Tokens say nothing about your bill. The tickets stop, which was the goal, and the budgeting stops, which was somebody else's goal entirely.
So what she is up against is not malice. It is that her monthly close depended on a disclosure. Every number a SaaS vendor puts in front of you is a product decision, not an accounting fact, and it survives exactly as long as showing it costs the vendor less than hiding it. Cost visibility is cheap while pricing is simple and margins are comfortable. It gets expensive the moment a flat subscription starts subsidising heavy users, because the number invites precisely the behaviour that hurts: teams rate-limiting themselves, capping model selection, shifting cheap workloads to a competitor.
A cost column is not a feature. It is a disclosure, offered voluntarily, revocable without notice, by a company whose interests diverge from yours at the exact moment the number gets interesting.
What it costs to fix
She will get most of it back, and it will take her about three weeks she did not budget.
There is an on-demand spending figure on another page, and a CSV export that still carries cost for on-demand usage but not for the included portion, which is the part she needed. Team admins can pull per-user totals from a third screen. None of these reconcile cleanly, and none restore the eleven closed months.
Then the real work starts, and it is the work she should have done in January. Pull the usage API into the warehouse nightly. Compute cost from her own contracted rates instead of reading it off a screen. Reconcile against the vendor monthly and alert on the divergence, not the absolute. Two days of engineering and a standing job. It did not happen because the dashboard looked fine, and a number that has been correct for eleven months does not feel like a dependency.
Where Tuka comes in
Tukaram is blunt about the arithmetic of concealment: "लपविलें तें उघड होय शेवटीं" (what is hidden surfaces in the end). This is not a moral threat. It is a claim about time. The reckoning is not cancelled by being deferred, and the interest accrues to whoever was kept from seeing it.
But he does not leave it there, and the second line is the one that carries the hope. "आपुली आपणा तुटी करूं नये" (do not cut yourself off from your own reckoning). The warning is not aimed at the party doing the concealing. It is aimed at the person who accepts someone else's account of their position as their own. The vendor is behaving as vendors behave. What costs her money is having had no number of her own.
That is the reachable part. She cannot make Cursor restore the column, and no amount of anger in a forum thread will. She can hold her own reckoning, and once she does, the next vendor to remove a disclosure removes nothing from her. The third line tells her how to start: "वरिवरी माती लोटूं नये" (do not shovel loose earth over the top). Loose earth is the reconciliation skipped because the dashboard looked fine. It holds until someone leans on it. She leaned on it this Friday.
Build your own meter for anything above roughly ₹50,000 a month, and write into the next renewal that historical billing data stays exportable and immutable for the contract term. Cursor's lesson was never that a column vanished. It is that eleven closed months went with it, and they were only ever on loan.
Chetan Dhandal