Home
Release · v0.2.0 · June 1, 2026

Durable prompt runs and sharper brand detection.

This release rebuilds the engine behind prompt runs so they survive restarts and deploys without dropping or duplicating prompts, sharpens how we detect your brand and competitors, and adds alias management to project settings.

New

Durable, crash-safe prompt runs

We rebuilt how a prompt run executes. Each run is now tracked task-by-task in the database rather than only in memory, so a run keeps a complete, accurate record of which prompts and platforms it covers even if the server restarts mid-run (which happens routinely on every deploy).

  • No more dropped or duplicated prompts. If a run is interrupted, it resumes from exactly where it left off instead of re-running work it already finished or silently skipping work it hadn't reached.
  • Self-recovering runs. A run that gets stranded by a server restart is now detected and driven to completion on its own, instead of blocking that project's future scheduled runs until someone notices. Scheduled reports are far less likely to show a gap.

Brand alias management

You can now edit the list of aliases for each brand directly from project settings — the trade names, initialisms, and short forms a brand is known by. OpenLens uses that list when deciding whether a mention in an AI answer is really your brand (or a competitor), so keeping it accurate directly improves your numbers.

Improved

More accurate brand detection

Brand matching now records which alias triggered each mention, so a mention is tied to the exact name it matched on. That makes detection easier to audit and tightens the line between a real mention and a coincidental substring.

As before, historical reports are not auto-corrected — they reflect the detection logic that was live when the run happened. Run a fresh scan if you want a project re-scored against the latest logic.

More complete answer coverage

  • Google AI Overview retries. When a search doesn't surface an AI Overview on the first try, OpenLens now retries before recording it as absent, so transient misses don't understate your visibility.
  • Consistent outcome recording. Answers from every platform now consistently record whether they returned content, so success and no-content cases are reported accurately across all engines.

For API and MCP users

No breaking changes for API or MCP integrations in this release. No endpoints or MCP tools were renamed or removed, and no request or response shapes changed in a way that requires you to update an existing integration.

Known issues

Grok coverage is temporarily unavailable. Grok has moved its responses behind a paywall, which has taken our Grok scraper offline. Until we restore it, prompt runs with Grok enabled will complete every other platform normally but will not return Grok results. We're actively working on a fix.

If Grok is a critical platform for your reporting, reach out and we'll let you know as soon as coverage is back.

Questions?

If something broke, looks wrong, or you want a project re-scored against the latest brand-detection logic, email [email protected].