screenpipeReview: local screen memory for agents
Freemium
screenpipe records your computer so an AI agent can answer questions about work you've already done. It captures your screen, reads the text off it when an app won't share it, transcribes audio, and logs which window you were in. Ask what you told a client about pricing and it searches the recording, including the bits you never saved anywhere.
It doesn't join your calls, and by default nothing leaves your machine. A local API and MCP let Claude, Codex or your own agent see only the parts you choose, so the end of a meeting can kick off notes or a follow-up. You decide which apps, windows and websites to exclude before anything is recorded. Free covers one device and your recent work. Basic is $25 a month, or $21 a month billed yearly ($250/year). Business is $50 per seat a month, or $42 billed yearly ($500/seat/year). See screenpipe.com/pricing for current plans. It runs on macOS, Windows and Linux, and uses about 30 GB of disk a month.
Freemium
Keywords
mcp, local, agents, memory, screen-recording
- Capture that does not wait to be invited: screen frames, audio, and window events recorded continuously, with OCR when an app will not expose its own text.
- The recording stays on the machine: history lives in a local database, and a local API plus MCP hand Claude, Codex, or your own agent only the slices you approve.
- Pipes that fire on what happened: a meeting ending can write notes or draft a follow-up, and you see the trigger, the context it used, and where the output went.
- Exclusions set before capture: block apps, windows, and URLs, and redact fields on device. Enterprise adds SSO, MDM, and audit.
- Plans: free download; Basic $25/month or $21/month billed annually ($250/year); Business $50/seat/month or $42/seat/month billed annually ($500/seat/year). Current plans: screenpipe.com/pricing.
TMRW VERDICT
For the work you never wrote down
by TMRW Team·Oct 4, 2026
Most AI memory tools ask you to bring the material: paste the transcript, upload the file, remember to invite the bot. screenpipe starts from the opposite idea, that the part of your week worth asking about was never saved anywhere. The number someone said out loud, the thread you scrolled past, the tab you closed on Tuesday. If an agent is going to write your update from what actually happened instead of what was on the calendar, something has to have been watching.
What you install is a local database that AI tools can query over MCP. That's the reason to use it and also the reason to go slowly. Always-on recording isn't something you can half commit to. Either the recording exists or it doesn't, and whatever's in it can be read by any model you point at it later. Set your app, window and website exclusions on the first run, before someone else's inbox ends up on your disk during a screen share. The 30 GB a month is the cheap part.
It's worth the disk space if you keep asking a chatbot where you left something and the chatbot wasn't there. Think consultants juggling five clients, or anyone whose real decisions happen in calls and DMs instead of documents.
If your work already lives somewhere searchable, with decisions in tickets and conversations in threads, a screen recording just duplicates it. If you really want meeting notes, Granola is much lighter. And if a recorder on your work laptop means a conversation with your legal team you're not ready for, wait. That's a policy question, not a missing feature.
