[Feature]: Optimize Default Web Strategy: Make WebSearch/WebFetch Default, Keep browser_use Optional

Currently, when Copaw needs to access the internet, it defaults to invoking browser_use (launching a full Chromium browser). This causes severe resource overhead; Chromium can easily consume hundreds of MBs of RAM, which frequently crashes or freezes low-memory servers (e.g., 2GB RAM VPS instances).

While it is possible to manually disable browser_use in the settings right now, doing so completely strips the Agent of any basic web search/fetch capabilities, which is not a reasonable default behavior.

Proposed Solution:
I suggest adjusting Copaw’s tool priority and default behavior as follows:

Default to Lightweight Tools: Make WebSearch (calling search APIs) and WebFetch (lightweight HTML-to-text scraping) the default methods for internet access. This covers 90% of use cases for retrieving web text, with minimal memory footprint (just a few MBs).
Make browser_use an Opt-in Feature: Full browser automation should be an advanced, non-default feature.
Enable Third-Party Extensions: If a user on a resource-constrained machine has turned off browser_use but encounters a complex dynamic webpage that requires a real browser, they should be able to bridge this gap by integrating third-party solutions (like a remote Playwright MCP Server) via MCP or Skills.
Benefits:

Lightweight Out-of-the-Box: Most users get immediate web access without risking machine crashes from hidden background processes.
Flexible Control: Power users or those with sufficient hardware resources can manually enable browser_use, or route browser tasks to remote environments via MCP.