Surf CLI — Control Chrome for AI Agents (No MCP)

Practical Notes

• README quick start is a 4-step install: npm global install, load unpacked extension, surf install <extension-id>, then surf tab.list.
• README lists supported browsers: chrome, chromium, brave, edge, arc, helium (plus --browser all).

A Safe Integration Pattern for Agents

Browser control becomes risky when agents can navigate and click freely. Practical guardrails:

• Give the agent a “read-only” browsing phase first: list tabs, capture URLs, extract text.
• Use explicit allowlists for domains your agent is allowed to interact with.
• Treat extension/native host changes like code: update via PRs, not ad-hoc local edits.

Troubleshooting Checklist

• If the extension path changes, re-run surf extension-path and reload unpacked extension.
• If a package manager stores binaries in non-standard locations, the README documents env vars such as SURF_NODE_PATH / SURF_HOST_PATH / SURF_EXTENSION_PATH.

FAQ

Q: Is this MCP-based? A: The README positions Surf as a CLI + extension/native host flow; it emphasizes zero MCP server configuration.

Q: What’s the hardest step? A: Typically loading the unpacked extension and copying the extension ID for surf install.

Q: Can I use other browsers? A: Yes—README lists multiple browsers and shows --browser flags, including --browser all.