Back to Signal Feed
CodeTracked since May 19, 2026

Fix Copilot auth scope and credential deduplication in oh-my-pi

PR #1210 makes GitHub Copilot login and request handling in oh-my-pi consistent by sending `Copilot-Integration-Id: vscode-chat` on non-auth Copilot API calls and by resolving a stable user `accountId` from `GET /user` during `/login` so existing credential rows can be matched and updated.

oh-my-piGitHub CopilotCopilot-Integration-Idghu_ token

What Happened

  • PR #1210 makes GitHub Copilot login and request handling in oh-my-pi consistent by sending `Copilot-Integration-Id: vscode-chat` on non-auth Copilot API calls and by resolving a stable user `accountId` from `GET /user` during `/login` so existing credential rows can be matched and updated.
  • PR #1210 makes GitHub Copilot login and request handling in oh-my-pi consistent by sending `Copilot-Integration-Id: vscode-chat` on non-auth Copilot API calls and by resolving a stable user `accountId` from `GET /user` during `/login` so existing credential rows can be matched and updated.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implements a concrete authentication reliability fix: it forces the correct Copilot integrator context on Copilot requests and uses GitHub `/user`-provided stable identity data at login to drive dedup logic instead of creating duplicate credentials on each sign-in.

Why Track This

Why It Matters

Developers and operators using oh-my-pi with GitHub Copilot should encounter fewer intermittent "model not available" failures and less credential clutter after login, making Copilot-backed workflows more predictable. By standardizing the integrator header and adding stable `accountId` matching in the credential store, the same user should no longer alternate between incompatible token scopes or accumulate stale rows; continue monitoring for `/user` fetch failures (which silently disable dedup for that login) and for future GitHub changes to token scoping or `/user` response fields that could reintroduce identity mismatch.

Impact

Developers and operators using oh-my-pi with GitHub Copilot should encounter fewer intermittent "model not available" failures and less credential clutter after login, making Copilot-backed workflows more predictable. By standardizing the integrator header and adding stable `accountId` matching in the credential store, the same user should no longer alternate between incompatible token scopes or accumulate stale rows; continue monitoring for `/user` fetch failures (which silently disable dedup for that login) and for future GitHub changes to token scoping or `/user` response fields that could reintroduce identity mismatch.

What To Watch Next

  • Watch whether oh-my-pi becomes a repeated pattern.
  • Track follow-up changes around AI IDE.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: missing_integration_id_in_new_endpoints, get_user_call_failure_disables_dedup.
Open Topic TimelineOpen Technical EventOpen Original Sourcemissing_integration_id_in_new_endpoints / get_user_call_failure_disables_dedup / github_token_scope_behavior_change / identity_resolution_regression

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

can1357/oh-my-pi PR #1210: fix(ai): add Copilot-Integration-Id header and fix credential dedup on login

The patch adds the documented Copilot integration header to model requests and switches login identity matching to use a GitHub `/user` numeric ID, preventing `ghu_`-scoped token misses and repeated credential inserts.