{"slug": "non-ascii-characters-in-q-are-not-decoded-when-assistant-is-opened-via-a-url-as", "title": "Non-ASCII characters in q= are not decoded when Assistant is opened via a URL template (umlaut stays as %C3%BC)", "summary": "Kagi Assistant fails to decode percent-encoded non-ASCII characters passed through the `q` URL parameter, so a query typed as `bügel` is submitted to the model as the literal string `b%C3%BCgel`. The bug, reported against Firefox 154.0.1 on MacOS 26.6.2, reproduces both via a custom browser search engine using the URL `https://kagi.com/assistant?profile=deepseek-v4-1-flash&internet=true&q=%s` and by opening `https://kagi.com/assistant?q=b%C3%BCgel` directly, while spaces are preserved correctly. Expected behavior is that the prompt box and submitted thread show `bügel`.", "body_md": "When Kagi Assistant is invoked through a URL with the `q` parameter, non-ASCII characters are passed through percent-encoded instead of being decoded. Typing `bügel` produces the literal text `b%C3%BCgel` in the submitted prompt:\n\nmeine brille mit plasikgestell ist am b%C3%BCgel über der Nase glatt gebrochen. Wie repariere ich das\n\nNote that spaces are preserved correctly, only the umlaut remains encoded.\n\n## Steps to reproduce\n\n1. Add a browser search engine in Firefox with the URL:\n\n```\nhttps://kagi.com/assistant?profile=deepseek-v4-1-flash&internet=true&q=%s\n```\n\n1. Use that search engine with a query containing a non-ASCII character, e.g. `bügel` .\n2. The Assistant opens with `b%C3%BCgel` as literal text in the prompt.\n\nAlso reproducible by opening the encoded URL directly:\n\n```\nhttps://kagi.com/assistant?q=b%C3%BCgel\n```\n\n## Expected behaviour\n\nThe prompt box / submitted thread shows `bügel`.\n\n## Actual behaviour\n\n`b%C3%BCgel` is submitted verbatim, both to the model and (as far as I can tell) in the visible prompt.\n\n## Environment\n\n- Firefox 154.0.1 on MacOS 26.6.2", "url": "https://wpnews.pro/news/non-ascii-characters-in-q-are-not-decoded-when-assistant-is-opened-via-a-url-as", "canonical_source": "https://kagifeedback.org/d/11501-non-ascii-characters-in-q-are-not-decoded-when-assistant-is-opened-via-a-url-template-umlaut-stays-as-c3bc/2", "published_at": "2026-09-16 19:54:37+00:00", "updated_at": "2026-09-16 20:26:47.336876+00:00", "lang": "en", "topics": ["ai-products", "ai-tools"], "entities": ["Kagi Assistant", "Kagi", "Firefox", "MacOS", "DeepSeek V4 1 Flash"], "alternates": {"html": "https://wpnews.pro/news/non-ascii-characters-in-q-are-not-decoded-when-assistant-is-opened-via-a-url-as", "markdown": "https://wpnews.pro/news/non-ascii-characters-in-q-are-not-decoded-when-assistant-is-opened-via-a-url-as.md", "text": "https://wpnews.pro/news/non-ascii-characters-in-q-are-not-decoded-when-assistant-is-opened-via-a-url-as.txt", "jsonld": "https://wpnews.pro/news/non-ascii-characters-in-q-are-not-decoded-when-assistant-is-opened-via-a-url-as.jsonld"}}