How to reconstruct your workday
At the end of a busy day you may remember the last task but not what changed in the morning. A ranking of apps gives you totals. Rebuilding the day means lining up time, projects, what you asked and what the repository shows. Here is an order that works.
Start with one thing you remember
Open Hina and select the day on the Trail. Look for a document title, a page path or a project name you recognize, check which apps surround it, then return to Day to see how long it took. A specific anchor is usually more useful than the largest number, and guessing from the biggest block tends to make the longest meeting look like the point of the day.
The span between the first and last record is not your working time. It can contain time away, or hours when Hina was not running. If window titles were off that day, the Trail has only app names, and the project breakdown and Search records can fill in some of the rest. Leave the stretches with no record empty.
Read the day from the daily report
The menu bar item has Today's report, and Day has a Daily report button. The report opens with one line of totals, then Work that day, with each project's local commits, What you asked AI and Recorded activity, then any local version tags under Confirmed outcomes and anything the repository cannot prove under In progress and unconfirmed. Worth a look comes next and compares the day with your usual two weeks, for example 39 minutes more deep work than usual.
Rhythm of the day states when recording began and ended, the hour with the most work, how many periods you were away and for how long, the gaps shorter than 5 minutes, and any time Hina was not recording. Attention gives the longest stretch of deep work with its start time and project, how often you were interrupted and by what, and the most common switch. Expand Evidence for a per-project table, then each project's local commits and what you asked AI. If a source could not be read, a note before Evidence says the report may be incomplete.
The report can be copied or exported as Markdown, and in a terminal Hina --daily yesterday prints the same report as text. Building a report needs the trial of seven recorded days or an activated license.
Separate a request from a result
With Read agent sessions on, the prompts in the report show what you meant to do, and the local commits show what the repository actually recorded. Read both without assuming that a nearby commit fulfilled a particular request. Add the project folders under Settings, Data, Project folders used in reports, because Hina reads no repository you have not chosen.
If you asked an assistant to review the export code in the morning and see an export fix commit in the afternoon, open the project and confirm the change. The report has a section called In progress and unconfirmed for what the repository cannot prove, such as a change sitting on a branch, uncommitted work in the folder, or local commits with no tag, merge or closure record. Hina does not query GitHub, so pull request, issue and release status stay outside what it can say.
Commits with timestamps inside a stretch you were away are flagged under Worth a look, along with how many of them had an AI session open on that repository at the time. That records an overlap in time. It does not say who wrote the change, and it does not turn the absence into working time.
Check how time was assigned to projects
Hina names a project from the repository path in a window title and, with agent sessions on, from the working directory of the Claude Code or Codex session that was running. Day shows the three biggest projects of the day in a Projects list. Hover over a bar to see its total split into From titles and From surrounding activity, where the second is time Hina inferred from agent sessions and nearby activity for windows whose titles named no project. Holding the pointer over the list shows the share of active time that maps to a project at all. With window titles off, the list is replaced by a note that projects are read from paths in window titles.
Leave room for the gaps
The report and the Trail state what is missing instead of filling it in. The report has a line for periods away and time Hina was not recording. On a day with no window titles, Day notes that none were read, leaving projects and sites for that time incomplete. After 10 minutes to 2 hours without input, with the Mac awake and not locked, Hina may ask once when you return whether that was a meeting, reading or thinking, watching a video, or away. An unanswered question counts as away.
If a block looks wrong, first check whether Hina was paused, not running or the Mac was asleep, because nothing is recorded then and the length of an AI session cannot replace it. Then check which day it belongs to. A day runs from 4 a.m. to 4 a.m., so activity at 1 a.m. sits on the previous day.
Leave a next step you can pick up
When you finish, write the part you have not verified in your own notes, for example that the export was changed and tomorrow's check is the format with a real file. Hina has no notes field and does not decide whether a task is finished.
Writing, discussion and thinking leave no commits, and that does not make them worth less. They show up on the Trail as time, so when you can match them to something, put that in your notes too.