The agent that turns websites into APIs!
---
title: Agent configuration
description: Configure the AI agent that drives the browser in agent mode.
---
Agent mode runs an AI loop. **`auto`** and **`chrome-mcp`** attach browser automation via **MCP**. **`agent-browser`** instead delegates browsing to the **[Vercel agent-browser CLI](https://github.com/vercel-labs/agent-browser)**; Reverse API Engineer looks for `agent-browser` on `PATH`, otherwise runs **`npm install -g …`** (using the same pin as config), surfaces a console notice, verifies **`--help`**, and only falls back to **`npx -y …`** if npm cannot complete the install.
## Agent providers
### `auto` (default)
Playwright MCP browser automation with real-time reverse engineering. The
configured SDK uses Playwright via MCP to control Chromium, capturing the HAR
as it goes. Add `--headless` when running without a display.
Works with the Claude SDK (default) or the OpenCode SDK. Pick whichever
you've already configured. Copilot and Cursor SDK backends are also supported
when their optional dependencies and credentials are installed.
### `chrome-mcp`
Drives your **real Chrome browser** via
[Chrome DevTools MCP](https://www.npmjs.com/package/chrome-devtools-mcp). Pick
this when you need existing sessions, cookies, or auth from your daily Chrome
profile.
**Requirements:**
- Chrome 146+
- Node.js 20.19+
- Auto-connect enabled at `chrome://inspect/#remote-debugging`
### `agent-browser`
Uses **[Vercel agent-browser](https://github.com/vercel-labs/agent-browser)** as a standalone CLI—not a Reverse API Engineer MCP shim.
After the CLI is available, Reverse API Engineer embeds the resolved shell prefix in the user prompt (**`agent-browser …`** vs **`npx -y <pin> …`**) and validates with **`--help`**. Prompts steer the model through **`skills get core --full`** (retry with **`skills list`** / matching bundles when operators name a cloud/runtime backend via `agent_browser_notes`). Claude SDK runs widen the tool allow-list for Bash-heavy flows; OpenCode/Copilot/Cursor omit Reverse API Engineer browser MCP registration for `agent-browser` and rely on their own shell primitives.
Suggested JSON knobs:
```json
{
"agent_provider": "agent-browser",
"agent_browser_npx_package": "agent-browser@0",
"agent_browser_notes": "Optional operator guidance (AgentCore endpoints, corp proxy tweaks, sandbox IDs, …)"
}
```
You can alternatively drive the same knobs with **`RAE_AGENT_BROWSER_PACKAGE`** or **`RAE_AGENT_BROWSER_NOTES`**.
First-time infra still needs Chromium bits just like upstream docs describe (`agent-browser install`, `--with-deps` on trimmed Linux VMs).
## How to switch providers
In the CLI:
```text
/settings then "agent provider"
```
Or edit `~/.reverse-api/config.json`:
```json
{
"agent_provider": "chrome-mcp"
}
```
## Reasoning model
The agent's reasoning model is the same as your configured SDK model. See
[Model selection](/docs/configuration/models) to change it independently
from the SDK.