29

I'm having the same issue accessing Assistant with Firefox from Debian's APT.
Firefox 115.15.0ESR is not that old... Also, make sure you include, in your tests before deploying something, whatever browser is packed by default in Debian, as I suspect that that is what a lot of your users are using.

Please fix this compatibility issue asap, as I'm currently paying for a service I cannot use.

z64 changed the title to Assistant page don't load correctly on Firefox ESR, librewolf .

    The new "The Assistant" does not seem to be working on my version of Firefox on a MacBook laptop.

    • The sidebar does not seem to be loading, or formatted, correctly (see attached screenshot).
    • The drop down below the search box to select an assistant seems to be stuck on "Loading..."
    • You can enter text in the search box but when you press return or click on the start search triangle button the search box is cleared of the text and nothing happens.

    My current Kagi Status is shown as:
    "...
    Status
    Connected to: AUSTRA-SOUTHEAST1
    Network latency: 31ms
    ..."

    MacBook operating system is macOS Big Sur 11.7.10.
    Firefox is reported as "up to date" with version 115.15.0esr (64-bit). All extensions turned off.

    I have logged out and back in to Kagi and the same problem occurs.

    Assistant to work with Firefox as it has in the past.

      works perfect for me. Maybe because your software is outdated.

      macos is currently at 14.5 and FF is 130 . Try pressing cmd+shift+R that will give a new reload to your page

        The Assistant requires some features Firefox ESR 115 does not have. The team is looking into it. In the meantime, if possible, please consider upgrading to ESR 128 to fix the issue.

        By @z64 on Kagi Discord:

          Merged 3 posts from New Assistant not working with Firefox on Macbook.

            Thank you all.

            I can see the issue now - I was using Firefox "Extended Support Release", mistakenly thinking it would be the most stable and reliable. (screenshot attached.)

            I have now reinstalled Firefox from the "Standard" (?) release and that now seems to work correctly. (screenshot attached).

            Apologies for not checking that.

              Vlad changed the title to Assistant page don't load correctly on Firefox ESR 115, librewolf .
                • While logged in, browse to https://kagi.com/assistant.
                • Notice the model drop-down menu (just below the prompt input) reads "Loading..." (and never finishes).
                • Clicking the "X" for the "Private by default" pop-over does nothing.
                • Browser console shows "Uncaught TypeError: Ur.showPopover is not a function"

                Attempting to enter and submit a prompt does nothing in the UI, but results in a different console error:

                Yes, Firefox 115 is not the latest, but it's still a supported ESR release that gets security updates. I use it because it's default browser on Debian stable.

                And yes, I have JavaScript enabled 🙂

                Assistant works as expected in Chromium 128 on the same computer.

                • Luis replied to this.

                  I also have this same issue. Model drop down stuck on "Loading...".

                  I'm on debian trixie/sid with firefox 115.15.0esr-1.

                  I can confirm chrome works too.

                    cmart I'll merge this thread with a related one that has additional follow ups.

                      Merged 3 posts from Cannot use new Assistant on Firefox 115 ESR (Debian Linux).

                        Steps:

                        1. In Safari, load the assistant
                        2. Press the button marked "Claude 3.5 Sonnet"

                        Actual:

                        1. A modal is displayed with the words "No results"

                        Expected:

                        1. A list of models appears to choose a different LLM model

                        Confirmed that it works in Chrome.

                          Hey Ben,
                          which version of Safari (and macOS) is this happening on? Do you have any browser extensions installed?
                          I am unable to reproduce the issue on macOS Sonoma 14.6.1 running Safari Version 17.6 (19618.3.11.11.5)

                            I was running 1Blocker and StopTheMadness but I'm still seeing it after disabling both of those. Let me know if there's anything else I can do to help debug.

                            Update:
                            I tried this in Safari 16 in BrowserStack and in that case the list doesn't load at all:

                            And Safari 17.3 in BrowserStack:

                            Unhandled Promise Rejection: TypeError: Object.groupBy is not a function. (In 'Object.groupBy(w,e=>e.id?"customAssistants":e.model_provider_name)', 'Object.groupBy' is undefined

                            Looks like groupBy wasn't fully supported until 17.4:

                            • laiz replied to this.

                              BenJohnson
                              Thanks for digging deeper. Indeed, older versions missing some features seem to be causing issues. This is very similar to #4726 and unfortunately the only remedy for now is to install a more up-to-date version of Safari.

                              • Luis replied to this.

                                  Kagi should have a clear policy of how old browsers they support. This is a very common problem within the industry.

                                  In this case they can either polyfill groupBy or write the code differently.

                                  The problem with Safari is that you can’t just ask users to update. The versions are bound to OS version. So for instance, a lot of users are on old iOS devices, locked to Safari 12, which is really old, and Kagi should strategically decide if they want to support these users or not. It is possible, just a bit of extra work.

                                  laiz @BenJohnson Yes. I'm merging this thread with the other since both report the same problem, and the other thread has further details and follow up discussion

                                      Merged 6 posts from Cannot change models in assistant in Safari.