Philip Meier

> I have never seen the Welcome Modal in the UI. Same. And I thought this happened, because we never got around to implement it. Thanks for reporting that we...

So if there are no chats open, we have static text where usually the chat interface is?

> Add a comparison workflow / app We need to clarify what we want here. Since we have a fully featured Python API, the "workflow" part is already covered. However,...

Bumping impact to medium. For the `0.2.0` release, we are going to add an example to the documentation to describe the comparison workflow together with the Python API. Although still...

On second thought, maybe this is actually a good thing? Like, if users don't configure anything they are still hit by the authentication screen. Being able to just click "Login"...

On third thought, I agree with my initial statement. As proposed in #179, the dummy authentication should not be the default and thus it is ok to require a username...

I don't really understand what the issue is with the current approach. `GET /chats` will give you all of the chats of the user. https://github.com/Quansight/ragna/blob/c1c159d196db99cb0372cddd4abf8ecee3ce255d/ragna/deploy/_api/core.py#L203-L206 If you know the ID...

> Ultimately, it's a QoL feature request. It's possible to get the behaviour I want with a GET to `/chats`, but it's not very user-friendly and has possible performance implications...

Here is how we are currently doing it in our UI: 1. When starting the UI, we hit `GET /chats`, store its result, and populate the left sidebar, i.e. the...

> My experience so far is that this is negligible compared to the time taken to actually rebuild and display the chat messages when switching between chats (which also affects...