ClawManager uses a TaskWarrior-compatible filter syntax for its named filters and its inline search bar. A filter expression is a space-separated list of tokens, combined with AND logic. Filters can also carry an optional ordering expression that controls how matching tasks are sorted.

Where filters run

• Named filters — created and managed from the funnel icon in the topbar. Each filter has a name, an expression, an optional ordering, a favourite flag (shows it as a chip in the filter row), and a readonly flag (used for the built-in “My Tasks”).
• Inline search — the search input in the topbar auto-detects whether its contents are filter syntax. If a token starts with +, -, or matches a known keyword:value pattern, the whole input is parsed as a filter. Otherwise it falls back to a case-insensitive description substring search.
• Built-in filters — seeded once on first launch:
  • My Tasks — status:pending, ordered priority-,due+, readonly.
  • Today — status:pending due.before:today, ordered priority-,due+. Pending tasks due today or earlier (i.e. due today + overdue).
  • This Week — status:pending due.before:eow, ordered priority-,due+. Pending tasks due on or before the end of the current week (Sunday).
  • Completed — status:completed, ordered modified-.

Filter syntax

Tokens are space-separated and combined with AND. Unknown tokens are ignored.

Tag tokens

Tags are case-sensitive. If the tag name is all-uppercase and matches a known virtual tag (see below), it is resolved as a virtual tag rather than a literal tag.

Field tokens

Notes:

• description:<text> is literal equality against the whole description. For the common “search by substring” case, use description.contains: or plain text in the inline search bar.
• There is no wildcard syntax. To match “has any project”, use the virtual tag +PROJECT; to match “has any priority”, use +PRIORITY; and so on.

Due-date tokens

The due:, due.before:, and due.after: keys accept either an ISO date or one of a few keywords.

Notes:

• due: for a specific day compares on the task’s calendar day in the local time zone, not the exact timestamp. Two tasks due at different times on the same day both match due:today.
• due:eow and due:eom are treated as before end-of-week and end-of-month respectively, rather than as exact-day matches.
• Invalid dates (e.g. 2026-02-31) and unrecognized keywords cause the token to match nothing rather than being ignored.
• Tasks with no due date never match any due: / due.before: / due.after: token.

Virtual tags

Virtual tags are uppercase tag names that are computed from a task’s properties rather than stored on the task. They are written with the same +TAG / -TAG syntax as regular tags. Virtual-tag detection is an exact-match check against the uppercase name, so +ACTIVE is a virtual tag and +active is a regular user tag.

Status-based

Field presence

Activity and state

Parent / child

Due-date relative

All due-date virtual tags evaluate against the task’s due date in the local time zone. Tasks with no due date never match.

Dependencies

Other

Combining filters and virtual tags

Virtual tags compose with any other tokens via AND:

+PENDING +urgent project:work due.before:eow

+OVERDUE -someday priority:H

+READY +PROJECT

Sort ordering

Each named filter can carry an ordering expression. The ordering is a comma-separated list of sort keys; each key is a field name optionally suffixed with + (ascending, the default) or - (descending). The leftmost key is the primary sort; later keys break ties.

Syntax

A token with no suffix is treated as ascending. Empty tokens and tokens with an empty field name are skipped.

Supported fields

Known fields use type-aware comparison:

Any other field name falls back to task.getValue(field), which makes custom attributes (UDAs) and any other TaskChampion key sortable. Numeric values use numeric comparison; everything else is compared as a case-insensitive string.

Null handling

Null and empty values always sort last, regardless of ascending or descending direction. This means due+ puts tasks with no due date after all dated tasks, and due- also puts them last rather than promoting them to the top.

No ordering

If a filter’s ordering expression is empty or omitted, the matching tasks are returned in their underlying working-set order — no explicit sort is applied.

Examples