Integrations

Lerim integrates with agents through two separate paths:

• Native trace ingestion reads completed local sessions and feeds Lerim's trace-to-context compiler.
• MCP client support writes a Lerim MCP server entry so an agent can load Lerim tools. Live recall or trace-submit acceptance is claimed only where the matrix lists installed-client/tool-call evidence.

These are not the same support level. MCP config support is useful, but config-only rows are not live recall acceptance and are not a claim that Lerim can capture that agent's completed sessions natively.

See the integration matrix for the public support boundary. Use integration verification before turning config support into a public support claim.

Lerim is not limited to coding agents. Native adapters are strongest for local agent traces, while custom trace import and MCP trace submission are the paths for support, incident, research, operations, and other workflow agents.

Native Adapters Today

• Claude Code
• Codex CLI
• Cursor
• OpenCode
• pi

MCP Config Targets

• Codex CLI
• Claude Code
• Cursor
• OpenCode
• Gemini CLI
• Cline
• Cline CLI, through lerim connect cline-cli --mode mcp
• Claude Desktop
• OpenClaw
• Hermes
• Goose
• Roo Code
• Kilo Code
• Windsurf
• OpenHuman experimental generic MCP config

These are MCP config surfaces unless their page lists installed-client or tool-call evidence. They are not native completed-session capture adapters.

Custom And Business Workflow Sources

• Generic trace submission
• Custom trace folders
• Support operations demo
• Incident operations demo

Planned Plugin Or Extension Paths

• OpenClaw native plugin
• Hermes provider plugin
• pi extension