Search runs in your database — the separate search service is gone
Full-text search is now entirely Postgres: the standalone search service and Meilisearch have been removed, so there is one less moving part, no public search endpoint, and results come straight from the same database that holds your records. This is a major release because the old workspace-wide search API in the SDK and MCP server is removed.
- Records you write are searchable the moment the write commits — there is no separate index to catch up.
- The standalone search service and its Meilisearch index are gone. Full-text search continues through the records query's `text` clause and `records.search()`, served by Postgres full-text search.
- SDK: `client.search()` and its `{ hits, totalHits }` response are removed. Use `client.records.search(collection, text)` or `client.records.query({ text })`, which return the standard `{ data, meta }` envelope.
- MCP: the `search_records` and `describe_search` tools are removed; search a collection's records with the records query tools instead.
- Typo-tolerant (fuzzy) matching is no longer offered; matching is exact-prefix on the last word and results are ranked by relevance unless you sort explicitly.