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.
Scanned 6/8/2026
Install via CLI
openskills install agentskillexchange/skills---
name: "Capture local screen and audio context so agents can search what happened on your device"
slug: "capture-local-screen-and-audio-context-so-agents-can-search-what-happened-on-your-device"
description: "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."
github_stars: 18176
verification: "security_reviewed"
source: "https://github.com/screenpipe/screenpipe"
author: "screenpipe"
publisher_type: "organization"
category: "Media & Transcription"
framework: "Multi-Framework"
tool_ecosystem:
github_repo: "screenpipe/screenpipe"
github_stars: 18176
npm_package: "screenpipe"
npm_weekly_downloads: 13200
---
# 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.
- Source: https://github.com/screenpipe/screenpipe
- Extracted from upstream docs: https://raw.githubusercontent.com/screenpipe/screenpipe/HEAD/README.md
## Documentation
- https://docs.screenpi.pe
## Source
- [Agent Skill Exchange](https://agentskillexchange.com/skills/capture-local-screen-and-audio-context-so-agents-can-search-what-happened-on-your-device/)
No comments yet. Be the first to comment!