Originally created by @atassis on GitHub (Aug 8, 2024).
Is your feature request related to a problem? Please describe.
Right now the response is sent to the client and the client then stores the chat with a separate api call /api/chat/completed. When client has any issues with stability of the network- it makes it difficult to use an app, there is no history saved after restarting the page.
Describe the solution you'd like
I suggest implementing the save of the chat via backend, so it would store all data server side after receiving the response from LLM (ollama)
Originally created by @atassis on GitHub (Aug 8, 2024).
**Is your feature request related to a problem? Please describe.**
Right now the response is sent to the client and the client then stores the chat with a separate api call `/api/chat/completed`. When client has any issues with stability of the network- it makes it difficult to use an app, there is no history saved after restarting the page.
**Describe the solution you'd like**
I suggest implementing the save of the chat via backend, so it would store all data server side after receiving the response from LLM (ollama)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @atassis on GitHub (Aug 8, 2024).
Is your feature request related to a problem? Please describe.
Right now the response is sent to the client and the client then stores the chat with a separate api call
/api/chat/completed. When client has any issues with stability of the network- it makes it difficult to use an app, there is no history saved after restarting the page.Describe the solution you'd like
I suggest implementing the save of the chat via backend, so it would store all data server side after receiving the response from LLM (ollama)