Repository navigation
[FEATURE]: Support enforced OTLP settings in managed configuration #47351
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
OpenCode supports system-managed configuration and macOS managed preferences, but its OTLP exporter is configured only through inherited environment variables:
OTEL_EXPORTER_OTLP_ENDPOINTOTEL_EXPORTER_OTLP_HEADERSOTEL_RESOURCE_ATTRIBUTES
This means an administrator cannot enforce an OTLP destination through /etc/opencode, %ProgramData%\opencode, or an ai.opencode.managed MDM profile. A user can unset or replace the environment variables when launching OpenCode.
Add dedicated managed OTLP settings:
{
"telemetry": {
"otlp": {
"endpoint": "https://otel.example.com",
"headers": "Authorization=Bearer token",
"resourceAttributes": "deployment.environment.name=production"
}
},
"experimental": {
"openTelemetry": true
}
}Values present in the macOS ai.opencode.managed profile should have the highest precedence and should not be overridable by system-managed files, inherited environment variables, user configuration, or project configuration. For values omitted from the profile, the system-managed file should take precedence over inherited OTEL_* variables. Precedence should be evaluated per setting.
A dedicated OTLP block is preferable to a general managed env dictionary because it limits the capability to exporter settings OpenCode already supports.
Activity
github-actions commentedon Sep 4, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:(e.g.[FEATURE]: Support enforced OTLP settings in managed configuration)Please edit this issue to address the above within 2 hours, or it will be automatically closed.
If you believe this was flagged incorrectly, please let a maintainer know.
[-]Support enforced OTLP settings in managed configuration[/-][+][FEATURE]: Support enforced OTLP settings in managed configuration[/+]lennyvaknine43 commentedon Sep 4, 2026
Updated the title and body to use the feature-request format and added the required duplicate-verification checkbox.
github-actions commentedon Sep 4, 2026
Thank you for updating the issue! It now follows the feature request template and includes a clear description of the problem and proposed solution. The needs:compliance label has been removed.
opencodejr commentedon Oct 28, 2026
Thanks for the detailed request, @lennyvaknine43! You're asking for dedicated
telemetry.otlpsettings (endpoint, headers, resource attributes) in managed configuration, so that administrators can enforce an OTLP destination through system-managed files or the macOSai.opencode.managedprofile. Precedence would be evaluated per setting, and users wouldn't be able to override these values withOTEL_*environment variables or their own config.I checked the current v2 code. The exporter is configured only from
OTEL_EXPORTER_OTLP_ENDPOINT/OTEL_EXPORTER_OTLP_HEADERSwhen the CLI starts, so this isn't possible today. A plugin can't fill the gap either: it loads after the exporter is set up, and the user could disable it.Related issues and PRs:
OTEL_*resource variables being ignored (closed)Maintainers will consider this request.