Summary

• build the event-driven capture WindowFilters once when the monitor loop starts
• reuse the cached filters for visual-change checks and full captures
• keep excluded SCK window IDs resolved freshly each check/capture so changing windows are still respected

Why

The ignore/include/window URL config is stable for an event-driven capture loop, but the loop rebuilt parsed WindowFilters on every visual check and every full capture. Caching the parsed filters removes repeated pattern parsing and URL lowercasing from the steady capture path without changing capture behavior.

Validation

• cargo fmt --package screenpipe-engine -- --check
• cargo test -p screenpipe-engine event_driven_capture --lib
• cargo check -p screenpipe-engine