@moda-ai/cli 1.35.0 → 1.37.0

package/dist/prompt-source-mcp.js

@@ -5,11 +5,12 @@ import {
   inspectCodeSelectors,
   inspectPythonSelectors,
   safePromptEvidencePath
-} from "./cli-0p6n391h.js";
+} from "./cli-07tv75te.js";
+import"./cli-q79sq80a.js";
 import {
   __commonJS,
   __toESM
-} from "./cli-drabjmaj.js";
+} from "./cli-0v6na3yp.js";
 
 // ../../node_modules/.bun/ajv@8.20.0/node_modules/ajv/dist/compile/codegen/code.js
 var require_code = __commonJS((exports) => {

package/dist/{provision-d242y9qd.js → provision-spwn5t41.js}

@@ -1,15 +1,16 @@
 import {
   selectTenantAndCreateKey
-} from "./cli-scjxgaba.js";
+} from "./cli-qgf2cz2v.js";
 import {
   loadAuthSession
-} from "./cli-yz99t7n8.js";
+} from "./cli-strngwn3.js";
 import {
   CliAuthError,
   resolveIngestUrl,
   resolveModaBaseUrl,
   stringOption
-} from "./cli-drabjmaj.js";
+} from "./cli-q79sq80a.js";
+import"./cli-0v6na3yp.js";
 
 // src/provision.ts
 async function runProvision(context, options = {}) {

package/dist/skills-bundled-mdmhzfsr.js

@@ -0,0 +1,14 @@
+import {
+  bundledSkillsDir,
+  installIntegrationSkill,
+  readBundledIndex,
+  readBundledSkillMd
+} from "./cli-c5c6f0yw.js";
+import"./cli-ssfq84k5.js";
+import"./cli-0v6na3yp.js";
+export {
+  readBundledSkillMd,
+  readBundledIndex,
+  installIntegrationSkill,
+  bundledSkillsDir
+};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@moda-ai/cli",
-  "version": "1.35.0",
+  "version": "1.37.0",
   "description": "CLI for Moda - AI agent analytics and observability",
   "type": "module",
   "bin": {

package/skills/integration/index.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "moda.skill_index.v1",
-  "bundled_at": "2026-09-26T21:50:32.589Z",
-  "cli_version": "1.35.0",
+  "bundled_at": "2026-09-27T21:11:50.220Z",
+  "cli_version": "1.37.0",
   "skills": [
     {
       "id": "integration-cloudflare-think",
@@ -109,7 +109,7 @@
     },
     {
       "id": "integration-python-langchain",
-      "version": "1.0.0",
+      "version": "1.1.0",
       "summary": "Instrument a Python LangChain or LangGraph app with Moda: init before the framework, explicit conversation ids around every run.",
       "targets": {
         "language": "python",

package/skills/integration/integration-python-langchain/EXAMPLE.md

@@ -53,7 +53,7 @@ moda.flush()
 
 ## What changed, and what did not
 
-- `moda-ai` added to the project dependencies.
+- `moda-ai`, `opentelemetry-instrumentation-langchain` and `wrapt<2` added to the project dependencies.
 - One `moda.init` call added at startup, before any LangChain model is
   constructed.
 - Each agent/chain entry point is wrapped in the scoped context managers

package/skills/integration/integration-python-langchain/SKILL.md

@@ -1,7 +1,7 @@
 ---
 id: integration-python-langchain
 name: "Integrate Moda with LangChain / LangGraph (Python)"
-version: 1.0.0
+version: 1.1.0
 category: integration
 targets:
   language: python
@@ -35,10 +35,11 @@ this skill, read https://docs.moda.dev/ingestion/moda-sdk.
 Two constraints drive every step below:
 
 1. Instrument at the Moda SDK level, not inside LangChain. Moda's Python SDK
-   ships a LangChain instrument (`Instruments.LANGCHAIN`), and `moda.init()`
-   enables all instruments by default (`instruments=None`). Do not add
-   LangChain callbacks or handler classes for Moda — no such Moda API
-   exists.
+   knows a LangChain instrument (`Instruments.LANGCHAIN`) and `moda.init()`
+   enables all instruments by default (`instruments=None`), but it only
+   activates when `opentelemetry-instrumentation-langchain` is installed
+   next to `moda-ai` (Step 2). Do not add LangChain callbacks or handler
+   classes for Moda — no such Moda API exists.
 2. Explicit conversation ids are mandatory. Moda's automatic conversation
    detection hashes the first user message, and agent frameworks construct
    different messages on every internal iteration, so without an explicit id
@@ -54,26 +55,58 @@ If you cannot find any LangChain/LangGraph entry point, stop and report.
 
 ## Step 2: Install the SDK
 
-Install `moda-ai` with the package manager this repository already uses
-(`uv.lock` means uv, `poetry.lock` means poetry, otherwise pip):
+Install `moda-ai`, the LangChain instrumentation it activates, and a
+`wrapt<2` pin with the package manager this repository already uses
+(`uv.lock` means uv, `poetry.lock` means poetry, otherwise pip). Without
+`opentelemetry-instrumentation-langchain`, only raw provider calls are traced
+and every chain, agent and tool span is missing. The instrumentation version
+that resolves next to `moda-ai` fails to start under `wrapt` 2, so keep the
+pin until `moda-ai` allows newer instrumentations:
 
 ```bash
-pip install moda-ai
+pip install moda-ai opentelemetry-instrumentation-langchain "wrapt<2"
+```
+
+With pip, also record them in the file the project installs from, so a
+fresh deployment gets them. In `requirements.txt`:
+
+```text
+moda-ai
+opentelemetry-instrumentation-langchain
+wrapt<2
+```
+
+In `pyproject.toml`, add quoted entries to the existing `dependencies` array:
+
+```toml
+dependencies = [
+    # ...existing dependencies...
+    "moda-ai",
+    "opentelemetry-instrumentation-langchain",
+    "wrapt<2",
+]
 ```
 
 With uv:
 
 ```bash
-uv add moda-ai
+uv add moda-ai opentelemetry-instrumentation-langchain "wrapt<2"
 ```
 
 With poetry:
 
 ```bash
-poetry add moda-ai
+poetry add moda-ai opentelemetry-instrumentation-langchain "wrapt<2"
 ```
 
-If `moda-ai` is already a dependency, skip the install.
+Skip `moda-ai` or the instrumentation if it is already a dependency. If the
+project already constrains `wrapt` (for example `wrapt>=2` or `wrapt==2.*`),
+change that constraint to `wrapt<2` rather than skipping it; if something else
+in the project requires `wrapt` 2, stop and report the conflict.
+
+After Step 3, start the app once and check its log: the line
+`Error initializing LangChain instrumentor` means the instrumentation did not
+activate. Stop and report it rather than continuing with provider-only traces.
 
 ## Step 3: Initialize Moda once at startup
 

package/skills/moda-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: moda-cli
-version: 2.6.0
+version: 2.7.0
 description: Query Moda's AI agent trace analytics and manage code-first prompt versions from the terminal — semantic/keyword/hybrid message search, overview KPIs, topic clusters, message context, user frustration detections, tool failures, custom signals, false-positive review of detections, and moda prompts status/sync/promote. Use when the user asks about moda, modaflows, trace or conversation analytics, prompt management, user frustrations, agent observability, tool failure debugging, custom signals, marking a detection as a false positive, wants to find traces or tool calls about a topic, or wants to investigate how their AI agent is performing.
 ---
 
@@ -750,6 +750,45 @@ Rules that keep the proof honest:
 
 ### 9. Custom signals and false positives
 
+**Mark anything as a false positive with one command.** `--reason` (why the
+detection is wrong) is optional but recommended; marks are logged for Moda's review.
+A marked item disappears from every list and count (`moda problems`,
+`hallucinations`, `laziness`, `tool-failures`, problem evidence, the dashboard);
+`--undo` brings it back.
+
+```bash
+moda false-positive problem <problem_id> --reason="two unrelated tools"   # dismiss: hidden at once
+moda false-positive problem-detection <problem_id> --conversation-id=<id> \
+  --attribution-id=<uuid> --reason="refund was approved"                  # one piece of evidence
+moda false-positive quote <conversation_id> --family=frustration --turn=3 \
+  --quote="this is useless lol" --reason="user was joking"               # one user quote
+moda false-positive tool <conversation_id> --tool=send_invoice \
+  --tool-use-id=<tool_use_id> --reason="retried upstream"               # one failing tool call
+moda false-positive laziness <conversation_id> --reason="reload is expected"
+moda false-positive hallucination <conversation_id> --reason="price came from the tool result"
+moda false-positive custom-signal <signal_id> --conversation-id=<id> --reason="refund was approved"
+moda false-positive laziness <conversation_id> --undo                    # remove a mark (any kind but problem)
+moda false-positives                                                     # every current mark (--kind=tool, --all, --limit)
+moda false-positives <conversation_id>                                   # marks + problem reviews on a trace
+```
+
+What each flag does downstream:
+
+| Kind | Effect |
+|---|---|
+| `problem` | Dismisses the problem: it leaves `moda problems` and the dashboard at once, and the reason is folded into the next reconcile. Cannot be undone from the CLI |
+| `problem-detection` | Drops that evidence from the problem and teaches the problem reader (same as `detection-review --verdict=false_positive`) |
+| `custom-signal` | Saved as a `does_not_fit` label with the reason, so the signal learns from it and the live match is retracted (same as `signal-label`). `--undo` removes the label |
+| `quote`, `tool`, `laziness`, `hallucination` | Audit only: recorded for review, never fed back to the detectors |
+
+Find targets with the read commands: `--family`, `--turn` and `--quote` verbatim
+from a `user_quotes` entry in `moda emotions`; a failing call's `tool_use_id` (or `msg_index` when it has none) from
+`moda tool-failure-detail <tool_name>`;
+laziness traces from `moda laziness`; hallucination traces from
+`moda hallucinations`; custom-signal hits from `moda trace-signals` or
+`moda signal <id> --detections`; problem evidence ids from
+`moda problem <id> --evidence`.
+
 **Custom signals** are tenant-defined behaviors (pass/fail criteria) judged on
 every trace. Read them, then label hits so the signal learns:
 
@@ -768,7 +807,7 @@ match; `--label=fits` confirms it. Pass the hit's `anchor_msg_index` (or
 message, and always give a `--note` when rejecting. Labels are throttled to 10
 per minute per API key and are never retried automatically.
 
-**Problem detections** (the dashboard's thumbs on a trace) are reviewed with
+**Problem detections** (the dashboard's flag on problem evidence) are reviewed with
 `detection-review`. A `false_positive` drops the detection out of
 `moda problem <id> --evidence` and is fed back to the problem reader; `clear`
 undoes an earlier review.
@@ -954,7 +993,12 @@ npx: `npx -p @moda-ai/cli moda <command>`.
 | `moda tool-failure-detail <tool_name>` | Per-tool failure breakdown + examples |
 | `moda problems` | Rank cross-signal Problems by root cause (what to fix first) |
 | `moda problem <problem_id>` | One Problem: dossier, or `--evidence`/`--reports`/`--traces`/`--feedback` pages (`--conversations` is a legacy alias of `--traces`) (`--limit` 1–50, `--cursor` verbatim keyset token) |
-| `moda problem-feedback <problem_id>` | Write: `--action=mark_fixed\|dismiss\|flag_attribution\|rename`. `--reason` required for dismiss/flag_attribution; `--new-name` for rename; `--attribution-id` (UUID) required for flag_attribution |
+| `moda problem-feedback <problem_id>` | Write: `--action=mark_fixed\|dismiss\|flag_attribution\|rename`. `--reason` required for flag_attribution, optional for dismiss; `--new-name` for rename; `--attribution-id` (UUID) required for flag_attribution |
+| `moda false-positive <kind> <target>` | Write: kinds `problem\|problem-detection\|quote\|tool\|laziness\|hallucination\|custom-signal`; `--reason` optional; problem-detection needs `--conversation-id` + `--attribution-id`; quote needs `--family`, `--turn`, `--quote`; tool needs `--tool` plus `--tool-use-id` or `--msg-index`; custom-signal needs `--conversation-id`; `--undo` removes a mark (not for problem) |
+| `moda false-positives [conversation_id]` | Current false-positive marks: all (`--kind`, `--all` to include removed, `--limit`) or one trace with its problem detection reviews |
+| `moda laziness` | Laziness detections per trace (`--days-back`, `--limit` 1-50, `--conversation-id`, `--family`) |
+| `moda problem-linear <problem_id>` | The Problem's linked Linear issue (key, state, URL) or `link: null`; needs Linear connected (Integrations → Linear) |
+| `moda problem-linear-file <problem_id>` | Write: file the Problem as a Linear issue (`--team-id`, `--title`, `--priority=0-4`), or link an existing one with `--issue=ENG-123\|URL` (exclusive with the others). Idempotent per Problem |
 | `moda detection-reviews <conversation_id>` | Problem detections on a trace with review state (`--attribution-id=UUID` narrows to one) |
 | `moda detection-review <problem_id>` | Write: `--conversation-id`, `--attribution-id` (UUID), `--verdict=correct\|false_positive\|clear`, optional `--note` |
 | `moda signals` | Custom signals: criteria, status, 7-day judged/matched stats |