Does my screen data get sent to Windsurf or its model providers?

The memory itself stays on your machine. What an agent actually pulls becomes part of that conversation. If the agent runs in someone else’s cloud, that conversation goes there. Connect only the agents you trust, and ask them for what you are willing to put in that thread.

How is this different from Windsurf's own workspace indexing?

Windsurf indexes the code in your workspace. LUCI remembers what happened outside it: browser, terminal, other apps, meetings. The two do not overlap, and LUCI is not scoped to one editor.

Do I need to keep LUCI running?

For live history, yes. If LUCI is quit, the luci skill reads your Life folder instead. The memory only grows while LUCI is capturing.

Coding agent

Give Windsurf Memory Beyond the Workspace

Cascade knows your workspace. It does not know the browser tab where the request failed, or the call where the deadline moved. Install the official LUCI skills and Cascade can search everything else that happened on this computer.

See all integrations

Windsurf indexes your workspace well, and that is where its knowledge stops. Debugging happens in browser tabs, terminals, dashboards, and calls. Every time you ask Cascade for help, you become the courier carrying that context in by hand.

LUCI turns the rest of your day into something Cascade can query. Install the two official skills and ask in plain language. The memory is built and stored on this machine, and Cascade pulls only the slice the question needs.

LUCI's in-app installer writes into Claude Code, Cursor, and Codex directly. For Windsurf, install from the official repo, or paste the connection details into Cascade's MCP config if you would rather have the tools without the skill files.

What Windsurf can do with your memory

Debug with what you actually saw

The exception in the console, the failing request in the network tab, the log line on a dashboard. Cascade can search the text of all of it instead of asking you to paste it.

Bring the call into the editor

Microphone and system audio are transcribed on this machine, so Cascade can pull up what was decided while you implement it.

Retrace your own steps

Narrow by app and time, or ask for a whole range at once. What was I doing before this broke becomes a question with an answer.

The memory outlives the editor

The same memory answers Claude Code, Codex, and Cursor. Changing editors does not cost you your history.

Try asking

Questions that work on day one

Search my screen memory for the 500 I saw in the network tab
What was on my screen when the build broke?
Find where we discussed the migration in this morning's call
What did I have open in Chrome before lunch?

Set up Windsurf

01
Turn on Screen Memory in LUCI
Install LUCI on your Mac or Windows machine, enable Screen Memory, and leave the app running.
02
Install the official skills
Ask Cascade to install them from the official repo, or run the installer from a terminal: https://github.com/Memories-ai-labs/Luci-skills
```
npx skills add Memories-ai-labs/Luci-skills -g
```
03
Optional: connect over MCP
Open the MCP panel in Cascade, choose Configure, and paste the connection details from LUCI's Screen Memory panel into ~/.codeium/windsurf/mcp_config.json.

Where Windsurf looks for it

The two skill folders are ordinary files you own. Drop them where this tool reads and it finds them on the next session.

Skills install: npx skills add, or ask Cascade to install from the repo
Optional MCP file: ~/.codeium/windsurf/mcp_config.json
On Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Written by the LUCI installer: Not directly. Claude Code, Cursor, and Codex are.

Frequently asked questions

Not from the app. LUCI's installer writes into Claude Code, Cursor, and Codex. For Windsurf, install from Memories-ai-labs/Luci-skills, or ask Cascade to install the skill from that URL.