Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #2426] [DOCS]: SERP Configuration (Live Web Search and Browsing) #1578

New Issue
Closed
opened 2026-02-22 18:25:29 -05:00 by yindo · 6 comments
yindo commented 2026-02-22 18:25:29 -05:00
Owner
Copy Link
Copy Source

Originally created by @WizenThorne on GitHub (Oct 4, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2426

Description

Could we get a little more clarification in getting the SERP configured, including the way to invoke a Web Search? As far as I've been able to glean from looking through other Issue conversations, the search is initiated using the @agent command followed by some sort of prompt like "Do a web search for XYZ". Is there a way to inform the LLM or Workspace to prioritize a current web search over information stored in the LLM, and can this be invoked without using the @agent command? An update to the DOCs could help clarify some of this.

Originally created by @WizenThorne on GitHub (Oct 4, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2426 ### Description Could we get a little more clarification in getting the SERP configured, including the way to invoke a Web Search? As far as I've been able to glean from looking through other Issue conversations, the search is initiated using the @agent command followed by some sort of prompt like "Do a web search for XYZ". Is there a way to inform the LLM or Workspace to prioritize a current web search over information stored in the LLM, and can this be invoked without using the @agent command? An update to the DOCs could help clarify some of this.
yindo added the documentation label 2026-02-22 18:25:29 -05:00
yindo closed this issue 2026-02-22 18:25:29 -05:00
yindo commented 2026-02-22 18:25:30 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Oct 4, 2024):

Since SERP is an agent skill, it must be done in an agent session since we currently differentiate the traditional RAG chat vs agent sessions.

You can prioritize tool calls over looking in memory via the workspaces system prompt though so you dont have to type it every session

@timothycarambat commented on GitHub (Oct 4, 2024): Since SERP is an agent skill, it must be done in an agent session since we currently differentiate the traditional RAG chat vs agent sessions. You can prioritize tool calls over looking in memory via the workspaces system prompt though so you dont have to type it every session
yindo commented 2026-02-22 18:25:30 -05:00
Author
Owner
Copy Link
Copy Source

@WizenThorne commented on GitHub (Oct 4, 2024):

Since SERP is an agent skill, it must be done in an agent session since we currently differentiate the traditional RAG chat vs agent sessions.

You can prioritize tool calls over looking in memory via the workspaces system prompt though so you dont have to type it every session

Do you know what I could put in that prompt to make that happen? I've tried a number of different workspace prompts and it always results in the LLM stating it doesn't have access to real-time information unless I force it to access the web search agent skill using the @agent command.

@WizenThorne commented on GitHub (Oct 4, 2024): > Since SERP is an agent skill, it must be done in an agent session since we currently differentiate the traditional RAG chat vs agent sessions. > > You can prioritize tool calls over looking in memory via the workspaces system prompt though so you dont have to type it every session Do you know what I could put in that prompt to make that happen? I've tried a number of different workspace prompts and it always results in the LLM stating it doesn't have access to real-time information unless I force it to access the web search agent skill using the @agent command.
yindo commented 2026-02-22 18:25:30 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Oct 5, 2024):

https://docs.anythingllm.com/agent-not-using-tools

What model are you using?

@timothycarambat commented on GitHub (Oct 5, 2024): https://docs.anythingllm.com/agent-not-using-tools What model are you using?
yindo commented 2026-02-22 18:25:30 -05:00
Author
Owner
Copy Link
Copy Source

@WizenThorne commented on GitHub (Oct 5, 2024):

Llama3.1 but I also tried with llama2.

@WizenThorne commented on GitHub (Oct 5, 2024): Llama3.1 but I also tried with llama2.
yindo commented 2026-02-22 18:25:30 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Oct 7, 2024):

Do you know what I could put in that prompt to make that happen? I've tried a number of different workspace prompts and it always results in the LLM stating it doesn't have access to real-time information unless I force it to access the web search agent skill using the https://github.com/agent command.

Apologies i misread this previously. The "force" of the agent to search is always what is required. Once you call @agent this starts a session where any tool is available until you either nav off the page or the agent responds session closed.

The RAG chat (which is the default when you nav to a workspace) will never be able to live-scrape a site as it does not have agent-delegation. You have to do @agent again to start a session. I think that is where the confusion lies here.

Calling @agent once ever in the workspace does not enable it forever and every new time you boot up the app or open the workspace. it is only for that specific session at the time. Does that make more sense now how @agent functions?

@timothycarambat commented on GitHub (Oct 7, 2024): > Do you know what I could put in that prompt to make that happen? I've tried a number of different workspace prompts and it always results in the LLM stating it doesn't have access to real-time information unless I force it to access the web search agent skill using the https://github.com/agent command. Apologies i misread this previously. The "force" of the agent to search is always what is required. Once you call `@agent` this starts a session where any tool is available until you either nav off the page or the agent responds `session closed`. The RAG chat (which is the default when you nav to a workspace) will never be able to live-scrape a site as it does not have agent-delegation. You have to do `@agent` again to start a session. I think that is where the confusion lies here. Calling `@agent` once ever in the workspace does not enable it forever and every new time you boot up the app or open the workspace. it is only for that specific session at the time. Does that make more sense now how `@agent` functions?
yindo commented 2026-02-22 18:25:30 -05:00
Author
Owner
Copy Link
Copy Source

@Julian-Dumitrascu commented on GitHub (Dec 5, 2025):

I'm setting up your program.
I've toggled on the live web search and browsing.
I'd use SearXNG when someone shares their API Base URL.

@Julian-Dumitrascu commented on GitHub (Dec 5, 2025): I'm setting up your program. I've toggled on the live web search and browsing. I'd use SearXNG when someone shares their [API Base URL](https://docs.searxng.org/search.html?q=API+Base+URL).
yindo changed title from [DOCS]: SERP Configuration (Live Web Search and Browsing) to [GH-ISSUE #2426] [DOCS]: SERP Configuration (Live Web Search and Browsing) 2026-06-05 14:41:31 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label documentation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1578
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?