Skip to content

copilot -p does not emit OTEL telemetry even with server-managed settings overrides #4169

Description

@ek-expd

Describe the bug

Running copilot cli with -p doesn't emit telemetry with server-managed settings:

{
  "telemetry": {
    "enabled": true,
    ...
  }
}

This could also contribute to sessions running under the CLI in the chat window do not show telemetry in IntelliJ:

Image

We need both of these scenarios covered with telemetry.

Affected version

1.0.71

Steps to reproduce the behavior

copilot -p "test"

or in IntelliJ select CLI as the harness and use the chat normally

Expected behavior

OTEL telemetry gets emitted no matter how copilot is triggered when OTEL is forced on in managed settings.

Additional context

No response

Activity

  1. added theissue type on Jul 17, 2026
  2. added
    area:configurationConfig files, instruction files, settings, and environment variables
    area:non-interactiveNon-interactive mode (-p), CI/CD, ACP protocol, and headless automation
    and removed on Jul 18, 2026
  3. jlisee commented on Aug 30, 2026

    @jlisee

    On v1.0.82 I was able to get OTEL traces to exported but only if telemetry.headers was not set:

  4. copilot-cli-bot commented on Oct 5, 2026

    @copilot-cli-bot

    This appears to be resolved as of GitHub Copilot CLI v1.0.91. Please update to that release or a newer stable version. We're closing this as completed. If it still happens, please comment with your version and reproduction steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:configurationConfig files, instruction files, settings, and environment variablesarea:non-interactiveNon-interactive mode (-p), CI/CD, ACP protocol, and headless automation

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions