Dia browser not recognized for meeting detection

Summary

Screenpipe's meeting detection doesn't recognize Dia (the browser from The Browser Company, makers of Arc) as a browser, so browser-based meetings (Google Meet, Slack huddles, Zoom web, etc.) running in Dia are never auto-detected.

Root cause

Browser windows are gated on the BROWSER_NAMES allowlist in crates/screenpipe-engine/src/meeting_watcher/shared/profiles.rs:

pub(crate) const BROWSER_NAMES: &[&str] = &[
    "google chrome",
    "arc",
    // ...
];

"dia" isn't in the list. is_browser_app() (in shared/ignore.rs) and the two inline BROWSER_NAMES.iter().any(|b| name_lower.contains(b)) checks in ui_scan/macos.rs all consult this constant, so a Dia window never gets classified as a browser — and its URL/title patterns are never consulted.

Dia is Chromium-based and behaves like Arc for meeting detection (tab URL not always exposed via AX, page title carries the meeting), so once it's recognized as a browser the existing URL/title matching takes over.

Fix

Add "dia" to BROWSER_NAMES:

"arc",
"dia",
"firefox",

is_browser_app uses a case-insensitive contains match, so this correctly matches the Dia app name. Extending browser_app_detection_is_case_insensitive in ui_scan/tests.rs to assert is_browser_app("Dia") covers it.

Related

• #6989 — Slack huddles in Arc not auto-detected (the title-pattern side of browser meeting detection). That fix and this one are independent but complementary for Dia users: Dia needs to be in the allowlist and (for Slack specifically) the title-pattern fix is needed.