isFocusedToday query param for GET /v1/tasks

[gursuj]

The Cloud API's GET /v1/tasks accepts status, query, all, and deleted as query params, but there's no way to filter by isFocusedToday. The field exists on the task model and serializes through the API, but filtering for today's focused tasks requires fetching the full task list and filtering client-side — expensive once the task list grows past a few hundred items.

This is especially relevant for AI agent / MCP workflows where a common query is "what am I focused on today?" — currently that's an N+1 client-filter pattern against every task in the namespace.

Request: support ?isFocusedToday=true on GET /v1/tasks, consistent with how status and all are handled.

[dongdongbh]

Done, in 455b4d9.

GET /v1/tasks?isFocusedToday=true returns only starred tasks, false returns only the rest, and leaving the parameter off filters nothing. Both true/1 and false/0 work — all and deleted already use the 1 spelling, so it seemed wrong to accept only one. Anything else is a 400 rather than a quiet fallback to false, which would return the whole list and read as "nothing is focused".

Two things beyond what you asked for.

The MCP tool needed this more than the REST endpoint did. mindwtr_list_tasks couldn't express the filter either, on either backend, so the workflow you actually described would still have gone through a full fetch after the query param landed. It now takes the same isFocusedToday option, and both adapters filter on it — SQLite in the query, cloud in the JSON pass. The desktop Local API's /tasks accepts it too, so all three read surfaces agree.

One correction on the cost, since it affects how much this buys you: it isn't an N+1. It's a single request plus a client-side filter, and the server deserializes the whole namespace on its side either way. What you save is transfer size and client CPU, not server work. Worth having, just less dramatic than the framing suggested.

One thing to know before you build on it: isFocusedToday is sticky. It stays set until the task is unstarred or completed — there's no midnight reset — so the filter mirrors the Focus view exactly rather than meaning "starred on today's date". That's almost certainly what you want for "what am I focused on today?", but it does mean a star left over from Tuesday still counts on Thursday.

Docs updated for the Cloud API and MCP.

[gursuj]

Thanks! The sticky behavior is preferable