In Stage 1, below the computed styles panel, there’s a small text field labeled “Anything else?” It’s optional. Most diagnoses don’t need it. But when the problem has context that Lens can’t see from the CSS alone, this is where you put it.
What it’s for #
Use it for context that isn’t visible in the current state of the page:
- “Only happens on mobile.”
- “Only in Safari.”
- “Only on the checkout page, not the product page.”
- “Started after I updated the theme last week.”
- “The button is the right color in the page editor but wrong on the live site.”
These are things Lens genuinely can’t capture from the CSS state. A responsive layout problem only visible at mobile widths won’t be in a desktop Viewport capture. A Safari-specific rendering issue won’t show in Chrome. This field lets you add that context before the session record is written.
What it’s not for #
Don’t use it to describe what you can already see on the page. “The button is the wrong color” is information Lens already has from the capture. “The text isn’t centered” is visible in the computed styles. You don’t need to tell Lens what it can already read. Put the context here that Lens can’t get any other way.
Where this information goes #
What you type here gets stored in the session record and included in the developer handoff message on the Triage Page. If you end up handing this off to a developer, they’ll see your note alongside the CSS context, so they don’t have to ask follow-up questions about when or where the problem appears.
It doesn’t change the rule engine’s output. The engine works from CSS data, not from text descriptions. But it gives your developer context that makes the handoff complete rather than requiring another round of back-and-forth to establish the basics.
Character limit #
280 characters. Enough for a sentence or two of context. The character count appears below the field as you type.