> ## Documentation Index
> Fetch the complete documentation index at: https://docs.screenpipe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitor one approved window or website

> Create a narrow local Screenpipe monitor for one approved app, window, or website with recording filters, explicit no-data states, and reviewed alerts.

Focused monitoring is useful for a build console, support queue, dashboard, or other surface you are authorized to observe. Do not use it for covert employee monitoring or to capture unrelated windows “just in case.”

```mermaid theme={"system"}
flowchart TD
    A["approved surface and schedule"] --> B["narrow app, window, or URL filter"]
    B --> C["local result or explicit no-data state"]
    C --> D["reviewed notification or report"]
```

## Step by step

**1. Define the event**

Write the exact condition worth reporting, such as a failed build, a new priority ticket, or a dashboard threshold visible in one window. Define what is not in scope.

**2. Set capture exclusions**

Use [recording filters](https://docs.screenpipe.com/privacy-filter.md) to exclude unrelated apps, private browser windows, personal messaging, credentials, and other sensitive surfaces.

**3. Test the filter manually**

Search a short window with `app_name`, `window_name`, `browser_url`, and a query term. Confirm that it returns the intended surface and excludes a nearby unrelated one.

**4. Define all result states**

Require the scheduled task to distinguish **matching event**, **no matching event**, **no captured data**, and **API or execution error**. These states should not collapse into one silent success.

**5. Create a manual scheduled task**

Under **Scheduled tasks → My tasks → NEW**, describe the exact filter, schedule you may add later, and local artifact. Request no external side effects.

**6. Test positive and negative cases**

Run once with a known matching event and once with no event. Inspect the artifact and execution log for both cases.

**7. Add a low-risk notification**

After stable manual runs, enable a desktop notification or local report. Require approval before creating tickets, sending messages, or changing a remote system.

## API test

```bash theme={"system"}
export SCREENPIPE_API_KEY="$(npx -y screenpipe@latest auth token)"

curl -H "Authorization: Bearer $SCREENPIPE_API_KEY" \
  "http://localhost:3030/search?q=failed&app_name=Terminal&window_name=build&start_time=30m+ago&end_time=now&limit=20"
```

## Scheduled task setup prompt

```text theme={"system"}
Create a manual local monitoring scheduled task for one approved app, window, or website.
Use bounded authenticated screenpipe API searches and write a Markdown artifact.
Report one of four states: matching event, no matching event, no captured data,
or execution error. Include the source time range and matching UI text.
Do not send messages, create tickets, or change another system.
```

> [!WARNING]
>
> A missing search result does not prove that an event did not happen. It may mean the surface was not captured, the filter was wrong, or the API failed.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.