opencode run: OTel spans lost because AppRuntime is not disposed before process.exit()

[astefanutti]

Summary

opencode run never emits OTel spans to an OTLP collector because process.exit() in the finally block of index.ts kills the process before the BatchSpanProcessor can flush its buffer.

The AppRuntime wraps a ManagedRuntime whose Observability.layer initializes the OTel NodeSdk with a BatchSpanProcessor. Disposing the runtime would trigger the SDK's shutdown() → forceFlush() chain, but AppRuntime.dispose() is never called.

Root cause

In packages/opencode/src/index.ts:

} finally {
  process.exit() // kills pending async ops including span export
}

Fix

Call await AppRuntime.dispose() before process.exit():

} finally {
  await AppRuntime.dispose().catch(() => {})
  process.exit()
}

Reproduction

1. Start a local OTLP collector on localhost:4318
2. Run: OTEL_EXPORTER_OTLP_ENDPOINT=http://127.0.0.1:4318 opencode run --format json "Say hi"
3. Observe: 0 spans received by the collector

Related: #13438

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• fix: opencode run does not emit OTLP traces even with experimental.openTelemetry enabled #13438: Same symptom — opencode run does not emit OTel spans to an OTLP collector, even with the relevant env vars set. Your root cause analysis (missing AppRuntime.dispose() before process.exit()) may explain that issue as well.

If this is the same underlying problem, consider contributing the fix to the existing issue or linking them.

[astefanutti]

Yes, this is the root cause of #13438. The fix is in #30089 — one-line change to dispose the runtime before process.exit().