Recent prompt runs
The landing view is a table of every prompt run for the project, newest first. One row per run, with:- ID — the run’s short id, with a copy button for the full id.
- Prompt Run — a sequential label (“Prompt Run 12”) counting from the project’s first run.
- Status — Running, Completed, Failed, Interrupted, or Cancelled.
- Trigger — Manual (you clicked Run Now) or Scheduled (a cadence fired it).
- Started and Ended — timestamps, with a relative time on hover.
- Duration — how long the run took.
- Platforms — the AI platforms the run covered, shown as logos.
- Report — a per-row PDF download, available once the run has completed.
Opening a run
Click a run to open it.- A completed run opens its dashboard — the full visibility view, scoped to that one run.
- A run that failed or was cancelled has no visibility numbers, so it opens on a per-run detail page instead: a per-platform breakdown of what succeeded, what failed, and why.
A run’s dashboard
Every run’s dashboard reads the same regardless of the run’s age. A small run-info header sits under the project title with the run’s id (and a copy button), its “Prompt Run” label, status, and date — plus an All runs link back to the list. A single run’s dashboard is read-only. You run and schedule from the run list, not from inside a specific run. What it shows:- Headline visibility score for your brand and each competitor.
- Per-topic and per-platform breakdowns.
- Trend lines on every score above. The trend spans the project’s full run history, not just the run you’re viewing.
- Click-through from any score into the prompts and citations behind it.
Filters
Within a run’s dashboard, filter by topic, platform, prompt attribute, date range, branded vs unbranded. Filter state lives in the URL, so a filtered view is shareable by link.Running prompts
Click Run Now at the top of the run list to kick off a run on demand. The button sends every active prompt to every active platform. The new run appears in the list immediately; open it and the numbers update live as platform responses come back, so the headline visibility, share of voice, and per-platform numbers shift while the run is in flight. Final numbers settle when the run completes. Scheduled cadence (daily, weekly, or monthly) is set in Settings. On-demand runs are independent of the schedule and can also be triggered via the REST API or MCP.Where the data comes from
See How OpenLens sources data.How outputs are produced
- Each run sends every active prompt to every active platform.
- Responses are parsed by Claude Haiku for brand mentions, citations, and response attributes (qualities discussed about a brand, each with a sentiment).
- Visibility scores are computed live from the parsed events. No pre-aggregated snapshot.
How to use it
- Pick a run from the list, then read the headline. Drill into per-platform to spot platforms that don’t know you.
- Trace a citation to see where models pull answers from for your space.
- For the interpretation layer (what each metric actually means, what to do about a result), see the Dashboard deep-dive.