refactor(ui): clarify browser automation setting

Generated-By: PostHog Code
Task-Id: 18a0ed17-2c63-4288-98b3-65563803ac72

Author: richardsolomou

docs/BROWSER-USE.md

@@ -1,21 +1,21 @@
 <!-- markdownlint-disable MD013 -->
 
-# Browser use
+# Browser automation
 
 PostHog Code can give local agent sessions browser automation tools through an isolated Playwright MCP server.
 
 ## Enable it
 
 1. Install Google Chrome.
 2. Open **Settings → Advanced**.
-3. Enable **Browser use**.
+3. Enable **Browser automation**.
 4. Start a new local session.
 
 The setting applies when a session starts. Existing sessions are unchanged.
 
 ## Behavior
 
-- Browser use is opt-in and disabled by default.
+- Browser automation is opt-in and disabled by default.
 - It is available only to local sessions.
 - Each session launches an isolated Chrome profile, so it does not inherit cookies or logins from the user's normal browser profile.
 - Tool calls and screenshots use the existing MCP tool-call pipeline.

packages/ui/src/features/settings/sections/AdvancedSettings.tsx

@@ -93,7 +93,7 @@ export function AdvancedSettings() {
         </Flex>
       </SettingRow>
       <SettingRow
-        label="Browser use"
+        label="Browser automation"
         description="Let local agent sessions launch an isolated Google Chrome window and interact with websites. Experimental; requires Chrome to be installed"
       >
         <Switch checked={browserUse} onCheckedChange={setBrowserUse} size="1" />