01 / THE SIGNAL

我们发现了什么

我构建了 Screenpipe(https://screenpipe.com),这是一款在本地(仅本地!)录制你的屏幕和音频的应用,并为 AI 智能体提供关于你所见、所说和所听内容的可搜索记忆。我在 https://www.tella.tv/video/build-your-ai-second-brain-with-s... 制作了一个 HN 风格的演示视频。

  • 来源:Hacker News(发现于 2026-07-24)
  • 证据等级:D · 发现产品或需求信号,暂未获得可核验的商业证据。
  • 商业模式:API / Usage-based
  • 主题:AI Agent
  • 初筛评分:30.4/100 · 收录 1 次
#工作流自动化#待验证#产品发现
02 / SOURCE & EVIDENCE

证据,比故事更重要。

发现产品或需求信号,暂未获得可核验的商业证据。

规则清洗与初筛,未经人工商业核验。原文语境、实际客户和付费情况仍需自行验证。

引用与数字披露

来源类型(原作者自述/第三方测算/媒体转引)需采集端标注,本版尚未落字段。

短句引用
作者
未标注
抓取日期
来源类型
未标注
数字口径
币种
未标注
口径
未标注
披露主体
未标注
披露日期
未标注

中文辅助译文(全文)

嗨,Hacker News,我是 Louis。我打造了 Screenpipe ( https://screenpipe.com ),这是一款仅在本地录制你的屏幕和音频的应用,并让 AI 智能体拥有一份可搜索的记忆,记录你看过、说过、听过的一切。这让自动化你的重复任务、将它们转化为 SOP(Standard Operating Procedure,标准操作流程)等变得更加轻松。我在 https://www.tella.tv/video/build-your-ai-second-brain-with-s... 制作了一个 HN 风格的演示视频,还有一个营销视频在 https://www.youtube.com/watch?v=c1jV6E9pyug 。

我为这件事着迷了很长时间。自 2020 年起我一直在维护一个"第二大脑",其中存储着日记、手写笔记、我听的音乐、我正在做的项目、我与人的对话、个人 CRM 等等。我早期尝试了大量 RAG,使用 ParlAI、几百个微调的 GPT2 模型以及 GPT3 ( https://forum.obsidian.md/t/fine-tuning-openai-api-gpt3-on-y... )。后来我打造了 Ava,这是第一个 Obsidian AI 插件,迅速增长到几千用户。它后来演变为 Embedbase,一个让基于 RAG 构建 AI 应用更容易的 API。从这些经历中我学到的是:让模型知道你正在电脑上做什么的背景信息,对于让它们按照你的意愿行事是多么重要。

早期是微调,但太痛苦了;后来出现了工具调用,让 AI 能访问你使用的软件,但仍不够自主,需要微观管理。接着 MCP 出现了,但它感觉太静态了,非技术用户难以构建和使用 MCP。然后我们有了 skills。最近我们看到了 Karpathy 维护的 LLM wiki、Garry 的 GBrain 等,这些案例中,智能体会逐步维护一个持久的 Markdown 页面集合。新来源更新实体页面,强化或反驳现有声明,并随着时间推移改进综合。我喜欢这种模式,但它仍然始于某人选择和导入来源。仍然没有办法让 AI 知道你和你的公司每天在做什么,跨应用、而不只是在应用内部。当然,并非每个人都想要这样。但我想要!我希望 AI 知道我在做什么,再也不会丢失记忆,我希望它使用和人类相同的软件,避免痛苦的上下文切换。

我在 2024 年开始为自己打造 Screenpipe —— 一个录制屏幕并将这些上下文接入 AI 的 CLI。2024 年一位 HN 用户发布了它 ( https://news.ycombinator.com/item?id=41695840 ),那场讨论影响了产品。最有用的批评涉及录制同意、本地安全、CPU 使用率、信噪比,以及智能体能否在这些数据之上行动。

最初的实现是从连续录制视频并对每一帧运行 OCR 开始的。但这会产生重复数据,消耗大量资源(基本上把你的电脑变成太空加热器!),并且丢弃了操作系统已知的结构。现在 Screenpipe 改为监听诸如应用切换、点击、输入停顿、滚动和空闲回退等事件。当发生有意义的变更时,它会将同一时间戳的截图与操作系统的可访问性树配对。在结构化可访问性数据不可用时才使用 OCR。我们还持续捕获音频,通过 Parakeet/Whisper 或使用云模型识别说话者并进行本地转录。所有内容都索引在本地 SQLite 数据库、mp4 文件中,有时还有 md 文件中。3030 端口上为智能体开放了一个对 AI 友好的 API,带身份验证、MCP 和 skills。

Screenpipe 运行一段时间后,你可以通过我们的内置聊天、Claude、ChatGPT、Hermes、Openclaw 或任何智能体来使用它,做以下事情: - 为当前聊天添加上下文,例如"收集关于任务 X 的所有上下文",然后用更少的提示就能达成目标 - 检索信息,例如"检索我上午 8 点到下午 4 点在做的任务,列出已完成和未完成的内容" - 为你的智能体创建并维护个人 wiki / 第二大脑:"每 1 小时把我做的所有事情组织成项目、人物、任务、会议,作为 markdown 文件和文件夹放到我的 Obsidian vault 中" - 创建自动化:每当我在 LinkedIn 上访问某人的主页时,更新我的 CRM - 发现自动化机会:查看我团队本周做的所有事情,将其转化为自动化机会列表

Screenpipe 数据存储在本地,不过我们也提供企业版来发现自动化机会,为此由公司决定数据的存储位置。我们构建了自己的 AI PII 模型来打码敏感信息,它在 Apple MLX 或 Windows DirectML 上本地运行,我们也支持面向低端设备的云端保密推理,尽管我们的本地模型设计为使用 <1% CPU 和 <400 MB 内存。用户可以设置要过滤的应用、窗口和 URL,以及浏览器隐身模式。我们还支持录制计划和其他隐私功能。

我们大部分代码库用 Rust、MLX、Onnx 编写,我们喜欢用 cidre 或直接 C 调用来对接 Apple API,用 windows-rs 对接 Windows API。我们也在试验性支持 Linux。我们有一个桌面应用 ( https://screenpipe.com/how-to-install ) 和一个 CLI:npx screenpipe record

你可以在不创建账户的情况下运行它。所有代码都在 https://github.com/screenpipe/screenpipe 源代码开放。我们迈出了可怕的一步,制作了我们自己的 Screenpipe 商业许可证。我知道 HN 强烈倾向 OSI 开源(MIT/Apache 等),但找不到一种可持续的方式在让公司免费商业使用的同时持续开发 Screenpipe。所以现在个人非商业、非营利、教育和研究使用是免费的,但商业使用需要许可证。许可证变更之前发布的版本仍按 MIT 提供。我们有免费版,以及其他套餐,包括帮助公司发现自动化机会的 Enterprise。

很想听听任何反馈、你用 screenpipe 做过的事、或你想要的特性。

译文由上游机器翻译生成,可能有误;判断请以英文原文为准。

英文原文(来源本站未改写)

Hi Hacker News, I'm Louis.I built Screenpipe ( https://screenpipe.com ), an app that records your screen and audio locally (only!), and gives AI agents a searchable memory of what you've seen, said, and heard.This makes it easier to automate your repetitive tasks, turn them into SOPs (Standard Operating Procedure) and so on.I made a HN-style demo video at https://www.tella.tv/video/build-your-ai-second-brain-with-s... and there’s a marketing video at https://www.youtube.com/watch?v=c1jV6E9pyug .I’ve been obsessed with this for a long time.

I’ve been maintaining a “second brain” since 2020, in which I would store journals, handwritten notes, music I listen to, projects I'm working on, conversations I have with people, personal CRM etc.I experimented a lot of RAG in the early days with ParlAI, hundreds of fine-tuned GPT2 models, and GPT3 ( https://forum.obsidian.md/t/fine-tuning-openai-api-gpt3-on-y... ).Later I built Ava, the first Obsidian AI plugin, which grew to a few thousands of users quickly.It then became Embedbase, an API to make it easier to build AI apps powered by RAG.

What I learned from all this is how important it is for the models to have context about what you’re doing on your computer, in order to get them to do what you want.In the early days there was fine tuning but it was too much pain, then there was tool calling so that AI can access software you use but still kinda not autonomous enough. needing micro management.Then MCP came, but it felt too static, and non technical users struggled to build and use MCP.Then we got skills.Most recently we’ve seen Karpathy’s LLM-maintained wiki, Garry's GBrain, etc., where an agent incrementally maintains a persistent collection of Markdown pages.

New sources update entity pages, strengthen or contradict existing claims, and improve a synthesis that compounds over time.I like this pattern, but it still begins with someone selecting and importing the sources.There is still no way AI can know what you and your company are doing every day, across apps, not just inside of apps.Of course, not everyone wants this.But I do!I want AI to know what I'm doing and never lose memory ever again, and I want it to use the same software that humans do, without painful context switches.I started building Screenpipe for myself in 2024 - a CLI to record your screen and plug this context into AI.

An HN user posted it in 2024 ( https://news.ycombinator.com/item?id=41695840 ) and that discussion influenced the product.The most useful criticism concerned recording consent, local security, CPU usage, signal-to-noise, and whether agents could act on top of the data.The naive implementation started from continuously recording video and running OCR over every frame.But that creates duplicate data, consumes substantial resources (it basically turns your computer into a space heater!), and discards structure the operating system already knows.Screenpipe now instead listens for events such as app switches, clicks, typing pauses, scrolling, and idle fallbacks.

When something meaningful changes, it pairs a screenshot with the operating system’s accessibility tree at the same timestamp.OCR is used when structured accessibility data is unavailable.We also capture audio continuously, identify speakers and transcribe locally through Parakeet/Whisper or using cloud models.Everything is indexed in a local SQLite database, mp4 files, and sometimes md files.An AI friendly API on port 3030 is open for agents, with authentication and a MCP and skills.

Once Screenpipe has been up and running for a while, you can use it through our built-in chat, Claude, ChatGPT, Hermes, Openclaw, or any agent, to do things like: - adding context to your current chat, e.g. "gather all context about task X", then requiring less prompts to achieve your goal - retrieve information, e.g. "retrieve the tasks i was working on from 8 am to 4 pm, make a list of what got done and what's left" - create and maintain a personal wiki / second brain for your agents: "every 1h organize everything i do in projects, people, tasks, meetings in my Obsidian vault as markdown files and folders" - create automations: whenever i visit someone's profile on linkedin, update my crm - find automation opportunities: look at everything my team has done this week and turn it into a list of automation opportunities Screenpipe data is stored locally, though we also offer an enterprise plan to discover automation opportunities and for that the company decides where the data lives.

We built our own AI PII model to redact sensitive information, it runs locally on Apple MLX or Windows DirectML, we also support cloud confidential inference for low end devices, although our local models are meant to use <1% CPU and <400 mb RAM.Users can set apps, windows, and urls to filter, in addition to browser incognito mode.We also support recording schedules and other privacy features.Most of our codebase is written in Rust, MLX, Onnx, we like cidre or direct C call for Apple APIs and windows-rs for Windows API.We also experimentally support Linux.We have a desktop app ( https://screenpipe.com/how-to-install ) and a CLI: npx screenpipe record

You can run that without creating an account.All the code is source-available at https://github.com/screenpipe/screenpipe .We took the dreaded step of making our own Screenpipe Commercial License.I know HN strongly prefers OSI open source (MIT/Apache/etc.) but couldn’t find a sustainable way to keep developing Screenpipe while companies were using it commercially for free.So now personal non-commercial, nonprofit, educational, and research use is free, but commercial use requires a license.Versions released before the license change remain available under MIT.We have a free tier, and other plans, including Enterprise which helps companies find automation opportunities.

Would love to hear any feedback, things you've done with screenpipe, or features you'd want

出处https://news.ycombinator.com/item?id=49024620抓取日期 · 采集源 Hacker News

03 / EVIDENCE GAPS

这条还缺什么证据?

下面每条都由本条已有字段推出(等级、理由、商业模式、来源次数、是否演示), 本站不生成推测性结论;通用验证方法放在方法论页。

  • 可核验的收入或付费证据查官网定价页与付费口径;第三方数据源(如 GetLatka)只作旁证,需标注来源与时点。
  • 只有单一来源找一手站点或其他渠道是否重复出现同一产品;社区热帖数量不等于商业进展。

通用验证清单(谁有这个问题/谁愿意付费/一个人能交付哪一小步)见我们的筛选方法。

04 / SIGNAL HISTORY

发现时间线