On October 20, 2026, Copilot edit predictions failed to start on macOS Apple Silicon. During investigation, I could not find the platform package version required by the main package in the public npm registry.

After reinstalling with 1.556.0, I confirmed that the executable was installed, the language server initialized, and completion requests received successful responses. I would like to understand the circumstances behind the package version discrepancy.

npm registry findings

At 02:25:59 UTC on October 20, 2026, a direct query to the public npm registry returned the following:

The main package’s 1.555.3 metadata explicitly declared:

{
  "optionalDependencies": {
    "@github/copilot-language-server-darwin-arm64": "1.555.3"
  }
}

However, copilot-language-server-darwin-arm64-1.555.3.zip was available in the corresponding GitHub release.

These findings reflect the registry state at the time of the query. I have not established why that version was absent or its availability before or after that check.

Observed behavior

The issue was observed in Zed 1.24.3 on macOS Apple Silicon.

• Repeatedly reinstalling Copilot selected 1.555.3.

• npm installation completed with exit code 0, but the required macOS ARM64 platform package and executable were absent from the installation directory.

• Signing in again did not resolve the issue.

• The editor repeatedly logged:

copilot hasn't started yet

Observations after reinstalling with 1.556.0

Without changing the Zed version, I reinstalled Copilot and confirmed:

• Both the main package and the macOS ARM64 platform package were installed at 1.556.0.

• The required executable was present and had executable permissions.

• The language server initialized successfully at 02:26:29 UTC:

[lsp] GitHub Copilot Language Server 1.556.0 initialized

• Between 02:27 and 02:30 UTC, logs recorded 22 completion requests returning HTTP 200.

• In the inspected log, the same startup error did not recur after 02:25 UTC.

These checks confirm installation, language server initialization, and completion API communication. On-screen suggestion display and acceptance were not independently verified.

Questions

1. Why was the macOS ARM64 platform package version required by the main package 1.555.3 absent from the npm registry at the time of the check?

2. Was there a known publication failure, registry propagation delay, or another release-related issue?

3. Was the release of 1.556.0 related to this behavior, or was it an independent release?

I am not trying to infer the internal release-process cause from these observations alone. I am sharing the findings to understand what happened and would appreciate clarification.

After reinstalling with 1.556.0, I confirmed that the executable was installed, the language server initialized, and completion requests received successful responses. I would like to understand the circumstances behind the package version discrepancy.

npm registry findings

At 02:25:59 UTC on October 20, 2026, a direct query to the public npm registry returned the following:

The main package’s 1.555.3 metadata explicitly declared:

{
  "optionalDependencies": {
    "@github/copilot-language-server-darwin-arm64": "1.555.3"
  }
}

However, copilot-language-server-darwin-arm64-1.555.3.zip was available in the corresponding [GitHub release](https://github.com/github/copilot-language-server-release/releases/tag/1.555.3).

These findings reflect the registry state at the time of the query. I have not established why that version was absent or its availability before or after that check.

Observed behavior

The issue was observed in Zed 1.24.3 on macOS Apple Silicon.

• Repeatedly reinstalling Copilot selected 1.555.3.
• npm installation completed with exit code 0, but the required macOS ARM64 platform package and executable were absent from the installation directory.
• Signing in again did not resolve the issue.
• The editor repeatedly logged:

copilot hasn't started yet

Observations after reinstalling with 1.556.0

Without changing the Zed version, I reinstalled Copilot and confirmed:

• Both the main package and the macOS ARM64 platform package were installed at 1.556.0.
• The required executable was present and had executable permissions.
• The language server initialized successfully at 02:26:29 UTC:

[lsp] GitHub Copilot Language Server 1.556.0 initialized

• Between 02:27 and 02:30 UTC, logs recorded 22 completion requests returning HTTP 200.
• In the inspected log, the same startup error did not recur after 02:25 UTC.

These checks confirm installation, language server initialization, and completion API communication. On-screen suggestion display and acceptance were not independently verified.

Questions

1. Why was the macOS ARM64 platform package version required by the main package 1.555.3 absent from the npm registry at the time of the check?
2. Was there a known publication failure, registry propagation delay, or another release-related issue?
3. Was the release of 1.556.0 related to this behavior, or was it an independent release?

I am not trying to infer the internal release-process cause from these observations alone. I am sharing the findings to understand what happened and would appreciate clarification.