feat(server): tell agents about the Threadlines browser panel - #204
Merged
Conversation
Claude never learned the browser panel existed. The SDK defers MCP tool descriptions behind tool search, so Claude saw eighteen tool names and none of their text, and nothing in its system prompt mentioned Threadlines or the panel. Codex had a note, but it only said what "our browser" meant; it never said to prefer the panel. Agents defaulted to Chrome DevTools or Playwright unless told otherwise. Load the browser MCP server's tools into Claude's prompt (alwaysLoad), append a browser note to Claude's system prompt, and rewrite the note both providers share so it says when to use the panel and why, naming each provider's rival tooling. Tool descriptions and the no-host error now use the same words: "browser panel", and "no desktop window is showing this thread" instead of asking the user to open a panel that opens itself.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
size:L
vouch:trusted
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.
Claude never learned the browser panel existed. The SDK defers MCP tool descriptions behind tool search, so Claude saw eighteen tool names and none of their text, and nothing in its system prompt mentioned Threadlines or the panel. Codex had a note, but it only said what "our browser" meant; it never said to prefer the panel. Agents defaulted to Chrome DevTools or Playwright unless told otherwise.
This loads the browser MCP server's tools into Claude's prompt (
alwaysLoad), appends a browser note to Claude's system prompt, and rewrites the note both providers share so it says when to use the panel and why, naming each provider's rival tooling. Tool descriptions and the no-host error now use the same words: "browser panel", and "no desktop window is showing this thread" instead of asking the user to open a panel that opens itself.Cost: about 3k tokens of tool schemas plus a 400-token note per turn, all in the cached prefix.