AI Agent Cloud Browser Infrastructure

Elastic cloud browsers for high-frequency agent work

Lexmount turns browsers into on-demand cloud resources. Agents can create, connect to, observe, and replay browser work through one control plane, so web tasks can scale beyond local hardware limits.

Quick start Open consoleRead docs

Agent

Browser CLI agent prompt

Choose the agent you use, then copy the matching setup prompt for Lexmount Browser.

Use Lexmount Browser through browser-cli for remote browser work.

Goal:
- Prefer browser-cli commands over handwritten Playwright.
- If Lexmount credentials are missing, guide me through browser-cli auth login.
- Never ask me to paste API keys or full direct browser URLs into chat.
- API keys must not appear in localhost callback URLs; browser-cli exchanges a one-time code with PKCE.

Official site:
- Lexmount Browser console: https://browser.lexmount.cn
- Use it to sign in, register, authorize CLI access, and manage browser projects.

Install:
1. Check whether browser-cli is already installed: browser-cli --version
2. If browser-cli is missing and uv is missing, install uv:
   curl -LsSf https://astral.sh/uv/install.sh | sh
3. Install or update browser-cli to 0.3.8 or newer:
   uv tool install --force git+https://github.com/lexmount/browser-cli.git
4. Install or update the packaged Codex skill:
   browser-cli skill status
   browser-cli skill install --force
   browser-cli skill status
5. Verify installation:
   browser-cli --version
   browser-cli version

Connect:
1. Run: browser-cli auth status
2. If credentials are missing or unusable, run:
   browser-cli auth login --open --connect-base-url https://browser.lexmount.cn --client-name Codex
3. Complete the https://browser.lexmount.cn Connect from Agent flow in the opened browser.
4. Confirm auth login reports authenticated=true or credentials_saved=true.
5. After login succeeds, run: browser-cli doctor --json

Installation result:
- browser-cli is installed or updated.
- The Lexmount Browser Codex skill is installed under the Codex skills directory.
- The API credential is saved by browser-cli auth login; do not paste API keys into chat.

Cleanup:
- To remove saved local browser-cli credentials, run:
  browser-cli auth clear-credentials
- If that command returns unset_env_commands, run those commands in the parent shell too.
- Use browser-cli auth logout --revoke only when you intentionally want remote token revocation.

Use:
- Create browser sessions with browser-cli session create.
- Inspect first with browser-cli action observe or browser-cli action interactive-snapshot.
- Prefer semantic actions such as click-role, click-text, fill-label, wait-role, get-text-role, exists-role, hover-role, press-role, and screenshots.
- If a page requires login, captcha, SMS verification, or QR-code scanning, do not just say that it is blocked. Get the current session inspect_url / inspectUrl from the session metadata or latest command output, open that URL with the available local/embedded browser, and ask the user to complete the handoff there. If no inspect URL is available, report that blocker explicitly.
- Do not paste full direct browser connect URLs into chat. Use inspect_url / inspectUrl for human handoff; use --reveal-connect-url only in a trusted local terminal when explicitly needed for debugging.
- For repeatable tasks, inspect browser-cli commands --workflow case_file_task and use case scaffold/run.
- Close temporary sessions unless I explicitly ask to keep them open.

WebFetch agent prompt

Choose the agent you use, then copy the matching setup prompt for WebFetch.

Use Lexmount WebFetch through webfetch-cli when the task only needs page extraction or DOM dump.

Goal:
- Prefer webfetch-cli for lightweight page extraction instead of opening a remote browser session.
- Use browser-cli only when interactive browser state, clicking, screenshots, or live session control is needed.
- Never ask me to paste API keys into chat.
- API keys must not appear in localhost callback URLs; webfetch-cli exchanges a one-time code with PKCE.

Official site:
- Lexmount Browser console: https://browser.lexmount.cn
- Use it to sign in, register, authorize CLI access, and manage WebFetch project credentials.

Install:
1. Check whether webfetch-cli is already installed: webfetch-cli --version
2. If webfetch-cli is missing and uv is missing, install uv:
   curl -LsSf https://astral.sh/uv/install.sh | sh
