Tasks, dates, and attention
Keep future work out of the way without losing sight of what is due.
Read as MarkdownCapture and edit
Press N to create a task where task creation is available. Click a task title or select a task and press Enter to read its details. Notes and agent annotations render Markdown. Tasks without annotations show no annotation section. Select Edit task, the pencil, or press E from the task list to edit it. Tasks can have notes, a due date, a priority, and a local attention date.
Press Space to complete or reopen the selected task. For connected tasks, supported changes sync to their original source.
Capture a link
Paste a web URL as the entire task title in Inbox. The app saves the task immediately and looks up its title in the background after it reaches the server. It keeps the original link, the cleaned destination, and your existing notes. A title that you write yourself stays unchanged.
Local tasks and supported tasks with writable connections receive this lookup. Tasks from one-way connections and source-managed items stay unchanged. Public X posts use FixTweet to retrieve the title or post text. The app sends no task notes, credentials, or browser cookies with these requests.
If a lookup fails, the app retries twice before it uses a readable title from the URL. Pages that require a login or browser challenge use this fallback.
See who created and changed a task
Select Task history in the task view to show its origin and latest change. Annotations and history load while online. Notes and local task controls remain available offline. The first sentence says how the task was created: by you, through a connected app, or imported from a connected service. Tasks created before this was recorded show their creation date and Origin not recorded.
A second sentence names the latest change after creation, such as an edit, completion, reopening, or move. Only that latest change appears. The details do not list every earlier change. Changes from a connected service or automatic completion never name you as the person who acted. Actor not recorded means the change was saved without a known actor.
A connected app’s name is the client name it registered, not a verified brand. An agent name marked (self-reported) is supplied by the agent and is not checked. See Task attribution in the MCP guide for the full rules.
Know when changes have synced
Pending sync appears beside a task while a creation or supported edit waits to reach its external source. Your change is saved in Plan Your Work during this time. Busy connections and API limits can delay delivery. The label clears automatically when the source confirms the latest change.
Sync needs attention means a sync attempt failed or the connection can no longer send changes. Select the label to open connection settings for details. The label clears after a successful retry.
Local-only tasks and fields do not show a pending label. For example, changing a local priority does not wait for Godspeed to confirm it.
Ready, Later, All, and Overdue
| Filter | What it shows |
|---|---|
| Ready | Active tasks that need attention now. |
| Later | Future work that has not reached its attention date. |
| All | All active tasks, including future work. |
| Overdue | Active tasks with a due date before today. Available when there are overdue tasks. |
By default, a task becomes Ready seven days before its due date. Tasks without a due date are Ready unless they have a future attention date. Tasks due today and overdue tasks remain Ready.
Later orders tasks by due date and groups them like Upcoming. The filter keeps pagination, so long lists remain manageable. Selecting a filter does not change a due date or complete a task.
Set a local attention date
Set Show from in the task editor to decide when the task belongs in Ready. This is separate from the due date. For example, a monthly task can stay in Later until the week you plan to do it.
The MCP field for this date is show_on, in YYYY-MM-DD format.
Send null to restore automatic attention timing.
Calendar events also support this local setting.
Calendar events finish themselves
An imported event uses its start time as its due time. Its end time controls automatic completion. After the event ends, it leaves active views and appears in Completed after the completion job runs.
Timed events use your browser’s time zone for display. All-day events keep their calendar dates. The stored source times and time zones remain unchanged for sync.
Calendar events are read-only except for their local attention date. Edit, reschedule, or cancel an event in Google Calendar. The next sync imports those changes.
Auto-complete a local task
Set Auto-complete at in the task editor for a task that expires at a specific time. Leave it blank for a normal task that you complete yourself. The completion time cannot precede the due time.
Recurring tasks
Supported imports retain recurrence metadata and show a repeat indicator. Plan Your Work does not provide a recurrence editor through MCP. For Godspeed, complete repeating tasks in Godspeed to create the next occurrence.
Recurring Google events arrive as separate event occurrences. Each occurrence completes after its own end time.
Search and navigate
Press / to focus task search. Search includes task titles and notes. Use ↑ and ↓, or J and K, to select tasks. Press Esc to return to the sidebar.
See Keyboard shortcuts for the full everyday workflow.