Hello @rstanislav! I'm a friendly bot here to help you solve bugs, answer questions, and assist you in becoming a contributor. I'll be here while you wait for a human maintainer. How can I assist you today?

The error you're encountering is related to running a browser automation tool (like Puppeteer) as root without the --no-sandbox flag. This is a known issue with Chromium-based browsers, which require the --no-sandbox flag when running as root to avoid security restrictions.

Unfortunately, I couldn't find any specific workarounds or configurations in the Roo Code repository for running the application with the --no-sandbox flag ^[1]. You might need to modify your setup to include this flag when launching the browser in your environment.

If you haven't already, try adding the --no-sandbox flag to your Puppeteer launch configuration. This should help bypass the restriction and allow the fetch operation to proceed.

To continue talking to Dosu, mention @dosu.

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

Can you please provide detailed steps to repro?

To reproduce you need to connect to any remote host as root in vscode (using official remote-ssh plugin), and in roocode include any web page link (with @), as a result there will be fail:

Error fetching content: Failed to launch the browser process! undefined
[3114556:3114556:0416/031730.132271:ERROR:content/browser/zygote_host/zygote_host_impl_linux.cc:105] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.

I left this comment on the test PR but I think it is relevant here as well:

This is too risky. Running Chrome without sandbox as root means any malicious website could take over the entire system.

The real problem is running Roo Code/VSCode as root in the first place. We shouldn't enable bad security practices. Instead, users should create a regular user account for development and only use sudo when absolutely necessary.

If we really need to support running Roo Code as root, at least make it opt-in with a big warning about the security risks. But honestly, we should just tell people to stop running Roo Code as root and help them set up a proper non-root environment instead.

Let's not make it easier for people to shoot themselves in the foot.

This issue will be closed to prevent others to try and "fix it" the same way.