Launching today
LUCI Desktop
Let your AI agents remember what you've seen
668 followers
Let your AI agents remember what you've seen
668 followers
Luci saves your screen history and meeting transcripts locally, so agents like Claude Code, Cursor and Codex can help you find a page you forgot to bookmark or recall a decision from a call. Capture context across apps without setting up a connector for each one. Includes on-device transcription and daily summaries with Microsoft Foundry Local. Free for Mac and Windows.
Statable Analytics
Congrats on the launch! Question from a heavy Claude Code user: I usually have two sessions running side by side on different parts of the same project. Can both query Luci at the same time without stepping on each other? And more interesting for me, would session B be able to recall what session A was doing on screen, so Luci works as shared context between them?
Memories.ai
@yevhen_skrypets Great question, and this is exactly how I run it myself. Luci runs a single local MCP server on your machine over HTTP, so any number of Claude Code sessions can connect and query it at the same time without stepping on each other. And yes to the second part: Luci captures what is on your screen, so if session A's work was visible, session B can ask what A was doing and pick up from there. There is no per-session sandbox, the whole screen history is one shared memory. Would love to hear how the two-session setup feels once you try it.
Most tools push everything to the cloud so a purely local memory engine is a breath of fresh air.
LUCI Desktop
@ashley_james Thank you! Screen and meeting history can be deeply personal, so keeping that memory on your own device matters to us.
Memories.ai
@ashley_james Thanks Ashley. Screen history is about as personal as data gets, so local was not a feature choice for us, it was the starting condition.
Pulling live screen context straight into Cursor without setting up app connectors is super convenient.
Memories.ai
@ashir_murtaza1 Thanks Ashir. That was the whole point: agents already know how to ask, they just had no memory of what you saw. Curious what you end up pulling into Cursor most, error traces, specs, or something else.
Dial
the retention and on-disk answers below cover your own data well. the case I'm curious about is other people's: a screen share where a coworker's Slack DMs are visible in the background, or a video call where someone else's face and name are on screen. that's not really "your history" anymore, it's theirs, captured without them opting into anything. is there any redaction or exclusion for windows/apps you don't own the content of, or is the assumption that if it crossed your screen it's fair game to record?