GitHub’s Copilot now persists cloud sessions and follows you across devices

What changed: GitHub announced a connected Copilot cloud experience that preserves a cloud-backed session (code, context, and agent work) so you can start a task in one surface and continue it on another (web, mobile, Copilot CLI, VS Code, Slack/Teams).

Why it matters: Instead of re-creating repository state or re-running setup when you switch devices, engineers can hand longer-running inspections, test runs, or PR drafts to a cloud-backed agent and pick up where they left off, reducing context-rebuild time and friction for distributed teams.

Try/watch: Try a short pilot that sends a non-sensitive, reproducible task (failing tests → agent investigates → proposed PR) through the cloud session flow to measure saved developer time and any surprises in persisted state visibility.

Copilot adds connect-once MCP connectors (public preview) for 26 services

What changed: GitHub published a public-preview update adding “connect-once” MCP-style connectors for about 26 third-party services (Slack, Figma, Notion, Sentry, Linear, Cloudflare, Vercel, etc.), letting a single sign-in authorize those services across Copilot surfaces and sessions.

Why it matters: For builders and ops teams this reduces per-surface auth friction and makes agent tool-calls more practical (agents can reach the same connected services whether run from CLI, IDE, mobile, or the cloud), but it also centralizes an access vector you should secure and audit.

Try/watch: If you manage Copilot seats, review your connector allowlist and test connector revocation flows — confirm org admin settings (e.g., Editor preview features, MCP allowlists) behave as expected before broad rollout.