mirror of
https://github.com/SillyTavern/SillyTavern-WebSearch-Selenium.git
synced 2026-11-05 00:37:40 +00:00
[GH-ISSUE #14] TypeError: Cannot destructure property 'textBits' when using Selenium Plugin with SillyTavern 1.17.0 #10
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
SillyTavern/SillyTavern-WebSearch-Selenium#10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nanaka050 on GitHub (Apr 24, 2026).
Original GitHub issue: https://github.com/SillyTavern/SillyTavern-WebSearch-Selenium/issues/14
Hi! First of all, I'm not very tech savvy, so I might have done something wrong during the plugin installation/configuration.
I’m having an issue using the SillyTavern-WebSearch-Selenium plugin with the latest SillyTavern release.
Here is what I did so far:
Enabled server plugins in config.yaml: enableServerPlugins: true
In the plugins directory of SillyTavern, I ran:
git clone https://github.com/SillyTavern/SillyTavern-WebSearch-Selenium
cd SillyTavern-WebSearch-Selenium
npm install
npm run build
Restarted the SillyTavern server.
I enabled the Web Search extension in the UI and selected "Selenium Plugin" as the source.
Triggered a web search from the chat - any query gives the same result:
From the model side (tool-calling logs), the WebSearch tool itself is correctly registered and invoked, but the returned object seems to be missing the textBits field that SillyTavern 1.17.0 expects. Because of that, ST fails before any web content reaches the model.
I restarted SillyTavern server and tried multiple times after installation and build - it still gives the same error.
Does anyone know what the issue is?
Edit: I changed the "headless" variable to "false" and did the Captcha manually (I though that was the issue) - it still gives the same error and the logs look like this: