[GH-ISSUE #22749] issue: URL Indexed Twice When Using Multiple Triggers and Backspace in Chat Input #35339

Closed
opened 2026-04-25 09:34:00 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @silentoplayz on GitHub (Mar 17, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22749

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.8.10

Ollama Version (if applicable)

v0.18.0

Operating System

Ubuntu 24.04.4 LTS

Browser (if applicable)

Mozilla Firefox Snap for Ubuntu v148.0.2 (64-bit) / Google Chrome v146.0.7680.80 (Official Build) (64-bit)

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

When using multiple triggers in sequence (e.g., selecting a skill with $ then adding a URL with #), the URL should only be indexed and added to the chat context once.

Actual Behavior

The URL is indexed twice, resulting in two identical URL chips appearing above the chat input. This happens if the user selects a skill/prompt trigger, then types the # trigger, backspaces to remove the #, and then re-types # to add a URL.

Steps to Reproduce

  1. Start an Open WebUI instance (v0.8.10).
  2. In the chat input, type $ and select a skill (e.g., $Visualize).
  3. Press Space.
  4. Type the # trigger. A popup modal appears.
  5. Press Backspace ONCE to remove the # trigger character.
  6. Type # again to trigger the URL/file selector.
  7. Enter a URL (e.g., https://www.goody2.ai/).
  8. Select the URL in the popup modal or simply press Enter on the keyboard.
  9. Observe that the URL is indexed twice rather than once.

Alternative / Easier Method (Multiple Triggers)

  1. Start an Open WebUI instance (v0.8.10).
  2. Type $ to select a skill (e.g., $Visualize).
  3. Type $ again to select another skill (or prompt with /).
  4. Follow immediately with #.
  5. Enter a URL and press Enter / select it.
  6. Result: The second skill/prompt is wiped, but the double-indexing of the URL is consistently triggered. If you include multiple triggers (more than 2) before steps 4-5, the last 2 triggers will always be removed and the double-indexing bug can be observed.

Logs & Screenshots

Step 2: Start with a skill selection (using $).
Skill selected

Step 4: Type the # trigger.
Hashtag trigger typed

Step 5: Press Backspace to remove the #.
Hashtag removed with backspace

Step 7: Type # again and enter a URL immediately following after the #.
URL being entered

Step 9: Select the URL and observe the double-indexing bug.
Double indexing bug

  • Note on Reproducibility: This issue is specific to the # trigger workflow in the chat input. It cannot be reproduced by using the Attach Webpage option from the More (+) modal. Using the UI menu option results in correct (single) indexing.

(Menu Comparison)

Attach Webpage UI: Selecting the menu option directly.

Attach Webpage Menu

Result: Correct single indexing when using the menu.
Single indexing via menu

Additional Information

  • This issue can also be reproduced using the / trigger instead of $.
  • It seems the internal state or event listener for the # trigger isn't being properly cleaned up when backspaced, causing the subsequent selection event to fire twice.
Originally created by @silentoplayz on GitHub (Mar 17, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22749 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.8.10 ### Ollama Version (if applicable) v0.18.0 ### Operating System Ubuntu 24.04.4 LTS ### Browser (if applicable) Mozilla Firefox Snap for Ubuntu v148.0.2 (64-bit) / Google Chrome v146.0.7680.80 (Official Build) (64-bit) ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior When using multiple triggers in sequence (e.g., selecting a skill with `$` then adding a URL with `#`), the URL should only be indexed and added to the chat context once. ### Actual Behavior The URL is indexed twice, resulting in two identical URL chips appearing above the chat input. This happens if the user selects a skill/prompt trigger, then types the `#` trigger, backspaces to remove the `#`, and then re-types `#` to add a URL. ### Steps to Reproduce 1. Start an Open WebUI instance (v0.8.10). 2. In the chat input, type `$` and select a skill (e.g., `$Visualize`). 3. Press `Space`. 4. Type the `#` trigger. A popup modal appears. 5. Press `Backspace` ONCE to remove the `#` trigger character. 6. Type `#` again to trigger the URL/file selector. 7. Enter a URL (e.g., `https://www.goody2.ai/`). 8. Select the URL in the popup modal or simply press `Enter` on the keyboard. 9. Observe that the URL is indexed twice rather than once. ### Alternative / Easier Method (Multiple Triggers) 1. Start an Open WebUI instance (v0.8.10). 2. Type `$` to select a skill (e.g., `$Visualize`). 3. Type `$` again to select another skill (or prompt with `/`). 4. Follow immediately with `#`. 5. Enter a URL and press `Enter` / select it. 6. **Result:** The second skill/prompt is wiped, but the double-indexing of the URL is consistently triggered. If you include multiple triggers (more than 2) before steps 4-5, the last 2 triggers will always be removed and the double-indexing bug can be observed. ### Logs & Screenshots **Step 2:** Start with a skill selection (using `$`). <img width="431" height="240" alt="Skill selected" src="https://github.com/user-attachments/assets/593f5727-8278-4e95-a0ca-ced2cacd89b3" /> **Step 4:** Type the `#` trigger. <img width="439" height="366" alt="Hashtag trigger typed" src="https://github.com/user-attachments/assets/a3d71cf3-e4b7-4d2a-8a4b-1bb9f987595d" /> **Step 5:** Press `Backspace` to remove the `#`. <img width="431" height="240" alt="Hashtag removed with backspace" src="https://github.com/user-attachments/assets/593f5727-8278-4e95-a0ca-ced2cacd89b3" /> **Step 7:** Type `#` again and enter a URL immediately following after the `#`. <img width="429" height="162" alt="URL being entered" src="https://github.com/user-attachments/assets/ff26a4c4-cd91-47a4-a39a-0fb20bdad68a" /> **Step 9:** Select the URL and observe the double-indexing bug. <img width="540" height="171" alt="Double indexing bug" src="https://github.com/user-attachments/assets/5fe9ea94-26f5-45eb-99d4-64303712278b" /> - **Note on Reproducibility:** This issue is specific to the `#` trigger workflow in the chat input. It **cannot** be reproduced by using the `Attach Webpage` option from the `More` (`+`) modal. Using the UI menu option results in correct (single) indexing. ## (Menu Comparison) **Attach Webpage UI:** Selecting the menu option directly. <img width="499" height="212" alt="Attach Webpage Menu" src="https://github.com/user-attachments/assets/220c851a-3e42-4af8-aead-f89167cac975" /> **Result:** Correct single indexing when using the menu. <img width="286" height="169" alt="Single indexing via menu" src="https://github.com/user-attachments/assets/144b84d2-5435-427b-88ad-67b8dd596cad" /> ### Additional Information - This issue can also be reproduced using the `/` trigger instead of `$`. - It seems the internal state or event listener for the `#` trigger isn't being properly cleaned up when backspaced, causing the subsequent selection event to fire twice.
GiteaMirror added the bugconfirmed issue labels 2026-04-25 09:34:00 -05:00
Author
Owner

@tjbck commented on GitHub (Mar 20, 2026):

@silentoplayz could you confirm if the issue has been addressed in dev?

<!-- gh-comment-id:4101439694 --> @tjbck commented on GitHub (Mar 20, 2026): @silentoplayz could you confirm if the issue has been addressed in dev?
Author
Owner

@silentoplayz commented on GitHub (Mar 20, 2026):

@silentoplayz could you confirm if the issue has been addressed in dev?

Yes, I can confirm this reported issue in particular has been resolved on the dev branch. Closing this issue now.

<!-- gh-comment-id:4101499099 --> @silentoplayz commented on GitHub (Mar 20, 2026): > [@silentoplayz](https://github.com/silentoplayz) could you confirm if the issue has been addressed in dev? Yes, I can confirm this reported issue in particular has been resolved on the `dev` branch. Closing this issue now.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#35339