Time session history
Tracked time is only useful if it is accurate, and timers are easy to forget. The Time Session History panel is where you look back at the sessions you recorded and fix the ones that went wrong: a timer left running overnight, a session on the wrong task, a block you meant to log but did not. It turns tracked time from a rough guess into a record you can trust.
MEDIA-DOCS-053-1: The Time Session History panel listing recent tracked sessions by day.

Open the history
Run Open Time Session History panel from the command palette. It lists your recent tracked sessions, grouped so you can see where your time went day by day. How far back it reaches is a setting, the history window, measured in days. A Tracked time filter in another view does not limit this panel; it keeps its own history window.
Open a task source
Task description click action, under Settings → Operon → Tasks → Tracker, chooses whether a task description opens Task Editor or its source. The companion button offers the other action: Open Source when the description opens the editor, or Open task editor when the description opens the source.
On desktop, both Source entry points open the shared lightbox for the current task. Inline source navigation uses the current task line and places the caret after the description in the editable Markdown view, with no text selected. To continue in a tab, use the preview's Open in new tab control. Opening Source does not edit the recorded session; mobile navigation is unchanged.
Edit a session
Each session is a time range you can correct. Open a session to adjust its start and end, so a forgotten stop or an off-by-an-hour block becomes right. Because tracked time rolls up into a task's duration and its totals, fixing a session here keeps every view that shows time honest. See Time tracking.
You can also edit a session directly from a table: click its chip in detailed Duration or Trackers. Click empty space in either cell to add time. This works in normal and embedded tables when editing is available. See Table cells: display and behavior.
MEDIA-DOCS-053-2: Editing a tracked session's start and end time to correct a forgotten stop.

The task description at the top of Edit session is a formatted, read-only context label. Default and six-color highlights appear in their display form, with the color marker hidden, just as on a Kanban card. This does not alter the source description or the session's times and save behavior. To change the description or its highlight color, use Task Editor; see Text field editor popover for highlight syntax.
Edit the latest session from Status Dock
On desktop, the visible Status Dock shows a temporary card for the latest newly saved task session. Click its duration, such as 34m 22s, to open the same Edit session window. The card lasts ten seconds, with its countdown paused while you hover over or interact with it. If a dock task list is open, the card waits until that list closes.
Clicking the card's task description follows the Status Dock opening preference, independently of the history panel's Task description click action setting. Once the card disappears, the saved session remains available in history and Task Editor.
Edit from Task Editor
In the desktop-style Task Editor, open Sessions and click or tap a session's duration, such as 35m 4s, or its pencil. Both open the same Edit session window for that recorded range. With a mouse, the duration is underlined on hover; it is also keyboard-accessible. On the desktop-style phone layout and on tablets, the controls are available without hovering.
The existing compact mobile editor keeps its own session presentation and pencil action. Choosing that phone layout does not change the stored sessions. Correcting a session updates the task's tracked time, regardless of which entry point opened it.
Use the desktop-style Sessions header's clock-plus button to Add session. Its dialog includes the task title and Start/End controls, so you can confirm the task before adding the range. Edit session uses the same compact Start/End arrangement. These controls keep the existing validation and save path; they do not edit the task description.
Log time you did not track
Sometimes the work happened but the timer did not. You can record a planned block as tracked time after the fact with the Log as tracked action in a task's contextual menu, so the history reflects what really happened even when you forgot to start a timer.
Where sessions come from
Sessions can come from a FlowTime focus session, a TrackTime stopwatch, a block logged as tracked, or a range added through Add session. They live on the task itself as tracked time ranges, which is why the history is a view of your tasks, not a separate log. See Time tracking.
FAQ
I left a timer running. Can I fix it? Yes. Open the session in the history and correct its end time.
How far back does the history show? As far as the history window setting allows, which you set in days.
Can I add time I forgot to track? Yes. Use Log as tracked on the task to record a block after the fact.
Settings
Operon settings for this live in Settings → Operon → Tasks → Tracker, which sets the history window in days and how sessions are split, alongside the rest of the time-tracking behavior.