3. Install or update webfetch-cli to 0.1.5 or newer:
   uv tool install --force git+https://github.com/lexmount/webfetch-cli.git
4. Install or update the packaged Codex skill:
   webfetch-cli skill status
   webfetch-cli skill install --force
   webfetch-cli skill status
5. Verify installation:
   webfetch-cli --version
   webfetch-cli capabilities --json

Connect:
1. Run: webfetch-cli auth status
2. If credentials are missing or unusable, run:
   webfetch-cli auth login --open --connect-base-url https://browser.lexmount.cn --client-name Codex
3. Complete the https://browser.lexmount.cn Connect from Agent flow in the opened browser.
4. Confirm auth login reports authenticated=true or credentials_saved=true.
5. After login succeeds, run: webfetch-cli doctor --json

Installation result:
- webfetch-cli is installed or updated.
- The Lexmount WebFetch Codex skill is installed under the Codex skills directory.
- The API credential is saved by webfetch-cli auth login; do not paste API keys into chat.

Use:
- Extract structured page content with:
  webfetch-cli extract --url https://example.com
- Dump rendered DOM with:
  webfetch-cli dump-dom --url https://example.com
- If extract needs an existing DOM snapshot, use:
  webfetch-cli extract --dom-id <dom_id>
- Use --format json-full only when debugging full API responses.

Cleanup:
- To remove saved local webfetch-cli credentials, run:
  webfetch-cli auth clear-credentials

ChatGPT MCP endpoints

Use the Browser MCP or WebFetch MCP endpoint that matches this site.

Browser MCP

https://browser.lexmount.cn/chatgpt-app/mcp

WebFetch MCP

https://browser.lexmount.cn/chatgpt-app-webfetch/mcp

Elastic browser pool

On demand

Remote View

Human takeover

Parallel sessions

Scale out

Recording

Replayable

Agent Browser Cloud

Cloud browsers, ready whenever agents need them

Create on demand. Run in parallel. Observe in one place.

Agent request

Natural language or automation code asks for web access.

Lexmount control plane

Creates instances, manages credentials, exposes connection entries.

Cloud browser pool

Runs multiple browser instances with observation and recording.

Control Plane

Create, access, observe, and trace in one place

Lexmount centralizes the browser lifecycle, identity credentials, connection information, remote View, and execution recordings into one clean operating surface.

Lifecycle management

Create, run, close, and recycle browser instances.

Credential and connection entry

Keep API access and browser connection details together.

Remote View

Open a cloud browser screen and take over when needed.

Recording replay

Preserve task execution for review and troubleshooting.

Agent Workflow

Many browsers, one observable execution loop

When an agent needs to inspect many web sources, Lexmount can provide multiple browser instances in parallel and keep every running screen visible for monitoring.

Multiple Lexmount cloud browser views monitored together

Task intake

The user describes a goal in natural language.

Browser execution

The agent opens cloud browsers and performs web work.

Live observation

Operators can monitor running browser screens.

Result and replay

Outputs and recordings close the review loop.

Give agents more browser capacity without local hardware limits

Use Lexmount to scale browser execution from a local bottleneck into an elastic cloud capability that is easier to create, observe, and manage.

Quick start Open console Explore documentation

Elastic cloud browsers for high-frequency agent work

Lexmount turns browsers into on-demand cloud resources. Agents can create, connect to, observe, and replay browser work through one control plane, so web tasks can scale beyond local hardware limits.

