More agents

Connect Qwen Code

Install the official LUCI skills so Qwen Code can search your screen and meetings, and distill your day. Install from the Luci-skills repo, or use MCP.

Qwen Code reads your repo and runs your terminal. It does not know what happened on this computer before you opened it: the doc you read, the failing build in another window, what you agreed to on a call. The official LUCI skills teach it when to look that up, and how to distill your day.

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

Install the skills

LUCI's in-app installer does not write into Qwen Code, so install from the repo.

bash
npx skills add Memories-ai-labs/Luci-skills -g -a qwen-code

That writes into ~/.qwen/skills/, so the skills work in every project. Drop -g to install into this project's .qwen/skills/ instead.

Or ask Qwen Code:

Install this agent skill for me: https://github.com/Memories-ai-labs/Luci-skills

That puts luci and distill on the agent. A running session picks up new skills after a short delay. Type /skills to see them in the Skills panel.

Try asking

  • "What was I looking at this morning?"
  • "Find the build error I saw in the other terminal"
  • "What did we say about the deadline on yesterday's call?"
  • "distill my life"

You can also run a skill directly by name, for example /distill-my-life.

Optional: connect over MCP

If you would rather give Qwen Code the tools without the skills, add LUCI as an HTTP server. LUCI has no Qwen Code preset, so copy the URL and token from Settings → Agent access → Manual MCP setup in LUCI, then run:

bash
qwen mcp add --transport http luci <url> --header "Authorization: Bearer <token>"

That saves the server to ~/.qwen/settings.json. Add --scope project to save it to this project's .qwen/settings.json instead. To edit the file yourself, the entry looks like this:

json
{
  "mcpServers": {
    "luci": {
      "httpUrl": "<url>",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Note the key is httpUrl, not url. Qwen Code treats url as the older SSE transport. If Qwen Code was already running, restart it, then type /mcp to confirm "luci" is connected.

More on the protocol path: Connect over MCP.

Skills are the recommended path. MCP is the fallback.

If Qwen Code still cannot see your memory, check Common issues. Privacy note: Agent Bridge.

Was this page helpful?