Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Test: Managed Copilot OTel file export

Open Beginner friendly
  • Is something wrong?
#342,454 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
66/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
observability, testing

Research direction

Start with the managed-settings file paths and the verification steps in this issue. Follow the listed VS Code setup, write the managed telemetry.filePath setting, and check whether the JSONL file contains invoke_agent and vscode.agent_host.session. Remove filePath, restart Agent Host, and verify the file is absent or empty; restore or delete the settings file during cleanup.

Written by the indexing model from the issue text.

Description

testplan-item

Refs: #340964

  • anyOS

Complexity: 3

Setup

  • Use a disposable profile and workspace.
  • Delete the managed settings file (take a backup before deleting so you can restore this if you want)
    • macOS: /Library/Application Support/GitHubCopilot/managed-settings.json
    • Linux: /etc/github-copilot/managed-settings.json
    • Windows: %ProgramFiles%\GitHubCopilot\managed-settings.json

Verify that managed telemetry.filePath:

  1. exports Copilot Agent Host telemetry to a JSONL file without personal OTel
    opt-in; and
  2. stops exporting after the managed setting is removed.

This TPI intentionally uses the device-wide managed-settings.json file. It is
the simplest way to test the setting: no proxy, mock policy server, SDK policy
cache, or OTLP collector is required. It validates file-based managed-settings
delivery, not GitHub server delivery.

Steps

  1. Exit all instances of VS Code
  2. Start an instace of VS Code in a transient location or disable all OTel related temetry as follows in your use settings.json file
{
  "chat.agentHost.otel.enabled": false,
  "chat.agentHost.otel.dbSpanExporter.enabled": false
}
  1. Restart VS Code (that you started in step 2) and ensure you are signed into Copilot and all other instances of VS Code and Copilot CLI have been killed
  2. Ensure all windows (and agent sessions have been closed in VS Code)
  3. Update the managed-settings.json file (see above for path) with the following content
{
  "telemetry": {
    "filePath": "<fully qualified path to a temp location>/copilot-otel.jsonl",
    "captureContent": false,
    "capture": {
      "identity": false
    }
  }
}
  1. Select the command Developer: Restart Local Agent Host from the command palette
  2. Now start a new agent session and send the prompt Reply exactly MANAGED_FILE_OK. Do not use tools.
  3. Wait for the session to compete and verify you get a response back of MANAGED_FILE_OK
  4. Verify the file is created <fully qualified path to a temp location>/copilot-otel.jsonl
  5. Verify the file contains the text invoke_agent.
  6. Verify the file contains the textvscode.agent_host.session.
  7. Go back to the managed-settings.json and remove the filePath setting
  8. Go back into VS Code and Close all of your agent host sessions in VS Code
  9. Go back into VS Code and restart Agent Host as in step 5
  10. Clear the contents or delete the file <fully qualified path to a temp location>/copilot-otel.jsonl
  11. Start a new agent session and send the prompt Reply exactly MANAGED_FILE_OK. Do not use tools. and wait for completion
  12. Verify the file is not created or is empty

Cleanup and results

  1. Restore (from backup) or delete the local managed-settings.json file created/edit earlier
Dominant language
TypeScript
Stars
194k
Forks
45.8k
Avg merge
10h 37m
Merged PRs (30d)
688

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode

All issues in microsoft/vscode

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.