Zachary

**Problem Statement** 1. Based on a previous PR #9, we have managed to introduce the concept of `thread` runs, where we await for a response based on the content of...

**Description** For each thread, there should be an associated assistant that the user can create. The user should be able to see all assistant information and change the behaviour of...

**Description** Following a common chat application pattern, this issue should have the [basic features](https://chat.vercel.ai/) of a chat interface for any generative ai application. - Design a responsive chat window that...

**Description** On the far left column of the layout, there's some mock data existing for the thread titles. However no styling as been applied to it yet, and we should...

**Description** Show a loading indicator (could be a skeleton) while messages are being fetched or sent to improve user experience. **Tasks** 1. Add a loading spinner or indicator when messages...

**Description** We should be able to stop streams of messages from coming in if the user chooses to do so. **Tasks** 1. Implement an Abort Controller to terminate the connection...

**Description:** Enable users to send messages using the input area. When the send button is clicked, the message should appear in the thread window. Please refer to our backend endpoint...

**Description** Messages should be displayed in the thread window with proper styling. Each message should show: - The sender's name, in this case the assistant name - The message text....

**Description** Create a basic layout for the thread interface. This should include: - A header section with the thread title. - A main chat window for displaying messages which is...