Where to see your Codex usage, and what local logs add
Codex’s remaining limits and their reset times are on the usage dashboard at chatgpt.com/codex/settings/usage, and inside a Codex CLI session /status shows the limits left. Which projects Codex worked on this week is a different question, answered by the session logs on this Mac. Hina only reads the latter.
Remaining allowance is on the status command and account page
Hina does not query your account allowance. Local logs record calls that have already happened, including the model, project, and tokens; they do not show your remaining allowance.
Calls that have already happened are stored in ~/.codex/sessions and the archive directories. The files keep the model, project, time, and tokens. The logs do not contain a remaining allowance. They can only tell you how much has been used, and where.
Local logs record tokens for each thread
AI usage metadata in Hina needs a separate permission and is off by default. Once it is on, Hina only reads local logs from Claude Code and Codex, and takes the model, project, time, and tokens. What you asked AI needs a separate permission, also off by default. The usage numbers do not include the sentence you typed at the time.
Tokens record how much that thread consumed. They are not how many times you asked, and they are not how long you stayed on the project. Several rounds of revision on the same thread raise the token count, while that stay on the Trail is still the foreground app’s duration and input count. For example, on Friday you revise the layout of an article in the blog repository and Codex runs four rounds. Usage shows the tokens from those four rounds. Whether the foreground was the editor or the terminal, the stay is still recorded on that app. More questions do not mean the article is finished. You have to open the repository to see whether the file is done, and Hina will not confirm that step for you.
Date folders are the creation day, later use follows event time
Under ~/.codex/sessions, folders are split by date. The day on a folder is the day the thread was created, not the day each later message happened. A thread created on Tuesday in the client site repository, then opened again on Friday to edit the same page, would count those Friday rounds entirely as Tuesday if you went only by the directory name. Friday’s usage would look as if those rounds never happened.
When Hina reads Codex logs, it assigns the day by event time, not by directory name. Records written later into an old thread count on the day they actually happened. A day runs from 4:00 a.m. to 4:00 a.m. the next day. A call that crosses 4:00 a.m. enters the next working day, on the same day boundary as the other records for that day.
If you reconcile by calendar day, 11:00 p.m. Friday through 1:00 a.m. Saturday splits into two days. Hina does not cut the day that way. If the client site thread continues past 4:00 a.m., tokens from before 4:00 stay on the previous working day, and only what happens after 4:00 enters the next day. That is independent of the creation day on the directory.
View Claude Code next to Codex without totaling them into a cost
On the same day, tokens from Claude Code and Codex can be viewed together, so you can see which project had more and which model had more. Each side’s local logs have their own numbers, and the table keeps each tool and model on its own row. Viewing them side by side is for recalling which models you used that day and which projects they landed on. The seven daily bars in AI in your work add the two tools’ input and output only to show how the scale moved, not to turn them into one bill.
These two numbers also cannot be turned into money. The blog repository uses Codex, and the client site repository uses Claude Code. Each plan is counted on its own. The unit price and how much this period has deducted are only on each account page. Local logs do not contain that bill, and Hina does not estimate one. The side with higher tokens is not necessarily the side that cost more. How much was deducted still has to be read from the numbers on the account page.