docs: Rename to cloud browser, update Kernel links and descriptions

- Rename "Remote browser" to "Cloud browser" throughout
- Update connection methods to CDP, BiDi, and CUA API
- Update Kernel features to CAPTCHA solving, proxies, auth, observability
- Fix Kernel links from kernel.computer to kernel.sh
- Update description to focus on agent internet access

Author: beran-t

docs/use-cases/remote-browser.mdx

@@ -1,21 +1,21 @@
 ---
-title: "Remote browser"
-description: "Use Kernel cloud browsers with E2B sandboxes for web scraping, screenshots, and autonomous browsing agents."
+title: "Cloud browser"
+description: "Use Kernel cloud browsers with E2B sandboxes to give your agents access to the internet."
 icon: "globe"
 ---
 
 <Note>
-This guide covers **remote browsers** powered by [Kernel](https://www.kernel.computer/) — cloud Chromium instances your code controls via [CDP](https://chromedevtools.github.io/devtools-protocol/) or the [Kernel SDK](https://www.kernel.sh/docs/sdk/overview). For **local browser automation** using a virtual desktop, see [Computer use](/docs/use-cases/computer-use).
+This guide covers **cloud browsers** powered by [Kernel](https://www.kernel.sh/) — cloud Chromium instances your code controls via [CDP](https://chromedevtools.github.io/devtools-protocol/) or the [Kernel SDK](https://www.kernel.sh/docs/sdk/overview). For **local browser automation** using a virtual desktop, see [Computer use](/docs/use-cases/computer-use).
 </Note>
 
-Remote browsers run on Kernel's infrastructure, not inside your sandbox. Your agent connects to them over the network via Playwright or Puppeteer. This keeps sandboxes lightweight and lets you spin up many browsers in parallel.
+Cloud browsers run on Kernel's infrastructure, not inside your sandbox. Your agent connects to them over the network via CDP, BiDi, or their CUA API. This keeps sandboxes lightweight and lets you spin up many browsers in parallel.
 
-Kernel handles stealth mode, CAPTCHA solving, residential proxies, and persistent browser profiles out of the box.
+Kernel handles CAPTCHA solving, residential proxies, authentication, and observability out of the box.
 
 ## Prerequisites
 
 - An [E2B API key](https://e2b.dev/dashboard?tab=keys)
-- A [Kernel API key](https://www.kernel.computer/)
+- A [Kernel API key](https://www.kernel.sh/)
 - Python 3.10+ / Node.js 18+
 
 <CodeGroup>
@@ -42,7 +42,7 @@ E2B provides a pre-built sandbox template with the Kernel SDK and Playwright alr
 
 ## Examples
 
-Here are three common patterns for using remote browsers with E2B sandboxes.
+Here are three common patterns for using cloud browsers with E2B sandboxes.
 
 <CardGroup cols={3}>
   <Card title="Screenshot app endpoints" icon="camera" href="#screenshot-app-endpoints">
@@ -60,7 +60,7 @@ Here are three common patterns for using remote browsers with E2B sandboxes.
 
 ## Screenshot app endpoints
 
-Deploy a web app inside an E2B sandbox, get a public URL, then use a Kernel browser to screenshot every route.
+Deploy a web app inside an E2B sandbox, get a public URL, then use a Kernel cloud browser to screenshot every route.
 
 <Steps>
 <Step title="Create the sandbox and start your app">