@leadbay/mcp 0.24.1 → 0.25.0

package/CHANGELOG.md

@@ -1,5 +1,23 @@
 # Changelog — @leadbay/mcp
 
+## 0.25.0 — 2026-07-13
+
+Add `leadbay_set_telemetry` — an in-product control to enable, disable, or check
+product-usage telemetry (product#3879). Telemetry stays ON by default (opt-out).
+The preference is stored per-user on the Leadbay account (via `POST
+/users/telemetry`, read from `GET /users/me`). On the **hosted/web connector** a
+user who opts out has their telemetry suppressed per-request. A **local/stdio
+install** decides telemetry at process start from `LEADBAY_TELEMETRY_ENABLED` and
+does NOT consult the account flag, so local opt-out also requires setting that
+env var (the tool's copy says so). Requires the backend `telemetry_enabled`
+field (leadbay/backend) + api-specs contract.
+
+## 0.24.2 — 2026-07-13
+
+Release bump to publish a fresh hosted HTTP-server image carrying the 0.24.1
+telemetry fix (the hosted `mcp.leadbay.app` endpoint deploys from the release
+image, separately from npm). No code changes.
+
 ## 0.24.1 — 2026-07-10
 
 Fix PostHog tool-call events silently dropped (product#3876). The hosted HTTP

package/README.md

@@ -609,7 +609,7 @@ The agent calls `leadbay_import_leads({ domains: [...] })`, gets back `{ leads:
 
 Suitable for **occasional automation**. **Not** suitable for high-cadence (>5 calls/day) — the right primitive is a clean async-import-with-crawl backend endpoint, tracked as a follow-up in `leadbay/backend`.
 
-**Limitation:** the wedge maps domains to leads the crawler already knows. Uncrawled domains land in `not_imported` with `reason: "uncrawled"` — the tool does **not** create new leads for unknown websites; the caller decides what to do (skip, queue for the backend follow-up, etc.).
+**`uncrawled` rows are pending, not failed.** The wedge matches domains the crawler already knows. A domain the crawler hasn't indexed yet lands in `not_imported` with `reason: "uncrawled"` — the import still completes, and Leadbay then crawls that domain in the background and adds the lead asynchronously (a *late import*), so those rows commonly resolve on their own within minutes to hours. Those late-added leads populate in the user's Leadbay account as the crawl completes. `leadbay_import_status` refreshes status/progress only (not the added leads), and `leadbay_pull_leads` reads the active lens's wishlist (so an imported lead outside that lens may not appear). For one named company, `leadbay_research_lead_by_name_fuzzy` searches across the visible corpus (not lens-scoped) and can surface it once crawled; for a bulk refresh, re-run the same import later to re-reconcile the now-crawled domains. `uncrawled` is **not** a failure and **not** a bad website — never surface it to the user as one.
 
 ### Importing + qualifying in one verb (0.5.0)
 
@@ -665,7 +665,9 @@ After your first authenticated call, your PostHog `distinctId` is set to your Le
 
 **Errors to Sentry**: only unexpected throws (TypeError, network failures, parse bugs). Expected business outcomes — quota walls, missing resources, auth expiry, billing suspension — stay in PostHog only.
 
-**Opt out** — `leadbay-mcp install` writes `LEADBAY_TELEMETRY_ENABLED=true` into your MCP client's env block by default. Most clients (Claude Desktop, Cursor) render env-var booleans as a toggle in their settings UI, so you can flip it without editing the file. To opt out at install time, pass `--no-telemetry`; to opt out manually, flip the env value to `"false"`:
+**Opt out** — the simplest way is to just ask the agent: "turn off telemetry" (or "is telemetry on?"). That calls the `leadbay_set_telemetry` tool, which stores your choice on your Leadbay account. The **hosted/web connector** honors it per-request (there's no local config to edit there). On a **local install** the server decides telemetry at startup from `LEADBAY_TELEMETRY_ENABLED` and does not read the account flag, so also set `LEADBAY_TELEMETRY_ENABLED=false` (below) to stop events locally.
+
+You can also opt out via config: `leadbay-mcp install` writes `LEADBAY_TELEMETRY_ENABLED=true` into your MCP client's env block by default. Most clients (Claude Desktop, Cursor) render env-var booleans as a toggle in their settings UI, so you can flip it without editing the file. To opt out at install time, pass `--no-telemetry`; to opt out manually, flip the env value to `"false"`:
 
 ```jsonc
 {