Connect Zed

Zed's agent reads the project and the files you point it at. Each thread starts without the browser tabs, terminal windows, and calls from the rest of your day. The official LUCI skills tell it when to look those up.

The skills live in the official repo: Memories-ai-labs/Luci-skills.

Install the skills

LUCI's in-app installer does not write into Zed. Install from the repo:

npx skills add Memories-ai-labs/Luci-skills -a zed -g

Each skill gets its own folder in ~/.agents/skills/, where Zed looks for global skills. That puts luci and distill on the agent.

For one project only, run it in the project folder without -g. The skills land in .agents/skills/, and Zed loads them only if you trust that worktree.

No restart needed. Type / in the agent panel and luci is in the list. More options: Install skills.

Try asking

• "What was I reading before I opened this file?"
• "Search my screen memory for the migration error from this morning"
• "Find where we agreed on the API shape in the call"
• "distill my life"

Optional: connect over MCP

Zed calls MCP servers context servers. Copy the URL and token from Settings → Agent access → Manual MCP setup in LUCI. Run zed: open settings file and add LUCI under context_servers:

{
  "context_servers": {
    "luci": {
      "url": "<url>",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Or add it from Settings → AI → MCP Servers → Add Server → Add Remote Server. A green dot next to luci means the server is active. By default Zed asks before each tool call. See Connect over MCP.

Skills are the recommended path. MCP is the fallback.

Notes

• Skills apply to the Zed Agent. If you run Claude Code or Codex inside Zed as an external agent, set up that agent instead: Claude Code, Codex.
• What the agent pulls becomes part of that thread, and goes to the model provider you picked in Zed. See Agent Bridge.
• Not working? Common issues. Overview: Zed integration.