Omniscio

Team Chat search dates — on:, during:, before: and after: in your own time zone

Type a date operator into the Team Chat search box, next to the words you are looking for. on: picks one day, during: picks a whole calendar period, and before: / after: cut at the edge of a day. Everything is read in the time zone your computer is set to, and a "day" is the real local day — 23 hours on the day the clocks go forward, 25 on the day they go back — never "midnight plus 24 hours". The line under the search box names the dates your search is actually limited to, so you can see it before you trust the results.

On this page

The four date operators

  • on:2026-11-15 — messages sent that day where you are.
  • during:2026-11 — the whole of November 2026. during:2026 is the whole year.
  • during:today, during:yesterday, during:week (the calendar week you are in), during:month (the calendar month you are in). These are calendar periods, not rolling windows: week starts on the first day of your week — Monday unless your language's week starts on Sunday — so during:week always covers whole days, never "the last seven days".
  • before:2026-11-15 — everything before that day began. after:2026-11-15 — everything from the moment the next day began, so the 15th itself is included only by on:.
  • on:today and on:yesterday also work when you want a single day without typing it.

A full timestamp still means an exact moment: before:2026-11-15T12:00:00Z cuts at noon UTC.

What "a day" means here

Your computer's time zone decides where a day starts. Two results follow from that, and both are deliberate:

  • The clock changes are handled. A local day is the interval between the start of that day and the start of the next one. On the spring-forward day that is 23 hours; on the fall-back day it is
    1. A search never computes "midnight plus 24 hours", so a message sent late on a clock-change day can never fall into the wrong day.
  • Nothing is rounded to UTC midnight. A message at 8pm your time belongs to your day, not to whatever day UTC is on.
  • A day starts at its real first moment. A few regions move their clocks at midnight rather than at 2am, so that day has no 00:00 at all; the search still begins at the first moment the day actually exists rather than an hour early.

The search is sent to the server as exact moments; the server never needs to know your time zone.

Combining dates

You can combine operators and the date filters in the Filters bar. They intersect — the search covers only what all of them allow. For example during:2026-11 on:2026-11-15 covers just that day inside that month, and picking a From date narrows a typed during: further.

The line under the search box reads the result back to you in your own zone, for example Dates: Nov 1 – Nov 30, 2026 or Dates: Nov 15, 2026.

When a date cannot be used

  • A value that is not a real date — on:2026-02-31, during:2026-13, before:last week — is reported under the box as ignored, and the search runs without that bound. It is never quietly rolled forward to another date, and it never empties your results.
  • A range with no days in it — for example after:2026-11-20 before:2026-11-20, or a From date later than the To date — is reported as empty and nothing is sent, rather than showing "no results" for a question that could never match.

Behind it

One shared resolver owns the rule: src/shared/team-chat/search-date-range.ts turns a date operator or a date pill into a start moment (inclusive) and an end moment (exclusive) in the frozen zone. src/shared/team-chat/search-operators.ts parses the operators and hands them over, and src/renderer/src/features/team-chat/TeamChatSearchDialog.tsx freezes one time zone and one "now" per search, intersects the bounds and displays the range. Because the end of a range is exclusive, the search service must compare it with "less than"; that server-side change belongs to the next slice of this work.

Last verified 2026-11-20