Provider Adapter

Purpose

Provider adapters isolate Codex, Claude, Cursor, and OMP hook differences from the core retrieval engine.

Target Interface

interface ProviderAdapter {
  provider: string;
  normalizeHookInput(input: unknown): NormalizedHookEvent;
  renderHookOutput(result: RetrievalResult): unknown;
  installHook?(options: HookInstallOptions): HookInstallResult;
  hookStatus?(options: HookStatusOptions): HookStatusResult;
}

Adapter Responsibilities

• install and inspect hook config when supported;
• expose provider-specific hook config paths and trust/status notes;
• map provider-specific install options into the shared hook runtime command;
• never implement retrieval scoring.

Core Responsibilities

• normalize hook payloads that reach ome hook run;
• match cards;
• explain scores;
• budget context;
• write logs;
• compute stats.

Current Shape

Codex, Claude, Cursor, and OMP use the shared hook runtime and inject additional context through provider-specific hook output. Adapter code lives under packages/adapters/agents/<provider>/ and owns install/status/uninstall.

OMP extension

The OMP adapter installs extensions/ome-recall.ts in the resolved OMP agent directory. before_agent_start sends the task to the existing ome hook run runtime; the extension delivers the returned additionalContext to OMP. It does not change prompt or systemPrompt, or duplicate retrieval scoring. Install, status, uninstall, and doctor use the same target resolver; OMP setup documents its flags and profile rules.