How can I disable the "explain" and "ask" pop-ups whenever any text is selected?

[murtaza-nasir]

I do not like these pop ups as I am often working with code or other text that I am copying and these keep popping up and keep getting clicked accidentally which is extremely frustrating. Is there a way to disable these?

[AapoTahkola]

This is also interfering with linux selection-clipboard copy, I hate it because I cannot middle-click paste stuff.

[AapoTahkola]

You can get rid of these by using ublock origin picker and carefully aiming it the floating panel and blocking. So happy I found a way. My opinion about these floating things that automatically appear is that this feature should be removed completely as they serve no practical purpose. What is this, language learning app I do think the assumption is that people are literate.

[shayanPRESTIGE]

These popups are a single most frustrating part of of my workflow as they cause a lot of unintended API calls that cost me a lot at times.

[FrankenLab]

I agree these are one of the most frustrating parts of using Open-WebUI. Here's my solution using Tampermonkey. For those that don't know, Tampermonkey is a browser extension (both Firefox and Chrome based browsers), that allows you to install, manage, and run custom JavaScript scripts on websites. It modifies web pages or browser behaviors by injecting user-written code at runtime.

// @name         OpenWebUI Disable Floating Ask/Explain Buttons
// @namespace    http://tampermonkey.net/
// @version      1.0
// @description  Disable and hide Ask/Explain buttons in OpenWebUI
// @match        *://*/*
// @grant        none
// ==/UserScript==

(function() {
    'use strict';

    function disableElement() {
        const el = document.getElementById('floating-buttons-199422b2-f258-42bf-8c69-e6803e6cefe0');
        if (el) {
            // Hide the element
            el.style.display = 'none';

            // Disable pointer events so clicks do nothing
            el.style.pointerEvents = 'none';

            // Remove from DOM completely
            el.remove();

            // Stop further attempts to disable
            return true;
        }
        return false;
    }

    // Try once immediately
    if (!disableElement()) {
        // If element doesn't exist yet, observe DOM changes and disable when it appears
        const observer = new MutationObserver(() => {
            if (disableElement()) {
                observer.disconnect();
            }
        });
        observer.observe(document.body, { childList: true, subtree: true });
    }
})();```

[rgaricano]

Murtaza, I'm sorry if I gave you that impression, but I'm by no means against criticism, especially if it's constructive, and the truth is I hadn't noticed the dates.
Anyway, if it were something that bothered users too much and "should be removed" (as has also been mentioned), I imagine there would be more insistence from the rest of us who use it and those of us who don't find it so bothersome... which suggests it's not essential.
But don't worry, even though it's not necessary for me, I'm going to prepare a PR for it, and for your sake. That doesn't mean it will be accepted. I'm just a user who contributes and doesn't make any decisions.

[murtaza-nasir]

Thank you for the thoughtful reply and your understanding. I recognize that developers on a project like this can get overwhelmed with requests. I would have attempted to work on a PR for this myself, but the project's complexity is a bit beyond my current expertise as a hobbyist.

I and a lot of other people who find the buttons disruptive would be very grateful if you prepare a PR for this. Thank you very much for offering to take it on.

[rgaricano]

you can disable it from user settings > interface > quick actions

[get-loose]

Thanks so much @rgaricano

[rgaricano]

I didn't anything on that!, I also joint myself to thanks to Team!