Two-way sync

Keep working in the task list you already use. Sync is opt-in and bolt-on: the local database stays authoritative, and the app is fully usable without it.

Offline first

Your tasks live in a local database on your machine, and that database is what the app reads and writes. Sync is a layer on top of it: when you connect an outside system, the app maps your tasks onto it and reconciles changes in both directions.

The practical consequence is that a sync that fails does not break the app. Nothing in the task loop requires a network call, so you keep working offline and the mapping catches up when it can.

Todoist

Todoist is the primary external task list, and it is the integration to reach for if you want two-way sync today. available

Connect your account from the app's integrations pane. Once connected, changes you make in Todoist arrive locally and changes you make locally are pushed back, with the local database remaining the copy the app trusts.

Each Todoist project maps onto a local project tag, and its sections become child tags beneath it, so the structure you built in Todoist survives the move. Todoist priorities map onto urgency — P1 lands as the most urgent, P4 as the least — and due dates become deadlines. If both sides changed the same task, the newer edit wins; a task deleted on one side disappears on the other rather than coming back.

GitHub

GitHub issues and projects are in preview. preview The same sync surface is there — authenticate in the integrations pane and your issues and projects map onto your lists — but expect the shape of that mapping to change while it settles.

GitHub also has a second, separate role: a coding workflow run can use a real checkout, which is what makes the diffs in Semi-automated workflows real.

What syncs

Titles, descriptions, and completion state are what flow today; the exact contract is written down rather than implied. If you need to know whether a specific field survives a round trip, the integration's spec is the answer — see Integrations.