Aleksandr Vishniakov

@DmitriyAlergant That sounds great, but: 1. We almost never have time to deliver multiple big features together (unless count them as one big feature) 2. The project changes frequently, and...

@samippl1 Yes, this is a frontend issue and it's a known one. As Chainlit is now a community-driven project, we would appreciate your help - or anyone else's - in...

@hayescode I would like to keep it open after #2349 to implement proper fix later

@samippl1 Workaround implemented in #2349, released in [2.6.5](https://github.com/Chainlit/chainlit/releases/tag/2.6.5)

@jbcallaghan These are just type annotations, they are ignored by Python at runtime. > Thread {thread_id} not found can only be caused by passing non-existing thread ID to get_thread_author Can...

Related to #2367 and #2357

@jbeckerdm Hi Jannis. I'm the other maintainer, and while React isn’t the primary framework of choice used by me or my company, I do have frontend experience and a background...

@aleks3fs Thank you for the explanation! I didn't see the deprecation message anywhere until I opened their repo. In that case, I think we don't have many options left, so...

@hayescode I'm working on that [here](https://github.com/Chainlit/chainlit/pull/2327) and in few other PRs, let's wait until you return at Wednesday, I think it should be ready

So actually, after careful review, here are my two biggest concerns: 1. After merging this PR, we’ll be using React 19 in `libs/react-client` and React 18 in the frontend itself....