@poncho-ai/harness 0.59.8 → 0.59.10

package/.turbo/turbo-build.log

@@ -1,5 +1,5 @@
 
-> @poncho-ai/harness@0.59.8 build /home/runner/work/poncho-ai/poncho-ai/packages/harness
+> @poncho-ai/harness@0.59.10 build /home/runner/work/poncho-ai/poncho-ai/packages/harness
 > node scripts/embed-docs.js && tsup src/index.ts --format esm --dts
 
 [embed-docs] Generated poncho-docs.ts with 4 topics
@@ -9,8 +9,8 @@
 CLI Target: es2022
 ESM Build start
 ESM dist/isolate-F2PPSUL6.js 53.82 KB
-ESM dist/index.js            558.23 KB
-ESM ⚡️ Build success in 235ms
+ESM dist/index.js            559.89 KB
+ESM ⚡️ Build success in 238ms
 DTS Build start
-DTS ⚡️ Build success in 8463ms
-DTS dist/index.d.ts 101.66 KB
+DTS ⚡️ Build success in 7368ms
+DTS dist/index.d.ts 102.06 KB

package/CHANGELOG.md

@@ -1,5 +1,26 @@
 # @poncho-ai/harness
 
+## 0.59.10
+
+### Patch Changes
+
+- [`fad3918`](https://github.com/cesr/poncho-ai/commit/fad3918302114f76a29080cf28e9c003c61ef0d9) Thanks [@cesr](https://github.com/cesr)! - Stamp `session.id` / `user.id` on EVERY span, not just the invoke_agent
+  root. Observability backends resolve a span's identity from its own
+  attributes — Latitude's console session/conversation views key on the LLM
+  generation spans, so root-only attributes grouped the API-level trace but
+  left the console showing one session per turn and no user. The identity now
+  rides the OTel Context and an IdentityAttributeSpanProcessor injects it
+  into every descendant span (LLM steps, tool executions) at start.
+
+## 0.59.9
+
+### Patch Changes
+
+- [`eb9600a`](https://github.com/cesr/poncho-ai/commit/eb9600a111cf74968689f8b33835d8b58c64e375) Thanks [@cesr](https://github.com/cesr)! - Root trace spans now carry `session.id` (= conversationId) and `user.id`
+  (new `config.telemetry.userId`) alongside the existing
+  `gen_ai.conversation.id` — the attributes observability backends
+  (Latitude) key session grouping and user filtering on.
+
 ## 0.59.8
 
 ### Patch Changes

package/dist/index.d.ts

@@ -756,6 +756,11 @@ interface PonchoConfig extends McpConfig {
             url: string;
             headers?: Record<string, string>;
         };
+        /** End-user identifier (e.g. an email) stamped as `user.id` on every
+         *  root trace span — observability backends (Latitude) group and
+         *  filter traces by it. Per-harness, so a harness-per-user consumer
+         *  sets it once at construction. */
+        userId?: string;
         handler?: (event: unknown) => Promise<void> | void;
     };
     skills?: Record<string, Record<string, unknown>>;
@@ -1442,6 +1447,8 @@ declare class AgentHarness {
     private otlpSpanProcessor?;
     private otlpTracerProvider?;
     private hasOtlpExporter;
+    /** End-user id (config.telemetry.userId) stamped as `user.id` on root spans. */
+    private telemetryUserId?;
     private _browserSession?;
     private _browserMod?;
     private parsedAgent?;

package/dist/index.js

@@ -8745,7 +8745,7 @@ var createSubagentTools = (manager) => [
 ];
 
 // src/harness.ts
-import { trace, context as otelContext, SpanStatusCode, SpanKind, diag, DiagConsoleLogger, DiagLogLevel } from "@opentelemetry/api";
+import { trace, context as otelContext, createContextKey, SpanStatusCode, SpanKind, diag, DiagConsoleLogger, DiagLogLevel } from "@opentelemetry/api";
 import { NodeTracerProvider, BatchSpanProcessor } from "@opentelemetry/sdk-trace-node";
 import { OTLPTraceExporter } from "@opentelemetry/exporter-trace-otlp-http";
 
@@ -8928,6 +8928,28 @@ var telemetryLog2 = createLogger7("telemetry");
 var costLog = createLogger7("cost");
 var mcpLog2 = createLogger7("mcp");
 var modelLog = createLogger7("model");
+var TELEMETRY_SESSION_ID_KEY = createContextKey("poncho.telemetry.session_id");
+var TELEMETRY_USER_ID_KEY = createContextKey("poncho.telemetry.user_id");
+var IdentityAttributeSpanProcessor = class {
+  onStart(span, parentContext) {
+    const sessionId = parentContext.getValue(TELEMETRY_SESSION_ID_KEY);
+    if (typeof sessionId === "string" && sessionId) {
+      span.setAttribute("session.id", sessionId);
+    }
+    const userId = parentContext.getValue(TELEMETRY_USER_ID_KEY);
+    if (typeof userId === "string" && userId) {
+      span.setAttribute("user.id", userId);
+    }
+  }
+  onEnd() {
+  }
+  forceFlush() {
+    return Promise.resolve();
+  }
+  shutdown() {
+    return Promise.resolve();
+  }
+};
 function formatOtlpError(err) {
   if (!(err instanceof Error)) return String(err);
   const parts = [];
@@ -9511,6 +9533,8 @@ var AgentHarness = class _AgentHarness {
   otlpSpanProcessor;
   otlpTracerProvider;
   hasOtlpExporter = false;
+  /** End-user id (config.telemetry.userId) stamped as `user.id` on root spans. */
+  telemetryUserId;
   _browserSession;
   _browserMod;
   parsedAgent;
@@ -10327,6 +10351,7 @@ var AgentHarness = class _AgentHarness {
     await this.refreshMcpTools("initialize");
     const telemetryEnabled = config?.telemetry?.enabled !== false;
     const otlpConfig = telemetryEnabled ? normalizeOtlp(config?.telemetry?.otlp) : void 0;
+    this.telemetryUserId = config?.telemetry?.userId;
     if (otlpConfig) {
       diag.setLogger(new DiagConsoleLogger(), DiagLogLevel.WARN);
       const exporter = new OTLPTraceExporter({
@@ -10336,7 +10361,9 @@ var AgentHarness = class _AgentHarness {
       const processor = new BatchSpanProcessor(exporter);
       this.otlpSpanProcessor = processor;
       const provider2 = new NodeTracerProvider({
-        spanProcessors: [processor]
+        // Identity injector FIRST so every span (root, LLM steps, tool
+        // executions) carries session.id/user.id before batching/export.
+        spanProcessors: [new IdentityAttributeSpanProcessor(), processor]
       });
       provider2.register();
       this.otlpTracerProvider = provider2;
@@ -10492,11 +10519,24 @@ var AgentHarness = class _AgentHarness {
         kind: SpanKind.INTERNAL,
         attributes: {
           "gen_ai.operation.name": "invoke_agent",
-          ...input.conversationId ? { "gen_ai.conversation.id": input.conversationId } : {},
+          // `session.id` / `user.id` are the attributes observability
+          // backends (Latitude) key session grouping and user filtering on.
+          // gen_ai.conversation.id is kept for the GenAI semantic convention.
+          ...input.conversationId ? {
+            "gen_ai.conversation.id": input.conversationId,
+            "session.id": input.conversationId
+          } : {},
+          ...this.telemetryUserId ? { "user.id": this.telemetryUserId } : {},
           ...input.tenantId ? { "tenant.id": input.tenantId } : {}
         }
       });
-      const spanContext = trace.setSpan(otelContext.active(), rootSpan);
+      let spanContext = trace.setSpan(otelContext.active(), rootSpan);
+      if (input.conversationId) {
+        spanContext = spanContext.setValue(TELEMETRY_SESSION_ID_KEY, input.conversationId);
+      }
+      if (this.telemetryUserId) {
+        spanContext = spanContext.setValue(TELEMETRY_USER_ID_KEY, this.telemetryUserId);
+      }
       try {
         const gen = this.run(input);
         let next;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@poncho-ai/harness",
-  "version": "0.59.8",
+  "version": "0.59.10",
   "description": "Agent execution runtime - conversation loop, tool dispatch, streaming",
   "repository": {
     "type": "git",

package/src/config.ts

@@ -231,6 +231,11 @@ export interface PonchoConfig extends McpConfig {
       url: string;
       headers?: Record<string, string>;
     };
+    /** End-user identifier (e.g. an email) stamped as `user.id` on every
+     *  root trace span — observability backends (Latitude) group and
+     *  filter traces by it. Per-harness, so a harness-per-user consumer
+     *  sets it once at construction. */
+    userId?: string;
     handler?: (event: unknown) => Promise<void> | void;
   };
   skills?: Record<string, Record<string, unknown>>;

package/src/harness.ts

@@ -67,9 +67,41 @@ import { createSkillTools, normalizeScriptPolicyPath } from "./skill-tools.js";
 import { createSearchTools } from "./search-tools.js";
 import { createSubagentTools } from "./subagent-tools.js";
 import type { SubagentManager } from "./subagent-manager.js";
-import { trace, context as otelContext, SpanStatusCode, SpanKind, diag, DiagConsoleLogger, DiagLogLevel } from "@opentelemetry/api";
+import { trace, context as otelContext, createContextKey, type Context as OtelContextType, SpanStatusCode, SpanKind, diag, DiagConsoleLogger, DiagLogLevel } from "@opentelemetry/api";
+import type { Span as OtelSdkSpan, SpanProcessor } from "@opentelemetry/sdk-trace-node";
 import { NodeTracerProvider, BatchSpanProcessor } from "@opentelemetry/sdk-trace-node";
 import { OTLPTraceExporter } from "@opentelemetry/exporter-trace-otlp-http";
+
+// ── Telemetry identity propagation ──────────────────────────────────────────
+// Observability backends (Latitude) resolve a span's session/user from the
+// span's OWN attributes — the console's session & conversation views key on
+// the LLM generation spans, not the root span. So stamping `session.id` /
+// `user.id` only on the invoke_agent root groups the API-level trace but
+// leaves the console treating every turn as its own session. The fix is the
+// same one vendor SDKs use: carry the identity in the OTel Context and have
+// a SpanProcessor stamp it onto EVERY span at start.
+const TELEMETRY_SESSION_ID_KEY = createContextKey("poncho.telemetry.session_id");
+const TELEMETRY_USER_ID_KEY = createContextKey("poncho.telemetry.user_id");
+
+class IdentityAttributeSpanProcessor implements SpanProcessor {
+  onStart(span: OtelSdkSpan, parentContext: OtelContextType): void {
+    const sessionId = parentContext.getValue(TELEMETRY_SESSION_ID_KEY);
+    if (typeof sessionId === "string" && sessionId) {
+      span.setAttribute("session.id", sessionId);
+    }
+    const userId = parentContext.getValue(TELEMETRY_USER_ID_KEY);
+    if (typeof userId === "string" && userId) {
+      span.setAttribute("user.id", userId);
+    }
+  }
+  onEnd(): void {}
+  forceFlush(): Promise<void> {
+    return Promise.resolve();
+  }
+  shutdown(): Promise<void> {
+    return Promise.resolve();
+  }
+}
 import { normalizeOtlp } from "./telemetry.js";
 
 /** Extract useful details from OTLPExporterError (has .code + .data) or plain Error. */
@@ -881,6 +913,8 @@ export class AgentHarness {
   private otlpSpanProcessor?: BatchSpanProcessor;
   private otlpTracerProvider?: NodeTracerProvider;
   private hasOtlpExporter = false;
+  /** End-user id (config.telemetry.userId) stamped as `user.id` on root spans. */
+  private telemetryUserId?: string;
   private _browserSession?: unknown;
   private _browserMod?: {
     createBrowserTools: (getSession: () => unknown, getConversationId?: () => string) => ToolDefinition[];
@@ -1871,6 +1905,7 @@ export class AgentHarness {
 
     const telemetryEnabled = config?.telemetry?.enabled !== false;
     const otlpConfig = telemetryEnabled ? normalizeOtlp(config?.telemetry?.otlp) : undefined;
+    this.telemetryUserId = config?.telemetry?.userId;
     if (otlpConfig) {
       diag.setLogger(new DiagConsoleLogger(), DiagLogLevel.WARN);
       const exporter = new OTLPTraceExporter({
@@ -1880,7 +1915,9 @@ export class AgentHarness {
       const processor = new BatchSpanProcessor(exporter);
       this.otlpSpanProcessor = processor;
       const provider = new NodeTracerProvider({
-        spanProcessors: [processor],
+        // Identity injector FIRST so every span (root, LLM steps, tool
+        // executions) carries session.id/user.id before batching/export.
+        spanProcessors: [new IdentityAttributeSpanProcessor(), processor],
       });
       provider.register();
       this.otlpTracerProvider = provider;
@@ -2057,12 +2094,29 @@ export class AgentHarness {
         kind: SpanKind.INTERNAL,
         attributes: {
           "gen_ai.operation.name": "invoke_agent",
-          ...(input.conversationId ? { "gen_ai.conversation.id": input.conversationId } : {}),
+          // `session.id` / `user.id` are the attributes observability
+          // backends (Latitude) key session grouping and user filtering on.
+          // gen_ai.conversation.id is kept for the GenAI semantic convention.
+          ...(input.conversationId
+            ? {
+                "gen_ai.conversation.id": input.conversationId,
+                "session.id": input.conversationId,
+              }
+            : {}),
+          ...(this.telemetryUserId ? { "user.id": this.telemetryUserId } : {}),
           ...(input.tenantId ? { "tenant.id": input.tenantId } : {}),
         },
       });
 
-      const spanContext = trace.setSpan(otelContext.active(), rootSpan);
+      let spanContext = trace.setSpan(otelContext.active(), rootSpan);
+      // Identity rides the context so IdentityAttributeSpanProcessor stamps
+      // session.id/user.id on every descendant span (see processor docs).
+      if (input.conversationId) {
+        spanContext = spanContext.setValue(TELEMETRY_SESSION_ID_KEY, input.conversationId);
+      }
+      if (this.telemetryUserId) {
+        spanContext = spanContext.setValue(TELEMETRY_USER_ID_KEY, this.telemetryUserId);
+      }
 
       try {
         const gen = this.run(input);