Capture local screen and audio context so agents can search what happened on your device
Use Screenpipe when an agent needs private, local-first memory of what you saw or heard on your computer, including searchable screen text, app context, and transcripts, instead of relying on a chat-only memory layer.
What it does
Capture local screen and audio context so agents can search what happened on your device
Use Screenpipe when an agent needs private, local-first memory of what you saw or heard on your computer, including searchable screen text, app context, and transcripts, instead of relying on a chat-only memory layer.
Prerequisites
Screenpipe desktop app or source build, local screen and audio permissions, sufficient local storage, and optionally an MCP-compatible agent client
Installation
Use the upstream install or setup path that matches your environment:
- Make sure to understand the main branch is moving fast and breaking things, if you're looking for a stable version check app releases https://github.com/screenpipe/screenpipe/releases and use the git commit accordingl...
Basic usage or getting-started notes:
-
Minimum requirements: 8 GB RAM recommended. ~5–10 GB disk space per month. CPU usage typically 5–10% on modern hardware thanks to event-driven capture.
-
Typical CPU usage is 5–10% on modern hardware. Event-driven capture only processes frames when something changes, and accessibility tree extraction is much lighter than OCR.
-
Extracted from upstream docs: https://raw.githubusercontent.com/screenpipe/screenpipe/HEAD/README.md
Documentation
Source
Capabilities
Install
Quality
deterministic score 0.45 from registry signals: · indexed on github topic:agent-skills · 8 github stars · SKILL.md body (1,523 chars)