Verification cutoff: August 30, 2026, daily edition.

Executive Summary

GitHub has announced a September 28 transition that unifies Copilot Chat on github.com, Copilot Chat in GitHub Mobile and the Copilot cloud agent. The practical issue is data retention: chat data in the unified experience will remain for the life of the account instead of 28 days. Separately, GitHub’s new Microsoft Teams integration turns channel discussions into visible, steerable cloud-agent sessions. The first change warrants a policy review; the second is worth a carefully bounded trial, not immediate classroom deployment.

Action Queue

1. Review Copilot’s unified-experience policy before September 28

Urgency: This week
Importance: ★★★★★

What it is: No earlier than September 28, GitHub plans to relaunch Copilot Chat on github.com, Copilot Chat in GitHub Mobile and the GitHub Copilot cloud agent under one experience and policy. It will be enabled by default. GitHub says chat data in the unified experience will be retained for the life of the account rather than 28 days.

Why it matters: A longer retention period changes the privacy boundary for prompts that may contain repository context, draft code, logs or operational details. Organizations also face an access tradeoff: opting out removes Copilot access on github.com and GitHub Mobile after launch.

Recommended action: Review personal and organization Copilot settings, identify repositories where persistent chat context is inappropriate, and document what information must never be pasted into Copilot. Organization administrators should explicitly choose the cloud-agent policy instead of inheriting the default.

Verified active: August 30, 2026; GitHub’s August 28 announcement was checked.
Deadline: Review before September 28, 2026. The launch is scheduled no earlier than that date.
Cost: No fee for reviewing settings. Copilot subscription and usage charges depend on the selected plan; this announcement does not change plan prices.
Requirements: A GitHub account using Copilot on github.com, GitHub Mobile or the cloud agent; organization policy changes require administrator access.
Official action/information: GitHub’s Copilot policy and billing announcement · Copilot settings

2. Trial shared Copilot agent sessions in Microsoft Teams

Urgency: This week
Importance: ★★★★☆

What it is: GitHub’s public preview lets a Teams conversation start a shared Copilot cloud-agent session by mentioning @GitHub. Participants can add context and steer the investigation; repository collaborators with write access can authorize changes.

Why it matters: This could turn a faculty or project-channel discussion into traceable repository work without hiding the agent’s reasoning in one person’s private session. The same visibility makes it useful for demonstrating human oversight, permissions and asynchronous agent work.

Recommended action: Test the integration in a private Teams channel against a disposable repository. Give participants read access first, set a small AI-credit and sandbox budget, require an extra approval for Copilot-authored pull requests, and inspect every artifact before granting broader write authority.

Verified active: August 30, 2026; GitHub’s August 21 release and August 28 weekly roundup were checked.
Deadline: None; public preview availability may change.
Cost: Requires a paid GitHub Copilot plan. Cloud-agent sessions consume AI credits, and cloud sandbox use is billed separately; GitHub says both can be governed by budgets. Regular price varies by plan and usage.
Requirements: Microsoft Teams, the GitHub app for Teams, a connected GitHub account, a paid Copilot plan, and administrator enablement for organization-managed cloud agents and sandboxes.
Official access/information: Shared Copilot work in Microsoft Teams · GitHub Copilot weekly release roundup · GitHub Copilot pricing

Official GitHub screenshot of a shared Copilot session in Microsoft Teams.

GitHub Discoveries

The Teams preview introduces an important control: repository administrators can require one additional approval before a pull request attributed to the Teams Copilot integration may merge. That control should be enabled before agents receive write access.

PKb Candidates

• AI chat retention register: record each assistant’s retention period, account-lifecycle behavior, opt-out effect and prohibited data classes.
• Shared-agent deployment gate: disposable repository, least privilege, explicit budget, human approval, audit trail and revocation procedure.
• Agent-channel etiquette: distinguish investigation, planning and authorized mutation so a conversational mention cannot silently broaden scope.

Trends Worth Watching

Agent interfaces are moving into collaboration channels while their histories are becoming more durable. That combination improves continuity but also makes channel membership, repository permissions, retention and budget controls part of the software-development security model.

Related PTIR Coverage

• Daily Briefing — August 29, 2026 — physical-agent boundaries, UniFi patching and Grafana staging.
• Daily Briefing — August 27, 2026 — agent containment and account-takeover risk.

Sources Consulted

GitHub’s August 28 Copilot policy announcement, August 28 weekly release roundup and August 21 Microsoft Teams integration announcement; selected technology newsletters; the latest PTIR edition; and read-only searches of the legacy recipient stream, Spam and Trash. GitHub’s official Teams screenshot was selected because it shows the shared-agent workflow rather than serving as decoration.