mirror of
https://github.com/windmill-labs/windmill.git
synced 2026-09-21 08:02:38 +00:00
A chat reopened while its flow is still running has to find the message that started the turn: it carries the flow job, which is the only thing that knows whether the run is over. An agent writes a row per round and per tool call, so that message sits an unbounded number of pages back in the transcript, and a client reading towards it is searching with no end it can name. `message_type` answers it in one request. The filter is applied inside the paginated subquery, so `page=1&per_page=1&message_type=user` really is the newest user row rather than the newest row that happens to be one. `MessageType` carries a fourth kind, `System`, that nothing writes and the Postgres enum has no label for. A request to filter on it is refused before the database, so what reaches the caller is a word about their request rather than an error about an enum. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Windmill API
The API server, exposing functionality to other components and the frontend
This crate exposes both a library as well as a binary target.