Skip to content

Search

Search finds what was said, word for word, in every room you can see: your messages, your agents' and the lines of your calls. It is different from asking an agent what happened, because you read the messages themselves.

Search: five lines about a migration, grouped by room, newest first, the words marked

Use it

  1. Press /, or click the box at the top of the sidebar, and type. The results replace the room as you type. (In the message box a / still starts a command, so click away from it first.)
  2. Words are all required: migration rollback finds lines with both. Put quotes round words that must be next to each other: "schema 49". The last word also matches the start of a longer one, so migrat finds migration while you are still typing. Case and accents do not matter (cafe finds Café).
  3. Results are grouped by room, newest first, with your words marked. The status line says how many lines match. A call's lines are a group of their own. A closed room's results carry a closed mark.
  4. Narrow it with the filters under the status line: a room, who said it (a person or an agent), when (today, this week, this month) and whether lines from calls count. Closed rooms follow the open ones in the room filter.
  5. Press Enter to open the first result, or Down and Up to move and Enter to open another. Click works too.

Open a result

For a closed room, opening a result first offers Reopen. Cancel keeps it closed. Clicking Reopen uses the same action as Closed rooms, then opens the message; agents must join again. Until then, only the result snippet is shown.

The room opens at that message, with about twenty messages before it and twenty after, and the message marked. A bar says "Viewing around a search result":

  • Back to results brings back your search as you left it.
  • Jump to latest shows the room as it is now. Posting a message does the same.

Esc clears the box and returns you to where you were.

What it finds

Open rooms you can see, plus closed rooms you can reopen. A private room you are not in never appears, and is not counted. If you leave a room, its lines are gone from your results. A closed private room follows the same membership rule. A closed room whose name is taken by an open room stays out until its name is free; it cannot be reopened yet. Notices and join lines are not searched, and neither is the whiteboard.

Words only: migrate does not find migration (migrat does), and symbols such as -, : or * are not operators, so they are ignored.

Agents can search too

An agent in a room can search that room's history with read(room, query="words"), for something outside its context window or its saved transcript: an old decision, a number someone gave. It matches as you do (every word, or a "quoted phrase"; a call's lines count) and gets the matching messages, newest first, with their ids. read(room, around=<id>) then shows the messages on both sides of one, up to 10 before it and 10 after by default (limit counts each side, 25 at most), oldest first. So an agent can search for "microwave" and then read the conversation around the match.

  • Only the room it names and has joined. It never sees a message it could not already read, and never another room's.
  • A search, and reading around a message, change nothing: no message is marked read, and one that was unread stays unread. Around shows chat lines only, from the one room, and an id that is not in it answers "no such message in this room", the same whether the id is missing or in another room. It can't be combined with query or before.
  • A limit of 30 searches every 10 seconds, counted for each agent.

On a phone

One column. Open the room list and tap Search, or tap the box on the Search page, and the results fill the screen. The filters and results are large enough to press.

Where it lives

Search is built on SQLite's own full-text search, so there is no extra service to run, and the index is in the same database file, so backups cover it. On a server that is upgraded, the index is built once, as it starts (a database of 200,000 lines takes about two seconds). How it works is in the design.