{"slug": "shared-chat-page-refreshes-on-load-which-strips-out-url-fragment-identifiers", "title": "Shared chat page refreshes on load, which strips out URL fragment identifiers", "summary": "A Kagi Assistant user reported that public share links at assistant.kagi.com reload or redirect on load without preserving URL fragments, breaking text fragment identifiers that would jump readers to a specific part of a shared LLM transcript. The user noted the fragment works only on a second load, once the page is already rendered, and linked the bug to a related Kagi feedback request for unique id attributes on individual chat messages, which would also be stripped on page load. The report asks Kagi to preserve fragments so shared transcripts can be linked to specific passages.", "body_md": "I have a bug to report in Kagi Assistant, which make it very difficult to usefully share LLM transcripts.\n\nWhen using the public share link, the page seems to reload or redirect itself on load, but it doesn't preserve any URL fragments when doing so (e.g. [https://assistant.kagi.com/share/f70a3701-edc3-49f4-8cbb-2ef65c497488#:~:text=The%20differences%20run%20deeper%20than,feedback%20loops%2C%20employer%2Dled%20delivery%29%2E](https://assistant.kagi.com/share/f70a3701-edc3-49f4-8cbb-2ef65c497488#:~:text=The%20differences%20run%20deeper%20than,feedback%20loops%2C%20employer%2Dled%20delivery%29%2E)). This means that it's not possible to use [text fragment identifiers](https://developer.mozilla.org/en-US/docs/Web/URI/Reference/Fragment/Text_fragments) to jump the user to a specific part of the transcript (see attached video for a demonstration — it works the second time because the text fragment applies to the already-loaded page).\n\n[This issue](https://kagifeedback.org/d/8979-allow-links-to-individual-messages-in-ai-chat/3) is related, as it asks for unique `id` attributes for the different chat messages to allow them to be identified with element fragments. My use case requires the more specific *text* fragments, but I think resolving this issue would also unblock a solution there (because currently, even if the elements did all have unique `id` s, they would also be stripped on page load).\n\n[This issue](https://kagifeedback.org/d/4029-research-assistant-references-are-difficult-to-check-implement-text-fragments) also talks about text fragments, but is not related—it is asking for the *agent* to use them when referencing other sources (which, as far as I can tell, is currently the case but [with limitations](https://kagifeedback.org/d/4029-research-assistant-references-are-difficult-to-check-implement-text-fragments/)", "url": "https://wpnews.pro/news/shared-chat-page-refreshes-on-load-which-strips-out-url-fragment-identifiers", "canonical_source": "https://kagifeedback.org/d/11870-shared-chat-page-refreshes-on-load-which-strips-out-url-fragment-identifiers/1", "published_at": "2026-11-11 09:34:22+00:00", "updated_at": "2026-11-11 09:50:05.958490+00:00", "lang": "en", "topics": ["ai-products", "ai-tools", "large-language-models", "generative-ai"], "entities": ["Kagi", "Kagi Assistant", "assistant.kagi.com", "kagifeedback.org"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/shared-chat-page-refreshes-on-load-which-strips-out-url-fragment-identifiers", "markdown": "https://wpnews.pro/news/shared-chat-page-refreshes-on-load-which-strips-out-url-fragment-identifiers.md", "text": "https://wpnews.pro/news/shared-chat-page-refreshes-on-load-which-strips-out-url-fragment-identifiers.txt", "jsonld": "https://wpnews.pro/news/shared-chat-page-refreshes-on-load-which-strips-out-url-fragment-identifiers.jsonld"}}