A record of the work you already did
My usage
Which agent used how much, in which project?
Demo: every log, project and commit here is invented. Your own agent logs are not read.
Preparing local logs…
Tokens cover the selected sessions in full. The period selects sessions by their last activity; it is not spending split by day.
Before comparing these records
File access warnings cover all selected log folders. Session and pricing limits follow the main filters.
Roodof cannot tell whether logs were deleted before its first read. It cannot recover records it never read. A successful read does not prove complete account history.
How to check or recover recordsRecorded quality reasons
My work
Give one job a name, then link its Claude and Codex sessions from session details.
No work groups yet. Create one to collect the sessions for a job.
Goal and outcome
Your entry applies to the whole work, independently of filters. Roodof does not infer completion or quality from tests, Git or usage.
Edit goal and outcome
Latest saved version
Your draft stays in the form. Review the saved values below before keeping your draft for the next save or using the saved version. Neither choice writes a change.
Some selected sessions have incomplete usage or attribution. These are known recorded values, not a complete measurement.
Recorded observations
These follow the main filters and cover whole linked sessions. Test/build counts describe each session's latest visible result; Git activity is a time association. They do not prove that the work met its goal.
Changes to try · weekly follow-up
Record a change to this work, then review two seven-day windows. Uses dated responses in all linked sessions, independently of the main filters. No new model calls.
A lower token count does not prove better results, saved money or reduced account quota. Logs may cover only part of a week. Compare the work's outcome separately.
Open a session below and link it to this work.
Usage follows the main filters and covers whole sessions, not the cost of one change. Search and data-quality list filters do not change this scope. A session may belong to several works; their totals cannot be added. The summary counts each linked session once.
API equivalents use available prices; unpriced usage may be omitted. They are not your subscription bill.
Titles and links stay on this computer and are excluded from normal JSON summaries. Private backups include them. Missing sessions remain linked by their saved codes; Roodof does not attach a different session automatically.
What did the agents read and produce?
These four parts are separate and add up to the total. Reasoning is part of output and is not added twice. Reading from the cache also uses resources.
Where does usage build up?
Split shown in the logs
Look into your sessions.
This list filter does not change totals or JSON scope.
Search narrows only this list; the summary above and the downloaded JSON follow the main filters. Open a session to see coincident local Git events. The record span includes waiting; it is not continuous working time.
Scroll sideways for more columns. With a keyboard, focus the table area and use the left and right arrows.
| Project / agent / session | Start → last activity | Total tokens | Model calls | Input from cache | Did it pay off? |
|---|
No session matches your search.
No sessions in this selection.
Widen the filters, or read the logs again after using your agent.