"Search instead" puts quotes in the wrong place

systemed

Steps to reproduce:

Search for cwmblewyn bridleway
Kagi says:
- Showing results for cwm berwyn bridleway
- Search instead for cwmblewyn bridleway
Click on the second one (Search instead...)

Expected behavior:
"Search instead" should enclose the replaced term only in quotes, i.e. "cwmblewyn" bridleway
Instead, it encloses the whole query in quotes, i.e. "cwmblewyn bridleway", which then produces no results

Debug info:
Mac Safari, UK, Europe West

Image/Video:

dreamplus

Steps to reproduce:

Search react-native-version postversion
Click on "Search instead for"

Expected behavior:
Clicking on "Search instead for ..." should only quote the term that was changed. In this case, the search term should be modified to react-native-version "postversion"

Debug info:
Windows 10/Firefox

Image/Video:

erik

Steps to reproduce:

Search for createLoggingMiddleware pino,
observe that it actually searches for create Logging Middleware pino
accept helpful suggestion to actually search for createLoggingMiddleware pino by clicking on it
observe that it now searches for "createLoggingMiddleware pino" with quotes around the entire expression instead of just around createLoggingMiddleware pino

Expected behavior:

In step 4 I expected it to only add quotes around createLoggingMiddleware, producing a new query that looks like this: "createLoggingMiddleware" pino

Debug info:
LibreWolf, Windows, EUROPE-WEST2

Image/Video:

This is just a minor ux issue for me since I am old enough to know how it works, but it might hassle users who doesn't realize or doesn't pay attention.

riddley

This happened to me as well

I searched for

riese muller tinker2

Kagi responds with

Showing results for riese muller tinker 2
Search instead for riese muller tinker2

When I choose that the search text becomes

"riese muller tinker2"

Where it should be

riese muller "tinker2"