Decide whether web search should be on by default #55

Open
opened 2026-11-18 01:29:59 +00:00 by jbwexler · 4 comments

What's the idea?

Currently, the web search feature in the chat is off by default, though it was on by default at one point. There seem to be varying opinions and not yet a clear consensus, so I thought I would create a space to try to reach a decision. Even though technically it's very simple, I think it's a pretty important design choice for the co-op.

Why does it matter?

This is especially important for new users who may not know how to toggle the web search feature. Even for users who do know how, some of us may have a preference for the default. There are also potential security concerns with it being on by default.

Who is it for?

Anyone who uses the chat.

How might it work?

Obviously, it could either be on or off by default. Additionally, if it's off by default, there could be a way for individual users to set the default on their account to on.

Anything else?

If there were no security concerns, I personally would be strongly in favor of it being on by default, as I think most users probably assume that it would have access to the web. I would like to hear these security concerns fleshed out a little more so we can weigh them against the convenience/user-friendly factor, and/or if there any other ways to mitigate them.

Here are @solo.ist's thoughts from matrix:

Just my two cents, I think it makes the most sense to have default on settings be something that defaults to off globally but can be overidden to on at the individual level.
Reason being: Web search can result in prompt injection risk, and if someone isn't aware of that, it could result in problematic behavior on the part of the LLM if it accesses the wrong thing on the web.
So, I think it's better for someone individually to opt-in to it being on, and also consciously decide to leave it default on and be aware of and accept the risk at an individual level.

And @ntnsndr's reply:

I'll just say when I use the chat I almost always want search, but this is a real concern.Z

## What's the idea? Currently, the web search feature in the chat is off by default, though it was on by default at one point. There seem to be varying opinions and not yet a clear consensus, so I thought I would create a space to try to reach a decision. Even though technically it's very simple, I think it's a pretty important design choice for the co-op. ## Why does it matter? This is especially important for new users who may not know how to toggle the web search feature. Even for users who do know how, some of us may have a preference for the default. There are also potential security concerns with it being on by default. ## Who is it for? Anyone who uses the chat. ## How might it work? Obviously, it could either be on or off by default. Additionally, if it's off by default, there could be a way for individual users to set the default on their account to on. ## Anything else? If there were no security concerns, I personally would be strongly in favor of it being on by default, as I think most users probably assume that it would have access to the web. I would like to hear these security concerns fleshed out a little more so we can weigh them against the convenience/user-friendly factor, and/or if there any other ways to mitigate them. Here are @solo.ist's thoughts from matrix: > Just my two cents, I think it makes the most sense to have default on settings be something that defaults to off globally but can be overidden to on at the individual level. Reason being: Web search can result in prompt injection risk, and if someone isn't aware of that, it could result in problematic behavior on the part of the LLM if it accesses the wrong thing on the web. So, I think it's better for someone individually to opt-in to it being on, and also consciously decide to leave it default on and be aware of and accept the risk at an individual level. And @ntnsndr's reply: > I'll just say when I use the chat I almost always want search, but this is a real concern.Z

I wonder how well librechat will work if all options (not just search) are set to default to off? Maybe @solo.ist just meant the chat "chips"?

Whatever we choose it would be great if when the first time a user comes to librechat they a get a little tour/walkthrough of the interface, and the Web search chip is explained, along with what we are using for search? Maybe that is something the Design WG could take up?

I'm kinda confused though: web search seems to be set to default to on? But the chip is off when starting a new chat using greenpt/deepseek-v4.1-flash:

I wonder how well librechat will work if all options (not just search) are set to default to off? Maybe @solo.ist just meant the chat "chips"? Whatever we choose it would be great if when the first time a user comes to librechat they a get a little tour/walkthrough of the interface, and the Web search chip is explained, along with what we are using for search? Maybe that is something the Design WG could take up? I'm kinda confused though: web search seems to be set to default to on? But the chip is off when starting a new chat using greenpt/deepseek-v4.1-flash: * https://git.inference.coop/co-op/librechat-custom/src/commit/1ffd62afca56acc7437c2033be717e97e010f997/librechat.yaml#L69

