Did GitHub relaunch Copilot Chat and cloud agent under one policy?

Did GitHub relaunch Copilot Chat and cloud agent under one policy

Yes. GitHub says Copilot Chat on github.com, Copilot Chat in GitHub Mobile, and Copilot cloud agent will relaunch as one unified experience with one policy replacing the separate policies. GitHub’s own changelog says this happens no earlier than September 28, 2026, so the policy change is part of the relaunch, not a side note.

The part people get wrong is treating Chat and cloud agent as two separate products with separate governance forever. GitHub’s update says the three surfaces are converging into a single experience, and the separate policies will be replaced by a single policy. That means administrators should read the new policy as the control point for access, not the old split model.

The inconvenient part is that opting out has a cost. GitHub says the unified experience will be enabled by default after launch, and if you opt out, you or your teams will lose access to Copilot on github.com and GitHub Mobile after the new experience launches. That makes the policy decision operational, not cosmetic.

GitHub also says the relaunch changes how data is handled. Copilot on github.com will move to the agent sessions experience previously used by cloud agent, and chat data will be retained for the life of the account instead of 28 days. That is a meaningful product change, because the chat surface is no longer just chat in the old sense.

The cleanest way to think about it is that GitHub is unifying surface, policy, and session model. The changelog says cloud agent will leverage Sandbox for a faster cloud experience, and Copilot on github.com will fully migrate to the agent sessions experience. In practice, this is a governance merge as much as a user interface merge.

If you administer Copilot for a business or enterprise, the question is not whether the relaunch is real. It is whether your current policy language matches the unified policy before the launch date GitHub named. GitHub explicitly tells admins to review the policy before September 28, 2026 and confirm that it reflects how they want to manage access.

A practical example shows why this matters. Suppose your org wants Chat available but is still deciding about cloud agent behavior. Under the unified model, the policy no longer behaves like two separate switches with independent outcomes. If you leave the policy unchanged and stay opted in, GitHub says the unified experience stays available by default.

That same example also shows the risk of misreading the change. A team might assume the old 28 day chat retention still applies because they only think about Chat, not agent sessions. GitHub’s announcement says the migrated chat data follows the life of the account, which is a different retention model and should be treated that way in internal policy reviews.

For readers comparing this to earlier Copilot policy changes, the important detail is that GitHub has been moving toward more shared governance across surfaces. The related changelog entries show dedicated policy controls for the Copilot app and enterprise managed settings for Copilot app and cloud agent, which makes the unified policy announcement consistent with GitHub’s broader direction. The pattern is not one-off branding, it is consolidation of controls.

If you are documenting this for a team, the shortest accurate phrasing is: GitHub did announce a relaunch that puts Copilot Chat and cloud agent under one policy. The official changelog uses the word unified, says the separate policies will be replaced, and ties the change to a specific launch window. That is the current answer.

If you need the exact operational next step, it is to review the Copilot policy in GitHub settings before the launch date GitHub gave. If your team wants to keep access on github.com and GitHub Mobile after the new experience ships, GitHub says staying opted in is the path that preserves access. If you opt out, the access loss is the consequence GitHub documented.

For teams using DevConnect alongside Copilot, the policy lesson is the same: the thing that looks like a UI change can actually be a governance change. DevConnect stays free and is built for reciprocal testing, while GitHub’s Copilot update is about how one policy now governs multiple Copilot surfaces. Those are different products, but the operational habit is the same, read the policy before the rollout, not after it bites.

If you want to keep this page aligned with the official wording, use GitHub’s own terms, unified experience, single policy, and no earlier than September 28, 2026. Those phrases matter because they tell you this is an announced relaunch with a policy merge, not a rumor about a future roadmap item.