feat(mcp): disable Playwright MCP by default#77
Merged
Conversation
Browser tools are now opt-in. Until the user enables Playwright from
the MCP settings UI, neither the main agent nor the browser-pilot crew
sees browser_navigate/click/screenshot/etc. The intent is that browser
work routes through use_crew("browser-pilot", ...) deliberately rather
than the main agent reaching for browser tools unprompted.
When the user does enable it, both the main agent and browser-pilot
get the tools simultaneously — current architecture is single MCP
server, shared catalog. (Per-crew MCP scoping would be a separate
larger change.)
4 tasks
UmarFarooq75
added a commit
that referenced
this pull request
May 7, 2026
## Summary Promotes the installer + safety changes from \`dev\` to \`main\`. What lands: - **PR #78** \`feat(install): native installers (.pkg + .exe)\` — proper macOS \`.pkg\` builder + Windows Inno Setup \`.exe\` with real icons. Replaces the curl-pipe scripts as the recommended path for non-technical users. - **PR #77** \`feat(mcp): disable Playwright MCP by default\` — browser tools become opt-in. Main agent and browser-pilot crew don't see \`browser_*\` tools until the user enables Playwright in MCP settings. - **PR #75** + follow-up fixes \`1cf856f\` and \`f61032a\` — the original curl-pipe scripts plus the two patches I pushed during testing (osascript GUI password prompt for non-TTY sudo; Unicode ellipses replaced with ASCII so \`set -u\` doesn't choke). After merge, the README's \`raw.githubusercontent.com/.../main/scripts/install.sh\` URL resolves and the legacy curl-pipe path keeps working alongside the new native installers. Future cleanup (deleting the curl-pipe scripts since the native installers are the recommended path) can be a follow-up commit. ## Test plan - [ ] After merge, build the macOS \`.pkg\` from \`installer/macos/build-pkg.sh\`, run on a clean Mac, confirm app installs and dashboard opens - [ ] Run \`installer/windows/Output/DaemoraSetup.exe\` on a clean Windows box, confirm same - [ ] Confirm browser tools are absent from main agent's tool list on a fresh install (PR #77 default) - [ ] Verify \`https://raw.githubusercontent.com/CodeAndCanvasLabs/Daemora/main/scripts/install.sh\` resolves
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.
Summary
Flip Playwright MCP's default `enabled` from `true` to `false`. Browser tools become opt-in — neither the main agent nor the browser-pilot crew sees `browser_navigate`, `browser_click`, `browser_screenshot`, etc. until the user explicitly enables the Playwright server from the MCP settings UI.
Why
The main agent shouldn't reach for browser tools unprompted. The intent is:
When the user enables Playwright via the UI, both the main agent and browser-pilot get the tools back simultaneously (current architecture is single shared MCP server, no per-crew scoping yet — that's a separate larger change tracked elsewhere).
Affected behaviour
Test plan