Copilot SDK tightens local connection checks and fixes plugin status
GitHub’s Copilot software development kit has tightened checks on local network connections and corrected how it reports user-installed plugins under organization policies. Version 1.0.34 rejects malformed requests and confines a supported agent connection to the local machine. It also preserves Windows certificate revocation checks and adds experimental controls for saved model providers, with explicit updates needed for live sessions.
Artificial Intelligence··Morning
Local servers reject malformed connections
GitHub has tightened local connection handling in Copilot SDK, its software development kit for building applications around coding agents. Version 1.0.34 rejects web requests and disconnects clients with invalid header names on its supported network message servers. Standard clients keep their existing behaviour. Another supported agent connection requires an address pointing back to the same computer and closes connections carrying invalid text or incorrectly formatted messages.[1]
Plugin status respects explicit user settings
User-installed plugins could appear disabled when an organization required managed ones. Their status now follows the user’s settings except where an explicit rule overrides them. Required plugins can be retried together or selectively, returning separate results and errors before the automatic retry pause ends. Cancellation while quitting or switching sessions also stops producing false startup-error events; genuine failures in live sessions remain visible.[1]
Windows keeps certificate revocation checks
Affected encrypted Windows connections now use the operating system’s native handling, retaining certificate revocation checks and support for system client-certificate keys that cannot be exported. GitHub also added experimental controls to inspect, edit or remove saved model providers. Applying such a change to an already running session requires a separate, explicit provider update.[1]