GitHub adds a package firewall, named agent metrics and refreshable CLI credentials

Three October releases strengthen dependency controls, make internal AI customisations visible and simplify expiring GitHub CLI authentication.

GitHub's releases from 20 to 22 October focus on the operational work surrounding coding agents: the packages they install, the customisations developers use and the credentials that connect local tools to the platform. Each addresses a different part of an increasingly automated software workflow.

Dependency policy at installation time

The new package firewall entered public preview on 20 October for GitHub Enterprise Cloud, including data-resident enterprises. It sits between development endpoints or internal registries and upstream package repositories. Administrators can set a cooldown for new packages, check advisory information and apply supply-chain controls such as attestation-downgrade checks.

Both package metadata requests and downloads pass through the policy gate. A user can request an exception when a legitimate package is blocked. GitHub says preview usage is free; general availability will use metered billing. This positions dependency policy at the point where an agent or CI runner attempts an installation.

Seeing the tools teams actually use

A 22 October change expands Copilot usage reporting. Customer-defined skills, agents, MCP servers, slash commands and plugins now appear by their configured names instead of being grouped entirely as custom or other. Relevant arrays can contain up to 25 entries, up from five, with remaining activity combined into an other entry.

Interaction counts keep their existing calculation. Supported CLI, application, SDK and ACP surfaces have minimum client-version requirements. The result gives enablement teams a clearer view of adoption: an internal code-review skill and a documentation MCP server can be tracked separately after rollout.

Credentials that refresh in the background

GitHub CLI's 21 October public preview introduces opt-in expiring OAuth credentials. From version 2.103.0, users can request them with `gh auth login --expiring`, or enable the preference in CLI configuration. The CLI stores the expiring access credential and a rotating refresh credential, refreshing access when needed.

For HTTPS Git operations, GitHub recommends configuring gh as the credential helper and using Git 2.46 or later. Existing sign-ins remain unchanged unless a user opts in.

Taken together, these releases give software teams three distinct control points. Dependency policy governs incoming code, named metrics describe working practices, and the credential helper manages continued access. Organisations can adopt them independently, document the relevant client versions and use normal deployment stages to introduce the change to developer machines and automated runners.

Sources

- [GitHub package firewall in public preview](https://github.blog/changelog/2026-10-20-github-package-firewall-in-public-preview/) — GitHub · 2026-10-20 - [Custom skills, agents, and MCP servers in usage metrics API](https://github.blog/changelog/2026-10-22-custom-skills-agents-and-mcp-servers-in-usage-metrics-api/) — GitHub · 2026-10-22 - [GitHub CLI: Opt in to expiring, auto-refreshing OAuth tokens](https://github.blog/changelog/2026-10-21-github-cli-opt-in-to-expiring-auto-refreshing-oauth-tokens/) — GitHub · 2026-10-21