Connect Factory Droid
Install the official LUCI skills so Factory Droid can search your screen and meetings, and distill your day. Install from the Luci-skills repo, or use MCP.
Droid can take a ticket and work it end to end in your repo. What it cannot see is the context around the ticket: the Slack thread you skimmed, the error in the browser, the call where the scope changed. The official LUCI skills let Droid look those up instead of guessing.
The skills live in the official repo: Memories-ai-labs/Luci-skills.
Install the skills
LUCI's in-app installer does not write into Droid, so install from the repo.
npx skills add Memories-ai-labs/Luci-skills -g -a droidThat writes into ~/.factory/skills/, so the skills work in every project. Drop -g to install into this project's .agents/skills/ instead. Droid reads that folder as well as .factory/skills/.
Or ask Droid:
Install this agent skill for me: https://github.com/Memories-ai-labs/Luci-skillsThat puts luci and distill on the agent. Run /skills inside Droid to check they are there. If they are missing, start a new Droid session.
Try asking
- "Search my screen memory for the error I saw in the browser this morning"
- "What was I working on before I picked up this ticket?"
- "Find the part of today's call where we changed the scope"
- "distill my life"
Optional: connect over MCP
If you would rather give Droid the tools without the skills, add LUCI as an HTTP server. LUCI has no Droid preset, so copy the URL and token from Settings → Agent access → Manual MCP setup in LUCI, then run:
droid mcp add luci <url> --type http --header "Authorization: Bearer <token>" --no-oauthLUCI checks the token, not an OAuth sign-in, so --no-oauth stops Droid from trying one.
Or add it to ~/.factory/mcp.json yourself:
{ "mcpServers": { "luci": { "type": "http", "url": "<url>", "headers": { "Authorization": "Bearer <token>" }, "oauth": false } } }
Droid reloads mcp.json when it changes, so there is nothing to restart. Type /mcp inside Droid to confirm "luci" is connected and see its tools.
More on the protocol path: Connect over MCP.
Skills are the recommended path. MCP is the fallback.
If Droid still cannot see your memory, check Common issues. Privacy note: Agent Bridge.
Was this page helpful?