[Enhancement]: Improve URL handling for chat configurations #7008
Closed
mawburn
started this conversation in
Feature Requests & Suggestions
Replies: 1 comment 2 replies
-
This is a request from people within my company and I can pretty much take this on immediately. If I need to expand on the idea, let me know. Considerations need to be made to the chat id once a chat starts, which I think should replace the url params that get live loaded. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What features would you like to see added?
Dynamic URL updating that reflects the current chat configuration as users make selections. The chat interface should update the URL using replaceState to include all supported parameters documented in the URL query documentation (excluding the prompt parameter).
When a user selects a specific endpoint and model, the URL should automatically update to reflect these choices.
For example, if the user chooses
ollama
andllama3:latest
changing from a basic URL/c/new
to one that includes the selected configuration/c/new?endpoint=ollama&model=llama3%3Alatest
.More details
This feature would enable users to share specific chat configurations by simply copying the URL from their browser. When another user opens this URL, it would create a new agent chat with the same configuration parameters.
The URL would update in real-time as users select different options such as models, providers, and other parameters. All relevant configuration details would be encoded in the URL parameters according to standard URL encoding practices.
The prompt parameter should be explicitly excluded from this URL updating mechanism as it would make URLs unnecessarily long and isn't needed for sharing configuration settings.
This enhancement would make the chat interface more user-friendly by improving shareability and allowing users to bookmark specific configurations for future use. It aligns with the existing URL query parameter support but makes it more accessible by automatically generating these URLs based on user selections.
Which components are impacted by your request?
UI
Pictures
No response
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions