# Claude Code Chrome and computer use

> Claude Code: Browser integration, macOS computer use, permissions, safety boundaries, caching, and Passion8 limitations.

URL: https://docs.passion8.cc/en/docs/claude-code/chrome-computer-use
Language: en
Publisher: Passion8

| Capability | Target | Use |
| --- | --- | --- |
| Chrome integration | Chrome/Edge tabs | Web testing, forms, console, signed-in pages |
| Computer use | macOS applications | Native apps, simulators, GUI-only tools |

These broad interfaces are slower and more sensitive than structured tools. Prefer API/MCP, then shell, then browser, and finally desktop control.

## Chrome integration

The Claude in Chrome extension connects tabs, reading, clicking, typing, console inspection, screenshots, and recording to Claude Code.

```bash
claude --chrome
```

In-session:

```text
/chrome
```

| Use | Example |
| --- | --- |
| Local app tests | Open localhost:3000, submit a form, inspect errors |
| Console debugging | Inspect errors, warnings, network failures |
| Design checks | Layout, spacing, responsive behavior |
| Signed-in websites | Existing Gmail, Notion, Docs sessions |
| Extraction | Save structured page data as CSV |
| Demonstrations | Record an interaction GIF |

## Chrome requirements

| Item | Requirement |
| --- | --- |
| Browser | Chrome or Edge |
| Extension | Claude in Chrome |
| CLI | A supported recent version |
| Account | Supported direct Anthropic plan |
| Unsupported combinations | Brave, Arc, WSL, provider-only setups where excluded |

In plan mode, reads can proceed without confirmation; state-changing actions such as navigation, clicks, typing, tabs, and saving screenshots require appropriate approval.

## Computer use

The built-in MCP server lets Claude operate macOS applications and inspect the screen.

| Task | Example |
| --- | --- |
| Native application validation | Build Swift app and exercise tabs |
| Electron/onboarding | Walk the flow and capture errors |
| Visual reproduction | Resize until a modal clips, then repair CSS |
| Simulators | Exercise iOS onboarding |
| GUI-only tools | Device panels, design software, internal desktop apps |

Enable it:

1. Open /mcp in an interactive session.
2. Enable computer-use.
3. Grant macOS Accessibility and Screen Recording when requested.
4. Approve each application when first controlled in the session.




This controls the real desktop, not a Bash sandbox. Terminal, IDE, Finder, and System Settings deserve particular care; grant access only for the intended task.




## Boundaries

| Mechanism | Effect |
| --- | --- |
| Per-app approval | Only approved applications are controllable |
| High-risk app warnings | Extra notice for terminal/IDE/files/system settings |
| Own terminal excluded | Avoids feeding the agent's terminal output back as screen content |
| Global Esc stop | Stop the current action |
| Single-session lock | One controlling session per machine |

Browser and transaction applications can have stricter controls. Payments, deletions, messages, and form submissions should have an explicit plan and authorization.

## Passion8 limitations

These are supported official-account integrations, not generic model-gateway features.

| Scenario | Result |
| --- | --- |
| Passion8 URL/token only | Do not assume official browser/desktop tools become available |
| Also signed in to claude.ai | Check feature eligibility and actual request routing separately |
| Local web verification | Use Playwright, browser MCP, or manual screenshots |
| Organization disabled tools | Local settings cannot override policy |

For ordinary responsive checks, use browser developer tools, Playwright, or a phone on the local network rather than enabling desktop control unnecessarily.

## Context and caching

| Action | Effect |
| --- | --- |
| Start with --chrome | Loads browser definitions; prefix differs from an ordinary session |
| Screenshots, DOM, console | Adds tool output to history |
| Recording/large logs | Can expand context significantly |
| Desktop screenshots | Image input adds cost versus plain text |
| Return to shell | Does not remove observations already in history |

Use browser tools where needed, then preserve concise findings instead of entire DOM/log dumps.

## Troubleshooting

| Problem | Action |
| --- | --- |
| Extension not connected | Enable it, restart browser, reconnect with /chrome |
| Browser unresponsive | Dismiss blocking alert/confirm/prompt dialogs |
| Receiving end does not exist | Reconnect a sleeping extension worker |
| computer-use missing | Check macOS, plan, CLI version, interactive mode |
| Repeated macOS prompts | Restart terminal/Claude after granting screen access |
| Another session holds lock | Exit the other controlling session |

## Official references

- [Chrome](https://code.claude.com/en/docs/en/chrome.md)
- [Computer use](https://code.claude.com/en/docs/en/computer-use.md)
- [Feature availability](https://code.claude.com/en/docs/en/feature-availability.md)
- [Permissions](https://code.claude.com/en/docs/en/permissions.md)
- [Data and privacy](https://code.claude.com/en/docs/en/data-usage.md)