@poncho-ai/sdk 1.12.0 → 1.13.0

package/.turbo/turbo-build.log

@@ -1,5 +1,5 @@
 
-> @poncho-ai/sdk@1.12.0 build /home/runner/work/poncho-ai/poncho-ai/packages/sdk
+> @poncho-ai/sdk@1.13.0 build /home/runner/work/poncho-ai/poncho-ai/packages/sdk
 > tsup src/index.ts --format esm --dts
 
 CLI Building entry: src/index.ts
@@ -8,7 +8,7 @@
 CLI Target: es2022
 ESM Build start
 ESM dist/index.js 17.24 KB
-ESM ⚡️ Build success in 20ms
+ESM ⚡️ Build success in 21ms
 DTS Build start
-DTS ⚡️ Build success in 1257ms
-DTS dist/index.d.ts 29.41 KB
+DTS ⚡️ Build success in 1513ms
+DTS dist/index.d.ts 29.81 KB

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # @poncho-ai/sdk
 
+## 1.13.0
+
+### Minor Changes
+
+- [`773f113`](https://github.com/cesr/poncho-ai/commit/773f11309e2410d6c5e17af0fde17425953105f2) Thanks [@cesr](https://github.com/cesr)! - harness: add a per-run `suppressTelemetry` flag so one harness can serve both telemetry-on and telemetry-off runs.
+
+  Telemetry was effectively an instance-level property: whether the OTLP exporter is attached is decided at construction, so a host that wants telemetry-off runs (e.g. incognito) had to build and maintain a _second_ harness instance with no exporter — duplicating all per-harness provisioning (tool registration, subagent manager, etc.) and risking drift between the two.
+
+  `RunInput.suppressTelemetry` lets a single harness — built once, with the exporter attached — emit nothing for a given run: the `invoke_agent` root span, the `execute_tool` spans, and the AI-SDK spans are all gated on `!input.suppressTelemetry`. Hosts can now keep one harness per user and pass `suppressTelemetry: true` per run instead of routing to a parallel exporter-less instance.
+
 ## 1.12.0
 
 ### Minor Changes

package/dist/index.d.ts

@@ -756,6 +756,14 @@ interface RunInput {
     disablePromptCache?: boolean;
     /** Scope this run to a specific tenant. */
     tenantId?: string;
+    /**
+     * When true, emit no telemetry for this run — no `invoke_agent` /
+     * `execute_tool` spans and no AI-SDK spans, even on a harness built with an
+     * OTLP exporter attached. Lets a single harness serve both telemetry-on and
+     * telemetry-off (e.g. incognito) runs, instead of needing a separate
+     * exporter-less harness instance per mode.
+     */
+    suppressTelemetry?: boolean;
 }
 interface TokenUsage {
     input: number;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@poncho-ai/sdk",
-  "version": "1.12.0",
+  "version": "1.13.0",
   "description": "Core types and utilities for building Poncho skills",
   "repository": {
     "type": "git",

package/src/index.ts

@@ -137,6 +137,14 @@ export interface RunInput {
   disablePromptCache?: boolean;
   /** Scope this run to a specific tenant. */
   tenantId?: string;
+  /**
+   * When true, emit no telemetry for this run — no `invoke_agent` /
+   * `execute_tool` spans and no AI-SDK spans, even on a harness built with an
+   * OTLP exporter attached. Lets a single harness serve both telemetry-on and
+   * telemetry-off (e.g. incognito) runs, instead of needing a separate
+   * exporter-less harness instance per mode.
+   */
+  suppressTelemetry?: boolean;
 }
 
 export interface TokenUsage {