Skip to content

Commit c438ab2

Browse files
browser-navigation: ask user before disabling MCPs
Don't run /mcp remove directly - suggest the commands and let the user decide. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
1 parent cf89d11 commit c438ab2

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

  • plugins/droid-evolved/skills/browser-navigation

plugins/droid-evolved/skills/browser-navigation/SKILL.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -358,17 +358,17 @@ agent-browser find nth 2 "a" text
358358
359359
## Disable conflicting MCPs
360360
361-
If you have Chrome DevTools or Playwright MCP enabled, disable them to save context. This skill covers the same functionality.
361+
If Chrome DevTools or Playwright MCP is enabled, ask the user if they want to disable it to save context. This skill covers the same functionality.
362362
363-
Check what's enabled:
363+
Ask them to run:
364364
```
365365
/mcp
366366
```
367367
368-
Remove the conflicting MCP:
368+
If they see chrome-devtools or playwright listed, suggest they remove it:
369369
```
370370
/mcp remove chrome-devtools
371371
/mcp remove playwright
372372
```
373373
374-
agent-browser handles everything those MCPs do, so there's no reason to have them loaded at the same time.
374+
Don't run these commands yourself. Let the user decide whether to disable the MCP.

0 commit comments

Comments
 (0)