OMP uses pilangfuse plugin (AsyncLocalStorage) …

Memory ID (Session ID): 019ee258-83ad-7000-b805-ad40381b5a6f
Last Updated: 2026-06-20 02:08:26

Fact Summary

Durable facts:

• OMP uses pi-langfuse plugin (AsyncLocalStorage) to auto-propagate sessionId to Langfuse OTLP spans.
• Endpoints: Langfuse OTLP /api/public/otel/v1/traces; session replay via UI filter on sessionId.
• omp-stats@16.1.4 (src/aggregator.ts:195, db.ts:417) overlays macro stats (cost/latency) keyed by sessionId.
• Key configs: ~/.omp/plugins/pi-langfuse/config.json, package.json, omp-plugins.lock.json; logs at ~/.omp/logs/omp.*.log contain live sessionIds.
• Commands: omp stats, omp stats —json, omp stats —sync.
• Best practices: Prefer OTLP, never manually manage sessionId, use Langfuse waterfall before raw logs, upgrade via package.json then bun install.
• Quirks: clearTracerProvider errors normal on reload; 401 on stats dashboard expected; batch OTLP to avoid 429.
• Deliverable: 80-line emojified ultra-condensed markdown cheat sheet placed in docs/ompp/ after todo-phased workflow (8 phases, 35 tasks).

Reference Session

• Associated Chat Session: 019ee258-83ad-7000-b805-ad40381b5a6f