[Task] Send copilot-sdk by default from SDK requests
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
Research direction
Start by locating the bundled CLI/runtime launch path and the tests for integration headers, then compare default and host-provided override handling across supported SDK surfaces. Done means default SDK traffic uses the SDK integration ID, explicit overrides remain unchanged, standalone CLI behavior is preserved, and the required tests, DRI, implementation links, and telemetry confirmation are present.
Written by the indexing model from the issue text.
Description
Outcome
The Copilot SDK launches its bundled runtime with Copilot-Integration-Id: copilot-sdk for default SDK traffic while preserving explicit registered integration overrides.
Current problem
The SDK currently inherits the direct CLI default and sends copilot-developer-cli unless the host sets GITHUB_COPILOT_INTEGRATION_ID. CAPI therefore classifies default SDK traffic as direct CLI traffic. Copilot-Harness-Id: copilot-sdk does not solve this because the SDK and standalone CLI share that harness value.
SDK team ownership
The Copilot SDK team owns the launch-path behavior in this issue. Assign an SDK engineering DRI before implementation and link the implementation pull requests for every affected language or shared launcher.
Scope
- Set
GITHUB_COPILOT_INTEGRATION_ID=copilot-sdkwhen the SDK launches the bundled CLI or runtime and the host did not provide an explicit integration override - Preserve host-provided registered integration IDs exactly
- Apply the behavior consistently across supported SDK language surfaces or in the shared launch layer used by them
- Keep standalone Copilot CLI defaulting to
copilot-developer-cli - Keep
Copilot-Harness-Idas supporting telemetry only - Coordinate rollout and compatibility normalization with github/copilot-api#37988
Acceptance criteria
- Default SDK requests send
Copilot-Integration-Id: copilot-sdk - A host-provided registered integration override remains effective
- Standalone CLI requests continue to send
copilot-developer-cli - Tests cover default behavior and explicit overrides across supported SDK launch paths
- An SDK engineering DRI and implementation pull request are linked here
- CAPI telemetry confirms default SDK traffic transitions from
copilot-developer-clitocopilot-sdk
Dependencies and references
- Parent epic github/copilot#30409
- SDK App-token plumbing github/copilot#30423
- CAPI integration allowlist and migration github/copilot-api#37988
- ADR github/copilot#30449
- Dominant language
- Java
- Stars
- 10.5k
- Forks
- 1.5k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 130
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/copilot-sdk
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/copilot-sdk#2760 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/copilot-sdk#2759 ·
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
github/copilot-sdk#2758 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/copilot-sdk#2709 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
github/copilot-sdk#2673 ·
All issues in github/copilot-sdk
Similar issues
-
awaiting triage bug Causes friction Hop Gui P1 P2 Transforms
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
apache/flink-agents#1152 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
jenkinsci/blueocean-plugin#5417 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
objectionary/eo-graphs#75 ·