Browser login

Manual login (recommended)

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

OmeniaClaw controls a dedicated Chrome profile (named OmeniaClaw, orange-tinted UI). This is separate from your daily browser profile.

For agent browser tool calls:

• Default choice: the agent should use its isolated OmeniaClaw browser.
• Use profile="user" only when existing logged-in sessions matter and the user is at the computer to click/approve any attach prompt.
• If you have multiple user-browser profiles, specify the profile explicitly instead of guessing.

Two easy ways to access it:

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

OmeniaClaw browser startOmeniaClaw browser open https://x.com

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

X/Twitter: recommended flow

• 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 open the host browser yourself (CLI invocations always run against the host browser):

OmeniaClaw browser open https://x.com --browser-profile OmeniaClaw

The agent's browser tool calls can then target the host once sandbox.browser.allowHostControl: true is set. Alternatively, disable sandboxing for the agent that posts updates.

Related

• Browser
• Browser Linux troubleshooting
• Browser WSL2 troubleshooting