Use Lexmount Browser through browser-cli for remote browser work. Goal: - Prefer browser-cli commands over handwritten Playwright. - If Lexmount credentials are missing, guide me through browser-cli auth login. - Never ask me to paste API keys or full direct browser URLs into chat. - API keys must not appear in localhost callback URLs; browser-cli exchanges a one-time code with PKCE. Official site: - Lexmount Browser console: https://browser.lexmount.cn - Use it to sign in, register, authorize CLI access, and manage browser projects. Install: 1. Check whether browser-cli is already installed: browser-cli --version 2. If browser-cli is missing and uv is missing, install uv: curl -LsSf https://astral.sh/uv/install.sh | sh 3. Install or update browser-cli to 0.3.8 or newer: uv tool install --force git+https://github.com/lexmount/browser-cli.git 4. Install or update the packaged Codex skill: browser-cli skill status browser-cli skill install --force browser-cli skill status 5. Verify installation: browser-cli --version browser-cli version Connect: 1. Run: browser-cli auth status 2. If credentials are missing or unusable, run: browser-cli auth login --open --connect-base-url https://browser.lexmount.cn --client-name Codex 3. Complete the https://browser.lexmount.cn Connect from Agent flow in the opened browser. 4. Confirm auth login reports authenticated=true or credentials_saved=true. 5. After login succeeds, run: browser-cli doctor --json Installation result: - browser-cli is installed or updated. - The Lexmount Browser Codex skill is installed under the Codex skills directory. - The API credential is saved by browser-cli auth login; do not paste API keys into chat. Cleanup: - To remove saved local browser-cli credentials, run: browser-cli auth clear-credentials - If that command returns unset_env_commands, run those commands in the parent shell too. - Use browser-cli auth logout --revoke only when you intentionally want remote token revocation. Use: - Create browser sessions with browser-cli session create. - Inspect first with browser-cli action observe or browser-cli action interactive-snapshot. - Prefer semantic actions such as click-role, click-text, fill-label, wait-role, get-text-role, exists-role, hover-role, press-role, and screenshots. - If a page requires login, captcha, SMS verification, or QR-code scanning, do not just say that it is blocked. Get the current session inspect_url / inspectUrl from the session metadata or latest command output, open that URL with the available local/embedded browser, and ask the user to complete the handoff there. If no inspect URL is available, report that blocker explicitly. - Do not paste full direct browser connect URLs into chat. Use inspect_url / inspectUrl for human handoff; use --reveal-connect-url only in a trusted local terminal when explicitly needed for debugging. - For repeatable tasks, inspect browser-cli commands --workflow case_file_task and use case scaffold/run. - Close temporary sessions unless I explicitly ask to keep them open.

Use Lexmount WebFetch through webfetch-cli when the task only needs page extraction or DOM dump. Goal: - Prefer webfetch-cli for lightweight page extraction instead of opening a remote browser session. - Use browser-cli only when interactive browser state, clicking, screenshots, or live session control is needed. - Never ask me to paste API keys into chat. - API keys must not appear in localhost callback URLs; webfetch-cli exchanges a one-time code with PKCE. Official site: - Lexmount Browser console: https://browser.lexmount.cn - Use it to sign in, register, authorize CLI access, and manage WebFetch project credentials. Install: 1. Check whether webfetch-cli is already installed: webfetch-cli --version 2. If webfetch-cli is missing and uv is missing, install uv: curl -LsSf https://astral.sh/uv/install.sh | sh 3. Install or update webfetch-cli to 0.1.5 or newer: uv tool install --force git+https://github.com/lexmount/webfetch-cli.git 4. Install or update the packaged Codex skill: webfetch-cli skill status webfetch-cli skill install --force webfetch-cli skill status 5. Verify installation: webfetch-cli --version webfetch-cli capabilities --json Connect: 1. Run: webfetch-cli auth status 2. If credentials are missing or unusable, run: webfetch-cli auth login --open --connect-base-url https://browser.lexmount.cn --client-name Codex 3. Complete the https://browser.lexmount.cn Connect from Agent flow in the opened browser. 4. Confirm auth login reports authenticated=true or credentials_saved=true. 5. After login succeeds, run: webfetch-cli doctor --json Installation result: - webfetch-cli is installed or updated. - The Lexmount WebFetch Codex skill is installed under the Codex skills directory. - The API credential is saved by webfetch-cli auth login; do not paste API keys into chat. Use: - Extract structured page content with: webfetch-cli extract --url https://example.com - Dump rendered DOM with: webfetch-cli dump-dom --url https://example.com - If extract needs an existing DOM snapshot, use: webfetch-cli extract --dom-id <dom_id> - Use --format json-full only when debugging full API responses. Cleanup: - To remove saved local webfetch-cli credentials, run: webfetch-cli auth clear-credentials