Test / Smoke Test

Classification: browser-app/extension (Chrome)

Status: browser-app/extension (Chrome) Nanobrowser is a Chrome extension that turns the browser into an AI web agent. It has no CLI, no npm package, and no pip installable. It is installed from the Chrome Web Store or loaded manually as an unpacked extension. An LLM API key (OpenAI, Anthropic, Gemini, or compatible provider) is required to operate the extension. There is no subscription fee for the extension itself, but you pay for LLM API usage.

Install method: Install from the Chrome Web Store, or download the source and use "Load unpacked" in chrome://extensions/. Enter a valid LLM API key in the extension settings before use.

Cost/access: Free to install. Requires a paid LLM API key (OpenAI, Anthropic, etc.) to operate.

---

Why there is no CLI smoke test

Nanobrowser is a Chrome extension with no CLI, no npm package, and no --version flag. It cannot be smoke-tested from a terminal. The verification steps below confirm the extension is installed and operational inside Chrome.

Manual smoke test (takes under 2 minutes)

Step 1: Confirm the extension loaded

Open Chrome and navigate to:

chrome://extensions/

Expected: Nanobrowser appears in the list with the toggle set to On (blue). No error badge.

Step 2: Confirm the sidebar opens

Click the Nanobrowser icon in the Chrome toolbar.

Expected: A sidebar or popup opens showing a chat input field and a Settings link.

Step 3: Confirm API key is accepted

Open Settings inside the sidebar, enter a valid API key, and save.

Expected: No error toast. Key is saved (persists on reload).

Step 4: Run a minimal task

Navigate to https://example.com in Chrome, open the Nanobrowser sidebar, and type:

Tell me the main heading text on this page

Expected success output (paraphrased, will vary by LLM):

The main heading on this page is: "Example Domain"

The Planner identifies the task, the Navigator reads the page, and the Validator confirms the answer matches visible content. If all three agents complete without an error toast, the extension is fully operational.

What failure looks like

Symptom	Likely cause
Extension not visible in chrome://extensions	Install did not complete; repeat Load unpacked
Sidebar shows "Invalid API key"	Wrong key or wrong provider selected in Settings
Task spins indefinitely	LLM API rate limit or network issue; check your provider dashboard
"Navigator failed" error	Page blocked automation (e.g., bot-detection wall); try a simpler public page

Tested status

This smoke test is documented but not run automatically by this SOP site (the tool requires an interactive Chrome session). Set tested=false in any automated audit pipeline; mark tested=true only after manually completing Step 4 above.