# Browser Login Documentation

## Key Recommendations

The documentation emphasizes that **manual login is the recommended approach** when sites require authentication. Rather than providing credentials to the model, users should sign in manually in the host browser profile (the openclaw browser), as automated logins frequently trigger security defenses.

## Chrome Profile Details

OpenClaw operates through a dedicated Chrome profile called `openclaw` with distinctive orange-tinted styling, kept separate from personal browser profiles. Users can access it either by requesting the agent to launch the browser or through command-line tools.

## X/Twitter Best Practices

For social media interactions, the guidance suggests using the CLI-based bird tool for reading and searching content, while reserving the host browser for posting activities that require authentication.

## Sandboxing Configuration

When agents operate in sandboxed environments, bot detection risks increase. The documentation provides configuration options to enable host browser control, allowing agents to access the main browser while maintaining sandboxing for other functions.

The core principle throughout: **prioritize host browser access over automated credentials** to avoid triggering anti-bot systems.
