Connect Codex

Chronicle proved that Codex is better with screen memory. It also locked that memory to macOS, ChatGPT Pro, and OpenAI, and dropped anything it judged one-off.

The official LUCI skills give Codex the same job from a memory that is local, includes meetings, and still has the moment Chronicle would have discarded.

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

Install the skills

From LUCI

1. Turn on screen memory and leave LUCI running.
2. Open Settings → Agent access.
3. Tick Codex and click Install.

LUCI writes luci and distill into ~/.codex/skills/.

From GitHub

npx skills add Memories-ai-labs/Luci-skills

Or install globally, for every project:

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

You can also paste this into Codex:

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

Try asking

• "Search my screen memory for the failing test output from this morning"
• "What was I doing between 10am and noon?"
• "Find the part of the call where we picked the database"
• "distill my life"

Optional: connect over MCP

If you would rather give Codex the tools without the skills, add the ready-made Codex snippet from LUCI's Screen Memory panel to ~/.codex/config.toml. The same snippet is on the Codex integration page.

Skills are the recommended path. MCP is the fallback.

Versus Chronicle

You can run both. They do not conflict. A searchable record means you depend less on what a summary decided to keep.

Full comparison: LUCI vs Codex Chronicle. Privacy note: Agent Bridge.