GitHub Copilot Connectors Preview: Control Permissions After One-Time Slack, Figma, or Notion Setup

[[zh]][[/zh]][[en]]Review a public website[[/en]]

SearchScope SEO/GEO

[[zh]][[/zh]][[en]]Access and usage guide[[/en]]

AI Prompt Management System | 418 Bilingual Prompts for Writing, SEO and AI Creation

High-Frequency AI Prompts for Work, Learning, and Teaching guide

High-Frequency AI Prompts for Work, Learning, and Teaching

GitHub Copilot Usage API Names Custom Skills, Agents, and MCP Servers: How to Read the Report

GitHub updated the Copilot usage metrics API on October 22, 2026, so customer-defined skills, agents, MCP servers, slash commands, and plugins can appear by configured name instead of being grouped entirely under other or custom. Each totals_by_* list now includes as many as 25 entries per record, up from five. This article helps administrators turn the change into a reliable adoption report. It covers required Copilot CLI and SDK versions, a naming review before reports are shared, one-day and 28-day comparisons, and a reconciliation check against known pilots. It also explains why historical days, path-like names, outdated clients, and blocked telemetry can still undercount activity. The metrics are useful for trends and enablement, not exact billing.

GitHub Copilot Cloud Sessions Are GA: How Cross-Device Work Uses Actions Entitlement

GitHub made its connected Copilot cloud experience and cloud sandboxes generally available on paid Copilot plans on October 28, 2026. A user can start a task on github.com, GitHub Mobile, Copilot CLI, the Copilot app, VS Code, Slack, or Microsoft Teams, then continue the same session elsewhere. The included Actions compute entitlement becomes one shared, dollar-based pool for standard hosted runners, cloud sandboxes, and certain larger runners. Billing for cloud-sandbox usage begins in November 2026, so cross-device convenience can affect the same budget used by builds. This article helps users check repository scope, write access, tool permissions, entitlement consumption, and stop conditions before their first cloud session.

GitHub Copilot Repository Plugin Defaults Are GA: Prevent Permission Drift Across Teams

GitHub made repository plugin defaults and enterprise-managed plugin controls generally available in VS Code, Copilot CLI, and the GitHub Copilot app on October 28, 2026. A maintainer can define a marketplace and default plugins for a trusted repository so contributors avoid repeating setup. Enterprise administrators can require or block plugins and restrict installation to approved marketplaces. Managed settings take precedence over repository and personal choices, and a required plugin cannot be disabled by the user. This article gives teams a rollout checklist for validating publisher identity, plugin contents, MCP connections, credentials, uninstall behavior, repository trust, and the difference between a convenient default and a mandatory enterprise control.

What Is Replica? A Validation Guide for AI Prototypes Built From Your Design System

Replica is an open-source AI prototyping tool released by GitHub Design on October 28, 2026. It uses a team’s existing components, patterns, and documentation to guide interactive prototypes instead of starting from a generic visual language. Team members can describe and refine a prototype through the GitHub Copilot app, begin locally, and optionally deploy a self-hosted Replica Hub for review and comments. The project is available under the MIT license. This durable guide explains the required design-system inputs, a small example task, expected outputs, consistency checks, feedback handling, and failure recovery so a prototype can inform product discussion without being presented as production code or a tested interface.

GitHub Copilot Memory Is GA: Check and Delete Context Before Enabling Dreaming

GitHub announced GitHub intelligence on October 28, 2026. Copilot Memory is generally available on paid plans, Dreaming is an opt-in public preview, and code search can reach related repositories and dependencies. Dreaming may add, update, or remove personal and repository memories, while proposed changes to checked-in skills and instructions arrive as pull requests for team review. Dream runs consume AI credits. This article gives developers a practical way to inspect and delete saved preferences, separate personal from repository context, limit repository access, and decide whether Dreaming and cross-repository search belong in a low-risk trial before broader adoption. The trial remains reversible.

GitHub Issue Artifacts Preview: What Agent Outputs Can Store and How Version History Works

GitHub announced Issue Artifacts in public preview on October 28, 2026. Teams can attach agent-generated plans, research, links, visualizations, and interactive HTML directly to an issue. Updates made on github.com retain version history as an artifact changes. GitHub CLI adds gh issue artifact commands to create, edit, list, view, download, and delete artifacts, while Markdown artifacts can include image and video attachments. This explainer uses a root-cause-analysis example to show which outputs belong beside an issue, how to separate observed evidence from unverified conclusions, when history helps reviewers follow a decision, and when an incorrect or sensitive artifact should be corrected or removed rather than being treated as repository truth.

GitHub official source (2026-10-28)