Skip to content
LM Nexus Docs

Modules

Modules

Section titled “Modules”

LM Nexus is designed around capability-based modular architecture. Modules can expose capabilities without requiring unrelated modules to hard-import each other.

Rules

Section titled “Rules”
  • Modules should not hard-import each other.
  • Optional integrations appear only when target capabilities exist.
  • Required dependencies block loading or show a dependency warning.
  • Optional missing integration actions are hidden.
  • Capability present but temporarily unavailable means a disabled action with a tooltip.
  • Action failure should show a toast/error.

Example capabilities

Section titled “Example capabilities”
  • Notes exposes notes.create.
  • Chat exposes chat.openWithContext or chat.sendContext.
  • Logs expose exportable log selection.
  • Knowledge exposes exportable entries.

Cross-module examples

Section titled “Cross-module examples”
  • Send chat to Notes appears only if Notes capability exists.
  • Send logs to Chat appears only if Chat capability exists.
  • Quick Capture may require Notes if it fundamentally creates notes.

This keeps LM Nexus modular without making every module depend on every other module.