GitHub plans one Copilot policy for github.com, Mobile and cloud agent
GitHub says Copilot Chat on github.com, Copilot Chat in GitHub Mobile and Copilot cloud agent will converge into one experience and a single policy no earlier than 28 September 2026; the unified experience will be enabled by default after launch.
Unified policy transition scheduled
Commercial transition
Previous stateBefore the planned unified launch, Copilot cloud agent, Copilot Chat on github.com and Copilot Chat in GitHub Mobile use separate policies, and github.com chat data is retained for 28 days.
→
New stateGitHub plans to converge the three named Copilot surfaces into one experience governed by a single policy. After launch the unified experience is enabled by default; administrators that opt out cause users or teams to lose Copilot access on github.com and GitHub Mobile. GitHub also says github.com chat data will move from 28-day retention to account-lifetime retention as the experience migrates to agent sessions.
Who is affected
Organisations and administrators governing GitHub Copilot access on github.com, GitHub Mobile and Copilot cloud agent, plus users whose access and chat-retention behaviour follow that policy.
Action required
Review the unified Copilot policy before the no-earlier-than 28 September launch boundary and decide whether to retain the default-enabled experience or opt out with the documented access consequences.
Evidence boundary
GitHub proves the planned policy/access and retention transition for the named Copilot surfaces. It does not establish a price change and does not claim the transition occurs before the stated no-earlier-than 28 September boundary.
Timeline
Unified policy transition announced
GitHub announced convergence of github.com, Mobile and cloud-agent Copilot experiences and policy controls.
Earliest stated launch date
GitHub says the unified experience will launch no earlier than 28 September 2026.