[GH-ISSUE #232] Sharable PHP/MySQL support for history #27521

New Issue

GiteaMirror · 2026-04-25T02:13:48-05:00

GiteaMirror commented

2026-04-25 02:13:48 -05:00

Originally created by @oliverbob on GitHub (Dec 15, 2023).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/232

Is your feature request related to a problem? Please describe.
I've noticed that the generated link (e.g., https://server.comt:3000/c/0eebe829-dc86-44a9-945c-00c2e80d1d22) is currently only accessible to users logged into the local machine that generated it. This limits its usefulness when shared, especially across different browsers or devices.

Describe the problem in more detail
Even on the same PC, users with ollama-webui chat history on Chrome cannot access individual history links on Firefox or other browsers. This restricts the flexibility of sharing and accessing chat histories.

Describe the solution you'd like
I propose enhancing ollama-webui to allow sharing links with anyone connected to the internet. One possible solution could involve saving chat histories to a database (e.g., PHP/MySQL) and extending the UI with an API (via Express) to reference these histories for each user. This would enable accessing chat history from different browsers and devices. Use cases would be a school personnel or office staff accessing the UI and exchanging ideas for research and development with a team.

Describe alternatives you've considered

Implementing a browser-independent local storage solution for chat histories. For instance, an API to extend such features accessible via https://server.comt:3000/user/0eebe829-dc86-44a9-945c-00c2e80d1d22 or https://server.comt:3000/user?=user1&fullchat_history=0eebe829-dc86-44a9-945c-00c2e80d1d22
Utilizing a cloud-based storage solution for chat histories.

TL;DR: While private AI chat services can be expensive for individual users, creating a shared server within an organization allows cost-effective utilization of high-performance GPUs like A100 or H100. This collaborative approach fosters teamwork, innovation, and broader access to AI capabilities without the financial burden of individual hardware investments.

Therefore, the following is a necessity for this repo to offer maximum benefits to users:

Additional context
To provide additional context, consider popular systems like OpenAI's ChatGPT. In such systems:

User sessions are associated with unique identifiers.
Chat histories are persistently stored, often in a database (e.g., MySQL or MongoDB).
An API, built with a framework like Express, is used to interact with the chat history database.
Timestamps are applied to messages for chronological ordering.
Tokenization may be used to represent chat history for compatibility with the underlying model.
Security measures, including authentication and authorization, ensure users can only access their own chat histories.

Hope this can provide a concise road map based on the community request for the full fledged, full stack ui.

Originally created by @oliverbob on GitHub (Dec 15, 2023). Original GitHub issue: https://github.com/open-webui/open-webui/issues/232 **Is your feature request related to a problem? Please describe.** I've noticed that the generated link (e.g., https://server.comt:3000/c/0eebe829-dc86-44a9-945c-00c2e80d1d22) is currently only accessible to users logged into the local machine that generated it. This limits its usefulness when shared, especially across different browsers or devices. **Describe the problem in more detail** Even on the same PC, users with ollama-webui chat history on Chrome cannot access individual history links on Firefox or other browsers. This restricts the flexibility of sharing and accessing chat histories. **Describe the solution you'd like** I propose enhancing ollama-webui to allow sharing links with anyone connected to the internet. One possible solution could involve saving chat histories to a database (e.g., PHP/MySQL) and extending the UI with an API (via Express) to reference these histories for each user. This would enable accessing chat history from different browsers and devices. Use cases would be a school personnel or office staff accessing the UI and exchanging ideas for research and development with a team. **Describe alternatives you've considered** - Implementing a browser-independent local storage solution for chat histories. For instance, an API to extend such features accessible via https://server.comt:3000/user/0eebe829-dc86-44a9-945c-00c2e80d1d22 or https://server.comt:3000/user?=user1&fullchat_history=0eebe829-dc86-44a9-945c-00c2e80d1d22 - Utilizing a cloud-based storage solution for chat histories. TL;DR: While private AI chat services can be expensive for individual users, creating a shared server within an organization allows cost-effective utilization of high-performance GPUs like A100 or H100. This collaborative approach fosters teamwork, innovation, and broader access to AI capabilities without the financial burden of individual hardware investments. Therefore, the following is a necessity for this repo to offer maximum benefits to users: **Additional context** To provide additional context, consider popular systems like OpenAI's ChatGPT. In such systems: - User sessions are associated with unique identifiers. - Chat histories are persistently stored, often in a database (e.g., MySQL or MongoDB). - An API, built with a framework like Express, is used to interact with the chat history database. - Timestamps are applied to messages for chronological ordering. - Tokenization may be used to represent chat history for compatibility with the underlying model. - Security measures, including authentication and authorization, ensure users can only access their own chat histories. Hope this can provide a concise road map based on the community request for the full fledged, full stack ui.

GiteaMirror closed this issue

2026-04-25 02:13:48 -05:00

GiteaMirror commented

2026-04-25 02:13:49 -05:00

@tjbck commented on GitHub (Dec 15, 2023):

Hi, Thanks for the suggestion. Chat share feature is being actively developed with #215. In addition, with #216 if you enable auth option it'll start saving the chat logs in the backend.

Also, It would free up a lot of my time to actually work on adding features if people here could help each other out and check both open and closed issues here before they create an issue, Thanks!

@tjbck commented on GitHub (Dec 15, 2023): Hi, Thanks for the suggestion. Chat share feature is being actively developed with #215. In addition, with #216 if you enable auth option it'll start saving the chat logs in the backend. Also, It would free up a lot of my time to actually work on adding features if people here could help each other out and check both open and closed issues here before they create an issue, Thanks!

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#27521