Interestingly it looks like websearch is set to default to true on the master branch, but not on main? I wonder if there might be confusion about which branch is being deployed? I'm certainly confused why we would have both. It may also be an issue of not deploying the configuration file when it is updated since that appears to be a separate step in release.sh.

Generally speaking most people have decided to move from master to main? We appear to have switched to master from main for the librechat-custom at some point after November 7 (the date of the last commit to main).

Perhaps this issue should be transferred over to the librechat-custom repository?

Interestingly it looks like websearch is set to default to true on the `master` branch, but not on `main`? I wonder if there might be confusion about which branch is being deployed? I'm certainly confused why we would have both. It may also be an issue of not deploying the configuration file when it is updated since that appears to be a separate step in `release.sh`. Generally speaking most people have decided to move from `master` to `main`? We appear to have switched to `master` from `main` for the librechat-custom at some point after November 7 (the date of the last commit to `main`). Perhaps this issue should be transferred over to the [librechat-custom](https://git.inference.coop/co-op/librechat-custom/) repository?

Ok, now that the master/main branch mixup has been resolved I can see that the configuration reflects reality, no default search in the model specification:

- name: greenpt-deepseek-v4-1-flash

So discussion about what we want as a default can resume :-)

Ok, now that the master/main branch mixup has been resolved I can see that the configuration reflects reality, no default search in the model specification: https://git.inference.coop/co-op/librechat-custom/src/commit/e8dcb67f7a19bf0951783f6a8b2e7d1bfab7a137/librechat.yaml#L62 So discussion about what we want as a default can resume :-)

Thanks @ed for running down the branch mix-up. I'd read the same master config and was confused by the same thing. Confirming from my side: new conversations start with search off, and that now matches main.

To answer your question, I only meant web search, not the other options.

Two things from the config that seem useful for the decision:

There's no per-member default. What I suggested on Matrix (off globally, each member opts in to on) isn't something LibreChat offers. It has a global default per model and a per-conversation toggle. When I turned search on, it didn't carry over to my next conversation. A member can save an agent or preset with search on and start chats from that, but new users won't find it.

Default-on has a known side effect on our current build. The note in librechat.yaml explains why the default was removed on Nov 6: with search on by default, the client re-applies it at the start of a new conversation even after a member has turned it off. So choosing "on" today means either accepting that, or carrying a small client patch.

So as things stand the realistic options are:

  1. Off for everyone (current behavior).
  2. On for everyone, accepting that turning it off may not stick for the first reply.
  3. On by default with a client patch so a member's choice is respected. I can scope what that would take if there's interest.

I still lean toward off for the prompt injection reason, and I like your idea of a first-visit walkthrough that explains the search chip. That would help whichever default we pick, and it seems like a good fit for the Design WG.

Thanks @ed for running down the branch mix-up. I'd read the same `master` config and was confused by the same thing. Confirming from my side: new conversations start with search off, and that now matches `main`. To answer your question, I only meant web search, not the other options. Two things from the config that seem useful for the decision: **There's no per-member default.** What I suggested on Matrix (off globally, each member opts in to on) isn't something LibreChat offers. It has a global default per model and a per-conversation toggle. When I turned search on, it didn't carry over to my next conversation. A member can save an agent or preset with search on and start chats from that, but new users won't find it. **Default-on has a known side effect on our current build.** The note in `librechat.yaml` explains why the default was removed on Nov 6: with search on by default, the client re-applies it at the start of a new conversation even after a member has turned it off. So choosing "on" today means either accepting that, or carrying a small client patch. So as things stand the realistic options are: 1. Off for everyone (current behavior). 2. On for everyone, accepting that turning it off may not stick for the first reply. 3. On by default with a client patch so a member's choice is respected. I can scope what that would take if there's interest. I still lean toward off for the prompt injection reason, and I like your idea of a first-visit walkthrough that explains the search chip. That would help whichever default we pick, and it seems like a good fit for the Design WG.
Sign in to join this conversation.
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: co-op/support#55