> ## 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 monitor for an approved app, window, or website with a clear no-data state and reviewed alerts.

{/* https://screenpi.pe */}

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={null}
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

<Steps>
  <Step title="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.
  </Step>

  <Step title="set capture exclusions">
    Use [recording filters](/privacy-filter) to exclude unrelated apps, private browser windows, personal messaging, credentials, and other sensitive surfaces.
  </Step>

  <Step title="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.
  </Step>

  <Step title="define all result states">
    Require the pipe to distinguish **matching event**, **no matching event**, **no captured data**, and **API or execution error**. these states should not collapse into one silent success.
  </Step>

  <Step title="create a manual pipe">
    Under **Pipes → My Pipes → create your own pipe**, describe the exact filter, schedule you may add later, and local artifact. request no external side effects.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## API test

```bash theme={null}
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"
```

## pipe-builder prompt

```text theme={null}
Create a manual local monitoring pipe 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.
</Warning>