> ## Documentation Index
> Fetch the complete documentation index at: https://docs.equa.cc/llms.txt
> Use this file to discover all available pages before exploring further.

# Browser login

# Browser login + X/Twitter posting

## Manual login (recommended)

When a site requires login, **sign in manually** in the **host** browser profile (the equabot browser).

Do **not** give the model your credentials. Automated logins often trigger anti‑bot defenses and can lock the account.

Back to the main browser docs: [Browser](/tools/browser).

## Which Chrome profile is used?

Equabot controls a **dedicated Chrome profile** (named `equabot`, orange‑tinted UI). This is separate from your daily browser profile.

Two easy ways to access it:

1. **Ask the agent to open the browser** and then log in yourself.
2. **Open it via CLI**:

```bash theme={null}
equabot browser start
equabot browser open https://x.com
```

If you have multiple profiles, pass `--browser-profile <name>` (the default is `equabot`).

## X/Twitter: recommended flow

* **Read/search/threads:** use the **bird** CLI skill (no browser, stable).
  * Repo: [https://github.com/steipete/bird](https://github.com/steipete/bird)
* **Post updates:** use the **host** browser (manual login).

## Sandboxing + host browser access

Sandboxed browser sessions are **more likely** to trigger bot detection. For X/Twitter (and other strict sites), prefer the **host** browser.

If the agent is sandboxed, the browser tool defaults to the sandbox. To allow host control:

```json5 theme={null}
{
  agents: {
    defaults: {
      sandbox: {
        mode: "non-main",
        browser: {
          allowHostControl: true
        }
      }
    }
  }
}
```

Then target the host browser:

```bash theme={null}
equabot browser open https://x.com --browser-profile equabot --target host
```

Or disable sandboxing for the agent that posts updates.