create recurring task with cli, first click in web UI doesn't complete, second click does

[banshee]

Create a task with the cli:

td task add --content "Buy milk" --due "every year, starting 1/1/2026"

That creates what I want: a task that's due now, and in theory when it's completed will be due again on 1/1/2027.

What's odd is that if you complete that task by clicking the bubble or hitting E, it gives you the popup saying the task has been completed:

But the actual date on the task doesn't change - it remains 1/1/2026. Completing it again then moves the date to 1/1/2027 as expected.

❯ td -V
1.76.0

[scottlovegrove]

Thanks for the clear report — this turned out to be a server-side bug rather than anything in the CLI, and the reproduction steps made it straightforward to track down.

When you pass --due, the CLI sends the string through to POST /api/v1/tasks as due_string and the API resolves it. That endpoint was storing the string verbatim, so your task ended up with due.string = "every year, starting 1/1/2026" rather than the date 2026-01-01 plus the rule every year. Because the explicit start date stays in the string, every subsequent re-parse is pinned back to it — so "advance to the next occurrence" resolves to the date the task already has, which is why the first completion looked like it did nothing. The completion itself rewrites the string into its normalised form, which is why the second click then behaved.

Todoist's other entry points that accept raw date text (quick add, CSV import, calendar sync) all normalise the string on the way in; the REST API was the one that didn't. Fix is up internally as Doist/Todoist#29249 — I'll update here once it's deployed.

In the meantime td task quickadd goes through the normalising path, so this works correctly today:

td task quickadd "Buy milk every year, starting 1/1/2026"

You can tell the two apart with td task view <id> --json | jq .due — the quickadd version comes back with "string": "every year", the task add version still has the starting ... clause in it.

One thing worth flagging for when the fix lands: due.string will come back normalised, so td task add --due tomorrow will print the resolved date rather than echoing tomorrow. Same value, different text.

[scottlovegrove]

This required a change on our API, so there are no updates required for the CLI. The fix is deploying at the moment, so give it an hour or so and try again.