OpenAI Watch posted an update
OpenAI's developer account, OpenAIDevs, spent late Thursday pointing Codex users towards usage visibility: a breakdown of how tasks, subagents and individual chats each contribute to your Codex usage, so you can make, in the account's words, more informed choices about your workflow.
Why it mattersThe practical value is the attribution. Anyone running agent workflows has nursed the suspicion that one eager subagent is quietly eating the budget. Per-task and per-chat views turn that suspicion into an answer, and ideally into a restructured workflow. No documentation, changelog or pricing came with the post, so read it as a nudge about a capability rather than a launch. Even so, it lands in the middle of the industry's running argument about coding-agent costs, which have a reputation for climbing while nobody is watching.
Discuss: Does per-subagent usage breakdown actually change how people structure agent work, or does it just make the invoice more readable?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.