User's guide
Day
Day shows one date on a timeline: your meetings and the entries you wrote, in the order they happened, so you can see the whole day at a glance.
The timelineMeetings and entries share one column of hours
Your meetings show as filled blocks across the hours they took, in the colour of the life area their calendar maps to, and each entry from your Journal shows as a coloured dot with its first line beside it. You see a meeting and what you did during it in one place. Two things at the same hour draw side by side. Each block is drawn tall enough to read even when it took less time than that, so short entries a few minutes apart draw as one block over the time they cover, with the first one’s words and a count such as +5; opening it opens the first, with the rest listed to move to. A short block inside a long one draws inset on top of it, so a fifteen-minute interruption leaves an eight-hour block whole, as long as it starts below the long block’s first line; one that starts sooner draws beside it, so neither covers the other’s words. An all-day item has no hours to draw against, so the timeline leaves it off.
Scale at the top stretches or shrinks the hours, so a packed morning opens up and a whole day fits one screen. On a computer, holding ⌘ or Ctrl while you scroll the hours does the same. The browser and the phone both remember where you left it, so the next day you open is drawn at the scale you were reading at. The strip of days across the top changes the date. Tap any day to jump to it, or step a day with the arrows either side. Hold a day, or right-click it on a computer, and the whole month opens under the strip for a date further off. A line marks the current time while you are on today, and a Today button appears beside the strip once you leave it. Untimed entries collect under the hours at the end of the day, under a heading the app calls Notes, which is not the Notes tab, each saying how far from that day it was written, since an entry written while you were looking at some other date has no time of day.
Meetings come from your Google Calendar, connected at Settings → Account → Calendar: one button, Google's own permission page, done. The same place then lists the calendars that came back, so you tick the ones you want on your Day and name the life area each one falls under. Until it is connected, the day simply shows what you wrote yourself and nothing else.
Opening a markTap anything on the timeline to see it whole
Every block and dot on the timeline is a mark, and a tap opens it whole. Several entries in the same minute collapse into one mark with a count, and opening that mark lists the rest as well, under the one you opened; pick one and the dialog moves to it. A row prints its own time only when it differs from the one you opened.
An entry you wrote opens in Edit journal, the same dialog the Journal's menu opens, with everything you put in it, not the single line the timeline had room for. It reads the way a journal row reads: its life areas as chips and its time on one line, the words under them. A clock lands when you leave it or press Enter; the arrow keys move a focused one five minutes, or an hour with Shift. Moving the start moves the end with it. The end clock is always there. A time typed into an empty one turns a point into a time log, and emptying it takes the end away. An untimed entry opens at the clock it was written, and saving the clocks is how it gets a time. A tap on an area chip opens the menu that takes one off or adds another. The words are the note editor's field on the web, plain text with the dash and bracket shortcuts on the phone, and Task under them opens your open tasks. Delete removes it after a confirm, and for six seconds an Undo on the day can take it back. On the phone a mark of yours opens the same edit screen.
A meeting opens with where it is and the notes on its invitation, and a call has a Join the call link. Four words mark where you stand with it. Open task sits above all four. It opens the meeting's own task page, where its goal is set the way any task's is. A meeting that has a goal shows the goal's name on its block. Going confirms you plan to attend and leaves the meeting on the day. Done records that it happened by turning it into a time log with its real title and times, so the block becomes logged time. Cancel task takes the meeting off the day and cancels the task behind it, and Google is never called about it. Cancel & Decline does that and answers no on the invitation as well. Google emails nobody either way. What separates them is what the organizer can see: after Cancel task your invitation still reads as unanswered, and after Cancel & Decline your name reads Declined in their guest list. Cancel & Decline always asks first. On the sheet a meeting opens into, Cancel task is a plain press, and on the menu a block opens it asks too. Both leave six seconds in which Undo brings the meeting back before anything is written. For a meeting you called yourself there is no invitation of yours to answer, so Cancel & Decline only clears it here, and the task behind it still closes. Leaving the day or closing the tab sends the answer early. If the server refuses a decline then, nothing has moved: the app names the meeting, says it is still there, and gives the reason it was handed. It says so the moment you are looking at that screen again, or on the next load of that day when the screen has gone for good.
A row in the Changes column and a row in the System column open to be read. Both belong to the app's own record rather than your writing, so there is nothing on either to correct here. A Changes row does offer the way through to the task, goal, note or event it is about. Deleting that thing takes its rows off the Day with it. What you deleted leaves no trail here. Older rows, from before the app worked this way, stay without the way through.
Logging time by drawingDrag an empty stretch of the hours to log your time
Drag down an empty stretch of the hours and the Day draws a block across it. Let go and the Day asks what you were doing, and the answer saves as a time log. The box has the same clocks and area chips as the Edit journal dialog, so a block drawn to the quarter hour can be set to the minute and filed under its area before it is saved. Typing an end on a point makes it a time log. On a touchscreen, hold still for a moment and then drag, since the pause is how the app knows you mean to draw rather than to scroll. A press with no drag makes a point, an entry at that minute with no end. Where one column fills the screen, a draw on the Points column makes a point however far the finger travels, since that column holds points.
A block you draw starts on a quarter hour, or on the end of the entry just before it when that is nearer, so a new block meets the one before it instead of leaving a two-minute hole between them.
The four columnsEach kind of row has its own column
Every row beside the hours belongs to one of four columns.
- Points — the entries you wrote at a moment.
- Time logs — the blocks with a start and an end, your own logged time and your meetings.
- Changes — what changed, at the time it changed: a task, a goal, a note or an event being made or shelved, and the field edits underneath. Changes too close together to each have a row at their own minute share one row with a count, such as +11, and opening it lists them all.
- System — the rows a machine left: a device reporting something, and anything the agent or the app wrote on its own. The morning sleep reading and the log of a completed meeting are machine-written too, but they are about your day, so they appear among your own marks instead.
A phone, and a browser window narrowed to about a phone's width, show one column at a time, with these four names as tabs across the top and a sideways swipe between them. A wide window shows all four side by side in the same order and drops the tabs, so you tell the columns apart there by what is in them.
The one column on screen still shows the marks the others hold. While you read Time logs, each moment written that day shows as a dot beside the hours; while you read Points, each time log shows as a short line at its own extent. Both take the colour of the entry's life area, grey when it has none, and both open the entry they stand for. A wide window has all four columns already, so it draws neither.
A finished thing shows as its own record rather than as a mark on something else. A meeting you finished is the time log it became, at the hours it took; a task you closed is its row in Changes, at the minute it closed. The timeline has those two layers and no third, so no tick, badge or dot anywhere on it says that something is done.
A Changes row says who made the change when it was not you. Your own edits are unmarked. A change made by something else shows a word in front of it: the client’s own name, such as Claude Code or ChatGPT, for a conversation connected through the connector, or Connector for one that gave no name; Assistant for the chat inside the app; Automatic for a background job; API for a program that used your account’s own token without saying which app it was; Agent for an agent account that works for you. Opening the row names the job, or the connection, whose calls are listed under Settings › Apps › MCP. Rows recorded before the app started keeping this show nothing, so an unmarked row from that time is not a claim that you made it. Unattributed means the record names nobody at all, which is worth seeing.