Skip to main content

โ€‹
Browser login + X/Twitter posting

When a site requires login, sign in manually in the host browser profile (the openclaw 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.

โ€‹
Which Chrome profile is used?

OpenClaw controls a dedicated Chrome profile (named openclaw, 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:
openclaw browser start
openclaw browser open https://x.com
If you have multiple profiles, pass --browser-profile <name> (the default is openclaw).
  • Read/search/threads: use the host browser (manual login).
  • 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: 
{
  agents: {
    defaults: {
      sandbox: {
        mode: "non-main",
        browser: {
          allowHostControl: true,
        },
      },
    },
  },
}
Then target the host browser: 
openclaw browser open https://x.com --browser-profile openclaw --target host
Or disable sandboxing for the agent that posts updates.