Skip to content

td task list --json returns 0 results when filters applied (plaintext returns expected count) #370

Description

@RikkeTL

Bug Description

td task list with filters (--workspace, --assignee, --due) returns 0 results when --json is passed, even though the same command without --json returns the expected tasks.

Steps to Reproduce

td task list --json
# returned 0 results

td task list --workspace Doist --assignee me --json
# returned 0 results

td task list --due today --json
# returned 0 results

Meanwhile, plaintext equivalents returned the expected tasks:

td task list
# returned ~285 tasks

td project view <projectId>
# showed 22 tasks in Inbox

Context

  • First reported: 29 April 2026
  • We haven't been able to confirm the exact version at the time — testing on v1.63.2 shows non-zero results for the above commands, so this may have been partially fixed. However, there's still a potential discrepancy: td task list --workspace Doist --assignee me --json returns 30 results while the plaintext equivalent returns ~93 lines of output.
  • Workaround in use: grepping plaintext output for date strings

Why This Matters

DoistOS agent skills rely on --json output for structured data processing. If the JSON path silently drops results that plaintext returns, agents get an incomplete view of tasks without any error signal. This is especially painful for skills that filter by assignee or due date.

Worth confirming whether this was fixed in a recent release, and if so, which version.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions