github / github/copilot-cli

Stable npm install 1.0.25 still reports 1.0.11 in copilot --version and VS Code CLI integration

Open
#2,694 1 comment 1 reaction 0 assignees View on GitHub
area:installation
Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Description

### Summary

On macOS arm64, after updating the stable npm packages to 1.0.25, `copilot --version` still reports `GitHub Copilot CLI 1.0.11.`. VS Code Copilot Chat also continues to surface 1.0.11 because its CLI shim shells out to `copilot --version`.

### Steps to reproduce

1. Update the stable npm packages:

```bash
npm install -g @github/copilot@latest
npm install -g @github/copilot-darwin-arm64@latest
```

2. Verify installed package versions:

```bash
npm list -g --depth=0 @github/copilot @github/copilot-darwin-arm64
```

3. Run:

```bash
copilot --version
```

4. In VS Code, use the Copilot Chat CLI integration that relies on the Copilot CLI shim.

### Actual result

- npm packages are updated to 1.0.25
- the VS Code cached Copilot CLI package is also 1.0.25
- `copilot --version` returns `GitHub Copilot CLI 1.0.11.`
- VS Code surfaces 1.0.11 as the effective CLI version because the shim checks `copilot --version`

### Expected result

- `copilot --version` should report the installed stable version
- VS Code should not appear stuck on 1.0.11 when the package has been updated

### Environment

- macOS (Apple Silicon)
- npm global install
- VS Code Copilot Chat integration enabled

### Additional notes

- This does not appear to be a stale PATH or cache issue. I verified:
- global npm package: 1.0.25
- global platform package: 1.0.25
- VS Code cache package: 1.0.25
- The installed source appears to embed the package version separately from the value used by `copilot --version`, which suggests a version-reporting mismatch rather than a failed update.
- This may be related to #2327, but this reproduction is on the stable channel rather than the prerelease channel.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the mismatch with the listed npm install, npm list, and copilot --version commands on macOS arm64. Compare the installed package versions with the separately embedded value used by copilot --version and the VS Code CLI shim. Done means the command reports the installed stable version and VS Code no longer surfaces 1.0.11.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, node.js, shell, vscode
Domain
cli, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.