Explorbot Setup

Install Explorbot into the user's project, connect a provider, teach it how to reach the app, and prove it with one navigation.

The config, the knowledge files, and the generated tests all land in the repo, so they are reviewed and versioned like the rest of the code. That is the point of installing locally.

To run Explorbot without installing it into the project, this is the wrong skill — [[explorbot-fundamentals]] covers that: npx, a provider, no project files.

Scope ends when npx explorbot navigate <path> exits 0 — exploring and testing belong to [[explorbot-fundamentals]].

1. Requirements

• Node ≥ 24 or Bun. If neither exists, stop — do not install a runtime.
• The generated config uses import, so package.json must be ESM. npm init -y produces CommonJS; if "type" is missing or "commonjs" in an existing file, ask before changing it, and write explorbot.config.mjs (passed as --config) if the user declines.
• Explorbot is for CRUD-heavy apps. Warn before installing if the target is a landing page, blog, CMS, or static site.

2. Install