Does my screen data get sent to the model Cline is using?

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.

I came from Roo Code. Does anything change?

Roo Code shut down in May 2026 and its own docs point at Cline. Nothing about LUCI changes. The memory is the same and the two skills move with you, so install them under .cline/skills and carry on.

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 Cline Memory of Everything Around the Code

Cline reads your files and runs your commands with your approval. It cannot see the browser tab where the request failed, or the call where the plan changed. Install the official LUCI skills and Cline can search both.

See all integrations

Cline works inside VS Code and asks before every step, which makes it good at the things it can see and blind to the things it cannot. The browser, the terminal in another window, the dashboards, the calls: none of it reaches Cline unless you carry it in yourself.

LUCI records that half of the day on this machine, and the official skills tell Cline when to search it. Skills go in .cline/skills, one folder each with a SKILL.md, and Cline loads them when a task matches.

Cline keeps MCP servers in its own cline_mcp_settings.json rather than in the editor-wide mcp.json, so that is the file to edit if you take the protocol path. Skills stay the path we recommend.

What Cline can do with your memory

See what you saw

The exception in the console, the failing request, the log line from a dashboard. Cline can search the text instead of asking you to paste it.

Approve one lookup at a time

Cline asks before it acts, and a memory search is no exception. You see the question before the answer is pulled.

Meetings on the record

LUCI transcribes microphone and system audio on this machine, so Cline can find the sentence where a requirement changed.

A memory you keep

The same two skills work in Claude Code, Codex, Cursor, and more. When you change tools, the history comes with you.

Try asking

Questions that work on day one

Search my screen memory for the TypeError I saw in the console
What was on my screen when the deploy failed?
Find the part of the call where we chose the queue
What tabs did I have open while writing this file?

Set up Cline

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
Install from the official repo, or ask Cline to install the skill from that URL. Each skill lands as its own folder under .cline/skills: https://github.com/Memories-ai-labs/Luci-skills
```
npx skills add Memories-ai-labs/Luci-skills
```
03
Optional: connect over MCP
Open Cline's MCP servers panel, add a remote server, and paste the URL and token from LUCI's Screen Memory panel. Cline writes them into cline_mcp_settings.json for you.

Where Cline 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 folder: .cline/skills/<skill>/SKILL.md
Optional MCP file: cline_mcp_settings.json
MCP file on macOS: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/
Written by the LUCI installer: Not directly. Claude Code, Cursor, and Codex are.

Frequently asked questions

.cline/skills, one folder per skill, each holding a SKILL.md. npx skills add Memories-ai-labs/Luci-skills writes them for you, and copying the two folders in by hand works just as well.