docs: document You.com as alternative browser backend for gpt-oss#603
Open
tyler5673 wants to merge 2 commits into
Open
docs: document You.com as alternative browser backend for gpt-oss#603tyler5673 wants to merge 2 commits into
tyler5673 wants to merge 2 commits into
Conversation
The gpt-oss reference library ships a YouComBackend and the MCP browser server (browser_server.py) defaults to BROWSER_BACKEND=youcom, but the vLLM gpt-oss recipes only documented the Exa backend. Add a brief 'Browser backend' section to both the 20b and 120b recipe guides showing how to use You.com via the MCP browser server with YDC_API_KEY. The mcp run and vllm serve commands are in separate code blocks since both are long-running blocking processes that need separate terminals. Signed-off-by: Tyler Eastman <tyler@you.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the documentation for the gpt-oss-120b and gpt-oss-20b models by adding a 'Browser backend' section to guide users on configuring web search using Exa or You.com. The reviewer correctly identified a potential port conflict when running both the MCP browser server and the vLLM server on the same machine, as both default to port 8000. To resolve this, it is recommended to explicitly set a different port (such as PORT=8001) for the MCP server.
The MCP browser server (browser_server.py) defaults to port 8001, not 8000. Replace the vague <browser-server-ip>:<port> placeholder with a concrete localhost:8001 example and note the default port. Signed-off-by: Tyler Eastman <tyler@you.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The gpt-oss reference library ships a
YouComBackendand the MCP browser server (browser_server.py) defaults toBROWSER_BACKEND=youcom, but the vLLM gpt-oss recipes only documented the Exa backend.This adds a brief "Browser backend" section to both the 20b and 120b recipe guides showing how to use You.com via the MCP browser server with
YDC_API_KEY.The demo tool server path (
--tool-server demo) still uses Exa by default and is noted as such. The You.com path applies to the MCP browser server, which defaults toBROWSER_BACKEND=youcom.The
mcp runandvllm servecommands are in separate code blocks since both are long-running blocking processes that need separate terminals.