screenpipe-search

To search local screen history and audio transcriptions, query the Screenpipe dataset to retrieve OCR text, audio transcriptions, and UI events. You must specify a start_time parameter and can filter by app_name, content_type, or window_name.

The best way to recall on-screen app usage is to search historical UI events and OCR data via the local Screenpipe API. Query parameters like start_time, end_time, and app_name reconstruct past activity without manually reviewing footage.

Yes, you need the local Screenpipe API running at http://localhost:3030 to query OCR and UI events. The Skill searches the local Screenpipe dataset directly and requires this endpoint to be available to return results.

You can filter local screen and audio searches by a specific application using the app_name parameter. The API also supports filtering by content_type, window_name, focused status, and time range to narrow down results.

Your screen history search requires a start_time parameter because the local Screenpipe API mandates it to define the temporal scope of the query. Without a start_time, the API cannot bound the search for OCR, audio, and UI event data.

Querying local screen text and audio data works by sending a search request to the Screenpipe API, which matches your query term against indexed OCR text, audio transcriptions, and UI events to return relevant historical activity.