3

When a lens is enabled, it would be nice if search autocomplete used information from the lens to make better suggestions.

If the lens contains keywords this could be done by prepending the keywords to the typed autocomplete string.

So for example if the lens included the keywords "slay spire" and the user typed "runic" into the search box, Kagi would actually autocomplete on the string "slay spire runic".

The presence of the lens keywords could be invisible to the user, or displayed in or near the search box in unmodifiable text as a visual reminder.

  • Vlad replied to this.
    12 days later

    riddley the way keywords work is they can appear anywhere on the page not necessarly together. So I am not sure this can be genralized.

        Hi Vlad, I'm not sure how that affects my suggestion? Here's a more detailed description of what I mean.

        Just say I'm searching for info about the game Slay The Spire, as I often do, without using a lens. It has a number of items in it called "runic pyramid", "runic dome", "runic cube".

        I type "slay spire runic" and I immediately get really good quality, relevant autocomplete suggestions.

        Then I set up a lens with they keywords "slay spire".

        I activate the lens, I type "runic" and I get irrelevant autocomplete suggestions.

        But if Kagi automatically used the keywords from the lens definition in the API call to autocomplete, suggestions would be relevant again. Prepending them seems logical to me, but no matter where you put them in the autocomplete API call, the suggestions would be better than leaving them out. E.g. "slay spire runic" and "runic slay spire" both give much better suggestions than just "runic".

          riddley Ok I now understand what you mean, this should be easy to do.

              7 days later
              No one is typing