Answer: Set gitHubToken on each session to scope GitHub auth to the requesting user, which differs from a client-level token that authenticates the runtime process. Status: Confirmed Entry: tool/github-copilot/permissions-and-security/sdk-per-session-github-token Revision: 3 Digest: sha256:76c45d68b17083bc (changes whenever the content changes) Timeline: Created: 2026-11-13T03:29:06Z Last changed: 2026-11-19T13:03:18Z (example property: — → gitHubToken : user. githubToken) Last verified: 2026-11-20T13:09:42Z Next check: 2026-11-21T13:09:42Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of method | Set gitHubToken on each session | [1] | 2026-11-20 example property | gitHubToken : user. githubToken | [1] | 2026-11-20 use cases | content exclusion, model routing, quota checks, and user-specific Copilot access | [1] | 2026-11-20 Sources: [1] GitHub. "Multi-tenancy and server deployments - GitHub Docs". https://docs.github.com/en/copilot/how-tos/copilot-sdk/setup/multi-tenancy Role: primary. Accessed: 2026-11-20T13:09:42Z Quote: "Set gitHubToken on each session to scope GitHub auth to the requesting user." (Supports: method) Quote: "gitHubToken : user. githubToken ," (Supports: example property) Quote: "Use per-session tokens for content exclusion, model routing, quota checks, and user-specific Copilot access." (Supports: use cases) Snapshot SHA-256: 6dbc64bdeac84865b2b3899cc72a8e9717530f92eac9c28ee9cd4042f97f4eb5 (captured 2026-11-18T13:05:02Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-18T13:05:04Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:09:42Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:09:42Z Last attempt: 2026-11-20T13:09:42Z Notes and limitations: Extracted automatically from a single official source (section "Per-session gitHubToken"). Related: https://latestn.com/tool/github-copilot/permissions-and-security/sdk-refresh-tokens How do I refresh server-to-server tokens for the GitHub Copilot SDK? https://latestn.com/tool/github-copilot/permissions-and-security/sdk-session-isolation-guarantees What session-level isolation guarantees does the GitHub Copilot SDK provide? https://latestn.com/tool/github-copilot/permissions-and-security/secure-repository How do I secure my repository using GitHub Copilot? https://latestn.com/tool/github-copilot/permissions-and-security/sandbox-policies How do I configure the sandbox filesystem and network policies for GitHub Copilot? https://latestn.com/tool/github-copilot/permissions-and-security/scan-code-vulnerabilities How do I scan code for vulnerabilities during a GitHub Copilot rollout? https://latestn.com/tool/github-copilot/permissions-and-security/sdk-authentication How does authentication work in the GitHub Copilot SDK? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T13:03:18Z | changed | example property: — → gitHubToken : user. githubToken | [1] 2026-11-19T13:03:18Z | changed | example usage: gitHubToken : user. githubToken → — | [1] 2026-11-19T13:03:18Z | changed | distinction: This is different from a client-level token, which authenticates the runtime process. → — | [1] 2026-11-17T13:28:04Z | changed | example usage: — → gitHubToken : user. githubToken | [1] 2026-11-17T13:28:04Z | changed | distinction: — → This is different from a client-level token, which authenticates the runtime process. | [1] 2026-11-17T13:28:04Z | changed | example property: gitHubToken : user. githubToken → — | [1] 2026-11-13T03:29:06Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/permissions-and-security/sdk-per-session-github-token/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/github-copilot/permissions-and-security/sdk-per-session-github-token POST: https://latestn.com/dispute/tool/github-copilot/permissions-and-security/sdk-per-session-github-token with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/permissions-and-security/sdk-per-session-github-token?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I pass a per-session GitHub token in the GitHub Copilot SDK? Revision 3, last verified 2026-11-20T13:09:42Z. https://latestn.com/tool/github-copilot/permissions-and-security/sdk-per-session-github-token (accessed 2026-11-21T09:54:08Z). @misc{LatestN_tool_github_copilot_permissions_and_security_sdk_per_session_github_token_r3, title = {How do I pass a per-session GitHub token in the GitHub Copilot SDK?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/permissions-and-security/sdk-per-session-github-token}}, note = {Revision 3; digest sha256:76c45d68b17083bc; last verified 2026-11-20T13:09:42Z; accessed 2026-11-21T09:54:08Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/github-copilot/permissions-and-security/sdk-per-session-github-token