Screenpipe

Overview

Screenpipe records screen and microphone continuously on macOS, Windows, or Linux, stores data locally, indexes it by text/audio, and runs AI agents that update CRMs, transcribe meetings, track expenses, or monitor competitors, delivering structured data to apps like Slack or Notion. Privacy is kept on device.

From the official site

Capture screen, audio, apps, and meetings locally on macOS, Windows, and Linux. Search your work history or use it with Claude, Codex, and other agents through MCP and API.

The text above is quoted from this tool’s official website — the vendor’s own words.

Official FAQ

What is screenpipe?

screenpipe is AI agent memory: it continuously captures what you've seen, said, and heard on your computer, and gives that context to whatever AI you already use, so it never starts from scratch. It runs on macOS, Windows, and Linux, and exposes your history to any AI through a local API and MCP server.

What will screenpipe actually remember?

screenpipe builds a timestamped, searchable history from on-screen text, app and window context, screen images, system audio, and microphone audio you choose to capture. Use it to find something you saw, reconstruct a day, recover a decision, or draft a follow-up. It cannot recall a period that was not successfully captured.

Do my screen recordings and audio leave my computer?

By default, capture, transcripts, and the search index stay on your device. Data leaves only when a feature you enable needs it, for example cloud AI, cloud sync, an export, a connector, or a team workflow. Each integration has its own destination: local-first does not mean every optional feature runs locally.

Can I exclude sensitive apps, windows, or hours?

Yes. You can pause recording, use recording schedules, include or ignore apps and windows, ignore URLs, and set automatic retention. Privacy filters can redact sensitive text before it is stored, and DRM-protected content pauses capture by default. Review these settings before recording confidential work.

What should I expect from CPU, battery, and storage use?

Any always-on capture uses CPU, battery, and disk. The load depends on your displays, capture quality, audio sources, and local transcription settings. screenpipe uses accessibility events, GPU capture, power tiers, compression, and retention controls to reduce that cost, but it is not zero. If the timeline has gaps, fix capture first. An AI summary cannot recover missing data.

Where can I run it, and can I inspect the code?

screenpipe runs on macOS, Windows, and Linux. Its capture engine is public and source-available under the Screenpipe Commercial License, so you can inspect the code that handles your data, build it yourself, or run the CLI headless.

These questions and answers come from the tool’s own structured data, not written by us.