API_ERROR on all commands — authentication and task commands fail despite HTTP 200 responses

[adamschmideg]

Environment

• td version: 1.72.1
• Node.js: v26.3.0
• OS: Linux (Ubuntu)

Steps to reproduce

1. Install @doist/todoist-cli globally
2. Run td auth token <api-token>
3. Run any command: td today, td inbox, td auth status

Expected

Commands authenticate and display results.

Actual

All commands return Error: API_ERROR immediately.

Diagnosis

The Todoist API itself responds correctly — curl with the same token returns HTTP 200 with valid JSON. Verbose CLI output confirms the API calls succeed before the error:

[td:info] fetch GET /api/v1/tasks/filter => 200 | duration_ms=400
Error: API_ERROR
terminated

The error occurs during response processing, not during the HTTP request. td auth token <token> also silently fails to save credentials — td doctor shows "No Todoist credentials found" and "Config file not created yet" after running it.

td doctor output:

WARN Config file is readable but contains unrecognized key "token"
WARN No Todoist credentials found. Set TODOIST_API_TOKEN or run td auth login

Workaround attempted

Setting TODOIST_API_TOKEN environment variable produces the same API_ERROR result.

[gnapse]

I've traced this to the SDK's Undici usage rather than the CLI command logic itself. The failures happen with Node 26 only, and fresh installs that resolve undici@7.27.1; pinning Undici back to 7.24.8 makes the issue go away.

I’m not fully sure yet what changed upstream to make this start happening suddenly. It looks related to Undici's decompression/proxy dispatcher path, but I wasn't able to narrow it down to a specific Undici commit or release note.

My proposed fix is to first pin Undici in the Todoist TypeScript SDK, publish a patched SDK release, and then bump the SDK version used by todoist-cli. That should make fresh CLI installs stable again while we decide whether to report a focused repro upstream to Undici.

I have not done these changes yet, waiting to see what others here think, given the uncertainty about how this started. That is the main thing giving me second thoughts.

[scottlovegrove]

My proposed fix is to first pin Undici in the Todoist TypeScript SDK, publish a patched SDK release, and then bump the SDK version used by todoist-cli. That should make fresh CLI installs stable again while we decide whether to report a focused repro upstream to Undici.

Makes sense to do this first, at least gives us breathing room to see what a proper fix looks like for Node 26.

[bhean]

Not sure if it's the same issue, but looks very similar...
I'm having these errors (API_ERROR) since a couple of days as well from the cli.
It was always working perfectly, but since a couple of days ago, suddenly started to get these errors and I can't use the cli anymore.

• td version: 1.73.0
• Installed using brew
• OS: MacOS (26.5.1)

When I try login, the web say "You're connected. Todoist CLI is now authenticated" but the cli shows errors and it doesn't work:

$ td auth login
Open this URL in your browser:
  https://todoist.com/oauth/authorize?response_type=xxxxxxxxxx
✖ Checking authentication...
Error: API_ERROR
terminated

$ td doctor
✖ Checking authentication...
PASS Config file is readable (/Users/bhean/.config/todoist-cli/config.json)
PASS 1 stored account (xxxxx@xxxxx.com)
FAIL Stored credentials failed validation: terminated
PASS CLI is up to date on stable (v1.73.0)
Doctor summary: 3 passed, 1 failed

[scottlovegrove]

@bhean can you do node --version and just confirm that you have node 26 as well. The quick workaround right now is to downgrade node to 24.

[doist-release-bot]

🎉 This issue has been resolved in version 1.73.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[gnapse]

@adamschmideg @bhean can you folks confirm if your issues are resolved when updating to v1.73.1?

[bhean]

Sorry, I forgot to add Node version to my post (but yes, it's v26)
Anyway, THANKS for the fast reply and the ultra-fast fix... I'm sure it's working with this new version, but I haven't been able to verify it yet because brew is not yet updated (last version available is still 1.73.0)

[scottlovegrove]

because brew is not yet updated

This is automatic on Homebrew's side of things and they usually pull in changes a day or so later (to allow breathing room for if anything went wrong with a package).

[bhean]

Updated! And I can confirm that the issue is fixed!
It's great to see someone opening an issue, and a few days later you launched a fixed release 👍🏽 THANKS!