Kagi Assistant (UPD: All Services) "Open Base Path" Now Broken (Regression)

Timmy256

Hi, I've always used this (!k <Prompt>) for assistant prompts and, if left blank, it would open the Assistant. Trying it now, it returns a ERR_INVALID_REDIRECT error instead of landing on the Assistant; as it always did.

The URL for the bang I'm using is https://kagi.com/assistant?q=%s. Yet, manually going to https://kagi.com/assistant works (so the Open Base Path should work), so there is clearly some issue that was introduced between Kagi doing the redirect its own Assistant there that broke this.

Could you please look at this? This is clearly a regression. Thanks.

EDIT/UPDATE: All Kagi own services redirects are broken! None of this that I had set up work and all through the same redirect error instead of opening the base path

nobodywasishere

Can you send me a screenshot of one of your bangs? I wasn't able to reproduce and want to make sure I have the same bang settings set. As well, what browser / OS are you using?

Timmy256

Thanks for replying @nobodywasishere. Attaching the bang for the " k" that would take me to the assistant home page. All of the bangs were working fine until a few days ago (sometime before I created this post; when I noticed).

All browsers fail. Chromium returns the ERROR REDIRECT screen attached; Safari triggers the download of a "search" file.

Thanks.

EDIT: @nobodywasishere as I realized as I was taking the bang screenshot (as I did this so long ago). Open Base Bath is disabled, because if it was enabled, they all would take me to Kagi.com. But, in the past, sending an empty value for "%s" actually landed on the proper service (Assistant, Summarizer, etc.); now after some changes is where it seems you started giving the redirect error.

My use case here was, if I quickly want to go to any of those services, I'd type "!k", "!ks", etc. (with an empty query string) and it would land me there ready to use. After those changes, this stopped working and, obviously Open Base Path won't work as they would send me to kagi.com

nobodywasishere

Not that I imagine this will have an impact, but can you try removing what you have for the domain for snaps?

Timmy256

Hi @nobodywasishere. Just checked it now and, without touching anything on my end, the Assistant redirect was working again (even with the "/" in the Snaps field).

The rest (except Translate, which resolves to a different domain and I can use the Open Base... option) still weren't working. Removed the "/" from Snaps for each and they are working now.

I'm happy that it works, although this erratic behaviour makes me feel like it might break again sometime soon. I'll post again in this thread if this happens.

Thanks.

nobodywasishere

Thank you for the update, please let us know if this happens again.