Answer: To scale GitHub Copilot SDK CLI servers horizontally behind a load balancer, session state must be on shared storage so any CLI server can resume any session. You can use sticky sessions (pinning users to specific servers, no shared storage needed) or shared storage (any CLI can handle any session, requiring networked storage for ~/.copilot/session-state/). Status: Confirmed Entry: tool/github-copilot/admin-and-enterprise/horizontal-scaling-load-balancer Revision: 3 Digest: sha256:52cb6d9c36f291d0 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:29:07Z Last changed: 2026-11-18T13:05:06Z (Example server addresses: — → cli-1:4321) Last verified: 2026-11-20T13:09:44Z Next check: 2026-11-21T13:09:44Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Key requirement | Session state must be on shared storage so any CLI server can resume any session. | [1] | 2026-11-20 Sticky sessions | Sticky sessions are simpler—pin users to specific CLI servers. | [1] | 2026-11-20 Sticky sessions tradeoff | No shared storage needed, but load distribution is uneven. | [1] | 2026-11-20 Shared storage tradeoff | Better load distribution, but requires networked storage for ~/.copilot/session-state/ . | [1] | 2026-11-20 Example server addresses | cli-1:4321 | [1] | 2026-11-20 Sources: [1] GitHub. "Scaling and multi-tenancy - GitHub Docs". https://docs.github.com/en/copilot/how-tos/copilot-sdk/setup/scaling Role: primary. Accessed: 2026-11-20T13:09:44Z Quote: "Key requirement: Session state must be on shared storage so any CLI server can resume any session." (Supports: Key requirement) Quote: "Sticky sessions are simpler—pin users to specific CLI servers." (Supports: Sticky sessions) Quote: "No shared storage needed, but load distribution is uneven." (Supports: Sticky sessions tradeoff) Quote: "Better load distribution, but requires networked storage for ~/.copilot/session-state/ ." (Supports: Shared storage tradeoff) Quote: "const lb = new CLILoadBalancer ([ "cli-1:4321" , "cli-2:4321" , "cli-3:4321" , ]);" (Supports: Example server addresses) Snapshot SHA-256: 96b1b58fa8254d1669f66715dcf15624502f5b4e5959224d02eeeb61424d8706 (captured 2026-11-18T13:05:06Z) 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:06Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:09:44Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:09:44Z Last attempt: 2026-11-20T13:09:44Z Notes and limitations: Extracted automatically from a single official source (section "Horizontal scaling"). Related: https://latestn.com/tool/github-copilot/admin-and-enterprise/how-plugin-standards-work How do GitHub Copilot enterprise-managed plugin standards work? https://latestn.com/tool/github-copilot/admin-and-enterprise/identify-app-usage How do I identify which GitHub Apps are using my organization's Copilot? https://latestn.com/tool/github-copilot/admin-and-enterprise/impact-dashboard-access Who can access the GitHub Copilot impact dashboard? https://latestn.com/tool/github-copilot/admin-and-enterprise/grant-copilot-access-to-members How do I grant organization members access to GitHub Copilot? https://latestn.com/tool/github-copilot/admin-and-enterprise/grant-copilot-access-via-api How can I use the API to grant GitHub Copilot access in my organization? https://latestn.com/tool/github-copilot/admin-and-enterprise/grant-copilot-licenses How do I grant GitHub Copilot licenses to users in my organization? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T13:05:06Z | changed | Example server addresses: — → cli-1:4321 | [1] 2026-11-18T13:05:06Z | changed | Shared storage tradeoff: — → Better load distribution, but requires networked storage for ~/.copilot/session-state/ . | [1] 2026-11-18T13:05:06Z | changed | Sticky sessions tradeoff: — → No shared storage needed, but load distribution is uneven. | [1] 2026-11-18T13:05:06Z | changed | Sticky sessions: — → Sticky sessions are simpler—pin users to specific CLI servers. | [1] 2026-11-18T13:05:06Z | changed | Key requirement: — → Session state must be on shared storage so any CLI server can resume any session. | [1] 2026-11-18T13:05:06Z | changed | example server ports: cli-1:4321 → — | [1] 2026-11-18T13:05:06Z | changed | shared storage tradeoff: Shared storage enables any CLI to handle any session. Better load distribution, but requires networked storage for ~/.copilot/session-state/ . → — | [1] 2026-11-18T13:05:06Z | changed | sticky sessions tradeoff: Sticky sessions are simpler—pin users to specific CLI servers. No shared storage needed, but load distribution is uneven. → — | [1] 2026-11-18T13:05:06Z | changed | key requirement: Session state must be on shared storage so any CLI server can resume any session. → — | [1] 2026-11-16T12:53:46Z | changed | example server ports: — → cli-1:4321 | [1] 2026-11-16T12:53:46Z | changed | shared storage tradeoff: — → Shared storage enables any CLI to handle any session. Better load distribution, but requires networked storage for ~/.copilot/session-state/ . | [1] 2026-11-16T12:53:46Z | changed | shared storage benefit: Better load distribution, but requires networked storage → — | [1] 2026-11-16T12:53:46Z | changed | sticky sessions tradeoff: No shared storage needed, but load distribution is uneven. → Sticky sessions are simpler—pin users to specific CLI servers. No shared storage needed, but load distribution is uneven. | [1] 2026-11-16T12:53:46Z | changed | shared storage path: ~/.copilot/session-state/ → — | [1] 2026-11-13T03:29:07Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/admin-and-enterprise/horizontal-scaling-load-balancer/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/admin-and-enterprise/horizontal-scaling-load-balancer POST: https://latestn.com/dispute/tool/github-copilot/admin-and-enterprise/horizontal-scaling-load-balancer with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/admin-and-enterprise/horizontal-scaling-load-balancer?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I scale GitHub Copilot SDK CLI servers horizontally behind a load balancer? Revision 3, last verified 2026-11-20T13:09:44Z. https://latestn.com/tool/github-copilot/admin-and-enterprise/horizontal-scaling-load-balancer (accessed 2026-11-21T09:58:05Z). @misc{LatestN_tool_github_copilot_admin_and_enterprise_horizontal_scaling_load_balancer_r3, title = {How do I scale GitHub Copilot SDK CLI servers horizontally behind a load balancer?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/admin-and-enterprise/horizontal-scaling-load-balancer}}, note = {Revision 3; digest sha256:52cb6d9c36f291d0; last verified 2026-11-20T13:09:44Z; accessed 2026-11-21T09:58:05Z} } 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/admin-and-enterprise/horizontal-scaling-load-balancer