Queries launched through a Kagi Assistant bang are no longer decoded correctly before being submitted to the Assistant.
For example, in the Chrome address bar I enter:
research recent news, only globally important ones! !q
Kagi Assistant opens, but the submitted prompt is displayed as:
research recent news%2C only globally important ones%21
The comma is left as %2C, and the exclamation mark is left as %21.
Steps to reproduce
Use Google Chrome on desktop with Kagi configured as the default search engine.
Enter the following in the address bar:
research recent news, only globally important ones! !q
Press Enter.
Observe the prompt submitted to Kagi Assistant.
Actual result
The Assistant receives:
research recent news%2C only globally important ones%21
instead of the decoded text.
Regression information
This worked correctly until approximately one week ago.
The timing suggests that this may be related to the fix for the following issue, which changed Assistant bangs to route directly to assistant.kagi.com:
#11077 – !ai bang – Query not working](https://kagifeedback.org/d/11077-fixed-ai-bang-query-not-working)
The new direct route may be passing an already URL-encoded query to the Assistant without decoding the q parameter.
This is reproducible with the !q Quick Assistant bang. It may also affect other Assistant bangs such as !ai.
The Assistant should decode the query parameter before submitting or displaying the prompt.
For the input:
research recent news, only globally important ones! !q
the Assistant should receive:
research recent news, only globally important ones!
URL encoding such as %2C, %21, and %3F should not appear as literal text in the submitted prompt.