---
title: "Tasks"
description: "Checkbox tasks parsed out of a Log, with due dates."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.loggo.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Tasks

1. **Write a checkbox**

   `- [ ] some task` in any Log becomes a real task record, tracked
   separately from the log's text.
2. **Add a due date, optionally**

   A trailing `!token` like `!tomorrow` or `!friday` sets when it's due.
3. **Tick it anywhere**

   The day board, the Tasks page — checking `- [x]` marks it done by
   rewriting that exact line in the log.

## Due dates

Add a `!` token at the end of the line to give a task a due date:

```md
- [ ] Ship the release notes !tomorrow
- [ ] Reply to the customer thread !today
- [ ] Renew the TLS cert !2026-09-12
- [ ] Follow up with the vendor !friday
```

`!today` and `!tomorrow` resolve relative to the log's own day (not necessarily today's real date, if you're writing into an older log). A weekday name resolves to the next occurrence of that weekday.

## The file is the source of truth

Ticking a checkbox anywhere in the app — the day board, the Tasks page — rewrites that exact line in the log's markdown body. There's no separate tasks table that can drift from what the log actually says; that's why every task tracks which line number it came from, and why editing a log's text underneath a task can make the tick briefly fail (see [`PATCH /tasks/:taskId`](/api/workspace-data#tasks)).

## The Tasks page

`/tasks` lists every task in the workspace, filterable by pending/completed and by date range.

Source: https://docs.loggo.dev/features/tasks/index.mdx