Coding agent

Give opencode Memory of Your Whole Day

opencode reads the repo in front of it. It cannot see the browser tab where the error appeared, or the call where the schema was decided. Install the official LUCI skills and opencode can search all of it, from a memory built and stored on this machine.

opencode runs in your terminal and loads a skill only when the skill applies. That suits a memory you query on demand. Nothing about your day sits in the context window until opencode decides to go and look.

Where opencode looks is the convenient part. Alongside its own .opencode/skills/ and ~/.config/opencode/skills/, it reads ~/.claude/skills/ and ~/.agents/skills/. If you already ticked Claude Code in LUCI's installer, opencode finds the same two skills on its next session with nothing new to configure.

None of the memory is opencode-specific. LUCI captures and indexes this computer, opencode asks it questions, and the same two skills answer for Claude Code, Codex, and Cursor as well.

What opencode can do with your memory

One install, two agents

opencode reads ~/.claude/skills/ as well as its own folders. Tick Claude Code once in LUCI and opencode has the same recall.

Recall exact text

Error strings, stack traces, ticket numbers, names. opencode can keyword-search anything that has been on this screen and gets the matching text back with its app, window, and time.

Recall by meaning

Ask about the caching article you read last week and the search runs over meaning, not the words you have forgotten.

Meetings, not only screens

LUCI transcribes microphone and system audio on this machine, so opencode can search what was said as easily as what was displayed.

Try asking

Questions that work on day one

  • Search my screen memory for the panic I saw in the terminal this morning
  • What was I doing before this test started failing?
  • Find where we agreed on the retry policy in yesterday's call
  • List the docs pages I read while writing this module

Set up opencode

  1. 01

    Turn on Screen Memory in LUCI

    Install LUCI on your Mac or Windows machine, enable Screen Memory, and leave the app running.

  2. 02

    Install the official skills

    Tick Claude Code in LUCI's Settings > Agent access, which writes to ~/.claude/skills/ where opencode also looks. Or install straight from the official repo: https://github.com/Memories-ai-labs/Luci-skills

    npx skills add Memories-ai-labs/Luci-skills
  3. 03

    Optional: connect over MCP

    To give opencode the tools without the skill files, add LUCI under the mcp block of opencode.json using the URL and token from the Screen Memory panel.

    {
      "$schema": "https://opencode.ai/config.json",
      "mcp": {
        "luci": {
          "type": "remote",
          "url": "<url>",
          "enabled": true,
          "headers": { "Authorization": "Bearer <token>" }
        }
      }
    }

Where opencode 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.

Own skills folders
.opencode/skills/, ~/.config/opencode/skills/
Also reads
~/.claude/skills/, ~/.agents/skills/
Optional MCP file
opencode.json, ~/.config/opencode/opencode.json
Written by the LUCI installer
Not directly. Tick Claude Code instead.

Frequently asked questions

No. opencode reads ~/.claude/skills/ in addition to its own skills folders, so one install covers both. Install into ~/.config/opencode/skills/ only if you want a copy opencode alone controls.

Connect your first agent in under a minute

Download LUCI, turn on Screen Memory, install the official skills.
Free on Mac and Windows.

New to LUCI? Read the quick start