@yagni-app/code-staging 1.0.7-staging.1266.1 → 1.0.7-staging.1267.1

package/README.md

@@ -183,7 +183,10 @@ prefix instead of `claude_code`:
   `yagni_code.llm_request` and `yagni_code.tool`, carrying both the flat
   Claude Code attributes (`model`, `input_tokens`, `cost_usd`, `tool_name`)
   and the OTel GenAI conventions (`gen_ai.*`) that LLM-observability
-  products read. The two count tokens differently on purpose: the flat
+  products read. `gen_ai.operation.name` classifies each span the way those
+  products expect: `invoke_agent` on the interaction root, `chat` on the LLM
+  request, `execute_tool` on tool spans (the turn span has no semconv
+  operation and is left unset). The two count tokens differently on purpose: the flat
   `input_tokens` / `cache_read_tokens` / `cache_creation_tokens` are disjoint,
   exactly as Claude Code reports them, while `gen_ai.usage.input_tokens`
   follows the semconv and includes the cached tokens, with

package/dist/extension/telemetry/tracker.js

@@ -168,9 +168,13 @@ export class SessionTelemetry {
         this.interactionSequence += 1;
         const promptId = randomUUID();
         const promptLength = typeof prompt === "string" ? prompt.length : 0;
+        // `invoke_agent` is the semconv operation for the root of an agent run.
+        // Without it Datadog files the trace as a generic workflow, flags an
+        // instrumentation issue on the span, and leaves it out of per-agent views.
         const span = this.tracer.startSpan(SPAN_INTERACTION, {
             attributes: {
                 ...this.spanAttributes(),
+                [ATTR_GEN_AI_OPERATION_NAME]: "invoke_agent",
                 user_prompt_length: promptLength,
                 "interaction.sequence": this.interactionSequence,
                 "prompt.id": promptId,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yagni-app/code-staging",
-  "version": "1.0.7-staging.1266.1",
+  "version": "1.0.7-staging.1267.1",
   "description": "YAGNI Code: a terminal coding agent that already knows your company. One YAGNI login routes the model and grounds the agent in your team's context.",
   "license": "SEE LICENSE IN LICENSE.md",
   "author": "YAGNI, Inc. <jack@yagni.app> (https://yagni.app)",
@@ -58,5 +58,5 @@
     "turndown": "^7.2.4",
     "typebox": "^1.3.15"
   },
-  "yagniSourceSha": "d1402054944b48117ac873cddd543c7ba14408a0"
+  "yagniSourceSha": "594ebbbef9ba1c2233382184dad54d1e81a3bc0f"
 }