Skip to content

Cold Turkey kills browsers without Cold Turkey extension installed & configured #9

@adamlogan

Description

@adamlogan

I'm running into an issue where cold turkey pops up into the foreground when this MCP service executes a search. Cold Turkey nags me about installing the cold turkey extension and enabling an option in the extension to allow the extension to operate in incognito/private windows. This is not an option I can disable, so, this is problematic. In Cold Turkey I have set 99 seconds grace period to install / enable and configure the Cold Turkey Extension. I would think that would be enough time for the MCP service to get in complete a search and get out but apparently some searches are taking so long that Cold Turkey does kill the app before the search completes.

I've managed to find the GUI enabled apps and have installed the Cold Turkey extension/addon for those, yet Cold Turkey still isn't satisfied I'm emailing the dev about that.

Am I correct that this MCP server only uses the headless browsers? I looked in the Dist directory and looked through some of the code. I am a baby at coding so I'm not adept at fully understanding what I'm reading or modifying it to suit. What I did glean from looking is the service round-robins the headless browsers that it detects playwright as serving, is that accurate?

Would appreciate help on this issue.

For context, I am on MacOS.

web-search-mcp-v0.3.2

MacBook Pro
14-inch, 2021
Chip Apple M1 Pro
Memory 32 GB
macOS Sequoia 15.6.1

Cold Turkey Version 4.7 (4.7)

Let me know if you need any other info.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions