Skip to content

feat: create subagents for search and fetch calls to disable default …#77

Open
Kylejeong2 wants to merge 1 commit intomainfrom
kylejeong/gro-1299-disable-native-search-and-fetch-in-browse-cli
Open

feat: create subagents for search and fetch calls to disable default …#77
Kylejeong2 wants to merge 1 commit intomainfrom
kylejeong/gro-1299-disable-native-search-and-fetch-in-browse-cli

Conversation

@Kylejeong2
Copy link
Copy Markdown
Member

@Kylejeong2 Kylejeong2 commented Apr 24, 2026

…behavior

Summary

Disabling default claude web search and fetch if the user opts to use the browse CLI/skill.

Claude code subagents load definitions from the /agents directory, which is why I added a small md file there.


Note

Medium Risk
Medium risk because it changes default web retrieval behavior by forcing fetch/search through a constrained subagent, which may affect tool availability and user workflows.

Overview
Introduces a new browserbase-web subagent (Bash-only) and updates the fetch and search skills to execute with context: fork inside that agent, preventing any fallback to Claude’s built-in WebFetch/WebSearch.

Updates marketplace registration to include the new fetch and search skills under the browse plugin, and documents the override/opt-out behavior in README.md.

Reviewed by Cursor Bugbot for commit 856fa1c. Bugbot is set up for automated code reviews on this repo. Configure here.

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 4 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 856fa1c. Configure here.

Comment thread skills/fetch/SKILL.md
allowed-tools: Bash
context: fork
agent: browse:browserbase-web
allowed-tools: Bash(curl *) Bash(bb *)
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-standard allowed-tools Bash pattern syntax

Medium Severity

The allowed-tools entry Bash(curl *) Bash(bb *) in the skill frontmatter uses non-standard syntax. It's missing a comma between the two Bash patterns and uses a space instead of a colon for the command filter wildcards (e.g., Bash(curl:*)). This may prevent proper parsing, causing bb commands to be blocked or require explicit permission.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 856fa1c. Configure here.

Comment thread skills/fetch/SKILL.md
allowed-tools: Bash
context: fork
agent: browse:browserbase-web
allowed-tools: Bash(curl *) Bash(bb *)
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Subagent restriction silently ignored for plugin skills

Medium Severity

The context: fork and agent: frontmatter fields are a known silent no‑op for skills distributed via a plugin marketplace (Claude Code issue #35054, still open in v2.1.76 / March 2026). Because both skills are loaded through .claude-plugin/marketplace.json, they run inline in the main agent context rather than being dispatched to the browserbase-web subagent, so the main agent retains access to WebFetch/WebSearch and the intended restriction never takes effect. The README.md "overrides WebFetch / WebSearch" claim therefore overstates the actual behavior.

Additional Locations (2)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 856fa1c. Configure here.

Comment thread skills/search/SKILL.md
allowed-tools: Bash
context: fork
agent: browse:browserbase-web
allowed-tools: Bash(curl *)
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Search skill blocks bb that shared agent expects

Low Severity

The shared browserbase-web subagent is instructed to "Run the curl or bb command provided in the prompt", and bb search is a real Browserbase CLI command referenced by other skills (browserbase-cli, company-research). However, the search skill restricts allowed-tools to Bash(curl *) only, so if the subagent selects bb search it will be denied, while the same agent invoked from fetch has Bash(bb *) available. Consider granting Bash(bb *) in the search skill or tightening the agent prompt to curl only for search.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 856fa1c. Configure here.

Comment thread skills/fetch/SKILL.md
---
name: fetch
description: "Use this skill when the user wants to retrieve a URL without a full browser session: fetch HTML or JSON from static pages, inspect status codes or headers, follow redirects, or get page source for simple scraping. Prefer it over a browser when JavaScript rendering and page interaction are not needed. Supports proxies and redirect control."
description: "DEFAULT for retrieving any URL HTML, JSON, status codes, headers, redirects. Use for any fetch, scrape, or HTTP inspection request. Prefer this over the built-in WebFetch."
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fetch/search skills conflict with browserbase-cli routing

Low Severity

The rewritten descriptions declare the skills as "DEFAULT for retrieving any URL" and "DEFAULT for any web search", but the browserbase-cli plugin's description and skill already claim ownership of the same operations via bb fetch / bb search. With both plugins installed, two skills aggressively claim default routing for every fetch/search, which can produce inconsistent selection and double-cover the same Browserbase APIs. It also overreaches for local/localhost URLs where a browser session or WebFetch would be more appropriate.

Additional Locations (2)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 856fa1c. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant