@JonhernandezIA What if people learned to govern their token usage instead?
Proper model selection for task delegation + planning = at least 40% cost saved
Read more:
https://t.co/Bc6xTtHtKJ
As per their docs, it's parsers record token usage while ingesting messages and usage events, so the database already knows the input, output, cache-creation, and cache-read tokens those agents have logged.
I know this reporting is in early phase, but is this reliable or just guesswork based on the above listed logs?
Wouldn't it be better to parse it from ~/.codex/sessions/* and log actual cost?
@GergelyOrosz I don’t think they aim for more premium users going forward.
We’ve been constantly throttled on top premium plans these past months already. It costs less and pays more to provide the government and top companies with premium models than the masses.
Thank you for this!
Memory and persistence is the single biggest source of chaos in the space right now.
After harnesses and loops, the next focus should be on a governance layer that sits on top of existing runtimes and tools, managing memory efficiently.
We won’t be able to “move fast and break things” for any longer because of these absurd costs and usage limits.
We don’t need another runtime or UI. Just a deterministic working-set selection so that persistent memory actually stays reliable, compact and cheap!