Screen-watching AI needs a kill switch

Name: Screen-watching AI needs a kill switch
Availability: InStock
Author: fidorka

by fidorka·Mar 9, 2026·2 points·1 comment

Visit Project View on HN

AI Analysis

●●SolidRabbit HoleBig Brain

MCP integration for querying screen history beats Rewind's closed ecosystem approach.

Strengths

•MCP server integration lets any AI chat query your screen history directly
•Only summaries and OCR stored locally — screenshots deleted after processing
•Supports OpenRouter managed keys or bring-your-own API key for flexibility

Weaknesses

•Screen capture AI memory space already has Rewind, Limitless, and others
•Requires Screen Recording and Accessibility permissions on macOS

Similar Projects

AI/ML●●Solid

ContextD – OCRs your screen activity, use it in AI agents via local API

Open-source Rewind alternative with diff-based OCR and a local HTTP API for agents.

Ship ItDark Horse

thesophiaxu

212mo ago

Productivity●●Solid

I made a Gemma 4 Mac app that names screenshots with local AI

Bundles a 5GB Gemma 4 model locally to name screenshots without uploading.

Niche GemSolve My ProblemSlick

joas_coder

7614d ago

AI/ML●Mid

Open-source time tracking using screenshots

Screenshots are summarized and OCR'd by configurable model endpoints (managed OpenRouter key or BYO/local Ollama) and only short text snippets are kept in a local SQLite DB — neat engineering to convert raw screen noise into searchable memory. The managed-key option lowers onboarding friction, but shipping images off-device by default is a real privacy tradeoff users should weigh. Practical, clever, and clearly built with real usage (timesheets, resume-of-work queries) in mind.

WizardryBold Bet

jzapletal

434mo ago

Developer Tools●●Solid