Better default journal queries in Logseq for Task management

Logseq task management becomes dramatically easier when default journal queries are replaced with a smaller set of purpose-built “task surfacing” queries—especially ones that automatically appear under the daily journal and disappear when there’s nothing relevant. The payoff is a short, skimmable list that shows what to do next in the morning, without the daily busywork of checking yesterday, copying unfinished items, or wading through fluff.

The core problem starts with two common setups: a daily task list that requires jumping back to the previous day to recover unfinished work, and a task list page that’s easy to build but too noisy—useful items mixed with unnecessary clutter. The solution is to design queries that condense tasks down to their essentials and then use Logseq’s “default queries” area so the right blocks pop up automatically beneath the daily journal.

A first priority is a dedicated “scheduled tasks” block that surfaces items due today (or earlier) at the top of the day. Instead of relying on the built-in scheduled/deadline line—which can be extensive and often shows the “important first” items at the end of the day—the workflow creates a separate scheduled tasks page. Tasks meant to recur daily are added there, and an advanced query checks for tasks marked as scheduled and “to do,” then filters by date using a less-than-or-equal condition (today or before). A result transform then condenses the output into a clean list view so the user can click a task for details while keeping the overview minimal. The query also benefits from Logseq’s behavior where empty default-query results vanish, keeping the daily journal tidy.

Next comes a “Bento box” approach for mid-sized work. Bento tasks are tagged (via a “Bento” marker) and pulled into a single daily query that only includes a small, controlled number of items—typically two or three—so focus doesn’t collapse under too many priorities. The query uses reference/block-name logic to find tasks stacked with Bento, then applies a result transform that groups and sorts by the journal date. This design intentionally prevents Bento from becoming “projects”; projects can exist elsewhere, while Bento represents day-sized chunks.

Finally, the system adds “widgets,” which are small, actionable tasks marked with a hashtag W. Borrowing the spirit of David Allen’s workflow, widgets are meant to be doable quickly—often in the range of 5–10 (up to ~25) minutes—so they work as an afternoon-friendly fallback when motivation dips. Widgets can be long in count, but they’re low-friction because they’re already broken down into concrete actions (e.g., “send email to…” or “order from webstore”). A separate “context” layer uses location-style tags like @Studio to filter tasks by where they can be done. An advanced query on the @Studio page then lists open tasks (including subtasks) relevant to that context, letting the user enter a location and immediately see what’s ready.

Together, scheduled tasks (today’s must-dos), Bento (a few focused chunks), widgets (quick wins), and context pages (@Studio, etc.) form a daily system that reduces cognitive load in the morning and keeps the task list clean enough to skim. Planning and alignment across projects and priorities are deferred to a separate workflow, keeping this setup focused on “now.”