TLS Observer for OpenCode

OpenCode plugin that converts OpenCode session events into GenAI OTEL traces and exports them to Volcengine TLS.

Trace shape

agent.turn (server)
  llm.request (client)
  tool.call (client)

The plugin listens to OpenCode public plugin events, groups them by user turn, and exports one agent.turn trace when the assistant reaches step-finish reason="stop".

Configuration

Environment variables:

• OPENCODE_TLS_EXPORT=0 disables export.
• OPENCODE_TLS_ENV_FILE optionally points to an env file. Defaults to ~/.config/opencode/tls-observer-opencode.env.
• OPENCODE_TLS_DATA_ROOT overrides local send-log and retry state.
• OPENCODE_TLS_CAPTURE_CONTENT=0 disables prompt/response/tool content capture.
• OPENCODE_TLS_ENDPOINT or TRACE_TLS_ENDPOINT
• OPENCODE_TLS_REGION or TLS_REGION
• OPENCODE_TLS_TRACE_TOPIC_ID or TLS_TRACE_TOPIC_ID
• OPENCODE_TLS_API_KEY or TLS_API_KEY
• OPENCODE_TLS_AK / OPENCODE_TLS_SK or TLS_AK / TLS_SK
• TRACE_OTEL_SPAN_ATTRIBUTES adds custom span attributes, for example session.name:${AIPAAS_SESSION_ID},tenant.id:${TENANT_ID}.

Default data root:

~/.config/opencode/plugins/data/tls-observer-opencode

OpenCode plugin loading

For local installs, place a JavaScript plugin entry file under ~/.config/opencode/plugins/. The installer writes ~/.config/opencode/plugins/tls-observer-opencode.js and keeps the runtime package in ~/.config/opencode/plugins/tls-observer-opencode/.

Design notes

This implementation uses a clean-room OpenCode adapter. It borrows the event-aggregation idea from existing OpenCode tracing integrations, but the code, names, state model, and TLS span mapping are independently implemented for this repository.