Does my screen data get sent to Google?

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.

Skills or a Gemini CLI extension?

Skills. They are two folders and they need no extension manifest. Extensions are useful when you want to ship an MCP server plus context files as one unit, which is not what LUCI needs.

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 Gemini CLI Memory of This Machine

Gemini CLI is quick at the task in front of it and blank on everything before it. Install the official LUCI skills and it can search what you saw and what was said on this computer, from a memory that is built and stored here.

See all integrations

Gemini CLI is at its best when you hand it the whole picture, which is also the tiring part. Every session starts with you retyping the error you already read, the page you already looked at, the decision the team already made.

LUCI keeps that record for you, and the official skills teach Gemini CLI when to consult it. Capture and indexing run on this machine. Gemini asks for the slice it needs, when a question calls for it.

Gemini CLI keeps its settings in ~/.gemini/settings.json and its extensions in ~/.gemini/extensions/. LUCI needs neither if you install the skills, and both stay available if you would rather take the MCP path.

What Gemini CLI can do with your memory

Stop re-explaining your morning

Ask what you were doing between two times and Gemini gets an account of your activity instead of a shrug.

Exact text, or the gist

Keyword-search an error string you remember word for word, or search by meaning when you only remember what the page was about.

Calls are searchable too

LUCI transcribes microphone and system audio locally, so a decision made out loud is as findable as a line of code.

Write the day down

The second skill distills a finished day into a record in your Life folder. Your agent writes your Life, and LUCI keeps the memory underneath.

Try asking

Questions that work on day one

What was I looking at this morning?
Search my screen memory for the error I saw in the browser
What did we say about the API on yesterday's call?
distill my life

Set up Gemini CLI

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 Gemini 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
Add LUCI under mcpServers in ~/.gemini/settings.json, using the URL and token from the Screen Memory panel. A project-level .gemini/settings.json works the same way.

Where Gemini CLI 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.

Settings file: ~/.gemini/settings.json, .gemini/settings.json per project
Optional MCP key: mcpServers
Extensions folder: ~/.gemini/extensions/
Written by the LUCI installer: Not directly. Claude Code, Cursor, and Codex are.

Frequently asked questions

The CLI, and anything else on this machine that can load skills or speak MCP. The memory is local, so a browser tab talking to Gemini in Google's cloud has no route to it.