screenpipe

mediar-ai/screenpipe · now at screenpipe/screenpipe

YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 10, 2026
today
Ship score
96/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 21,226 → 21,823 (Aug 25 – Oct 6, 2026)
+350 stars in the 28 days to 2026-10-06

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
21.9K
Forks
2.2K
Open issues
40
Watchers
116
Primary language
Rust
License
Other
Created
Jun 19, 2024
Owner
screenpipe · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 42 startups in the directory ship primarily in Rust.

Topics

#agents#agi#ai#ai-memory#audio-recording#computer-vision#hermes#hermes-agent#llm#local-ai#local-first#machine-learning#mcp#multimodal#openclaw#privacy#rewind#screen-recording#speech-to-text#ycombinator

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 100%, self-hostable 86%, hosted offering 40%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-10This is the badge for mediar-ai/screenpipe, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/mediar-ai/screenpipe.svg)](https://ossean.com/mediar-ai/screenpipe)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.