Archive no. MY-0002
GitHub Copilot Voice
A GitHub Next experiment that let developers write, edit, navigate and run code by voice — aimed explicitly at people who find a keyboard and mouse difficult. The preview ended and the work moved into VS Code.
Original intent · 初衷
The pitch was explicit about who it was for: developers who find a keyboard and mouse difficult. Rather than replacing the editor, it let a person talk through a session — stating intent in natural language, entering and leaving a code mode, inserting lines, running the program — while GitHub Copilot did the editing work in the file. The demo scripts on the project page are spoken instructions about data cleaning and plotting, not code.
Timeline · 时间线
-
2022-11 · month-level
The experiment appears publicly as "Hey, GitHub!", a GitHub Next project for coding by voice.
-
2024-03-04 · date-level
Independent coverage reports that GitHub emailed preview participants to say the preview was ending and the tool would not become a product.
-
2024-04-03 · date-level
GitHub Next records that the technical preview concluded on 3 April 2024 and that the learning was transferred to the VS Code Speech extension.
Dates are shown at the precision the sources provide; nothing is rounded up to a full date.
What happened · 后来发生了什么
GitHub Next recorded that the technical preview concluded on 3 April 2024 and that everything learned was handed to the VS Code Speech extension, described as generally available. Independent coverage in March 2024 reported that GitHub had emailed preview participants that the preview was ending and that the tool would not become a product, and noted that the successor extension did not yet cover everything the experiment did.
Why it stopped · 停止原因
GitHub's own page states only that the preview concluded and that the learning moved to VS Code Speech; it gives no cause. Independent reporting frames it as an accessibility experiment that would not become a company product, which is the outlet's characterisation of the same decision.
Curator's reading · 策展人分析
Facts cite a source. Author statements are the makers' own words. Curator analysis and hypotheses are marked as interpretation.
Editor's reading: this is a rare clean case of a project that ended because the work moved, not because it failed. The recorded status is therefore 'discontinued' for the experiment as a product surface, while the underlying capability continued in a different codebase. Our interpretation, not a statement by GitHub.
What remains · 留下了什么
The GitHub Next project page remains online and carries the closing note about 3 April 2024, so it doubles as the status record.
The VS Code Speech extension is the successor that GitHub points to; we did not verify its licence or feature coverage ourselves.
The independent report about the preview ending exists but is behind a bot-protection layer for automated readers; the museum records the headline and the claims attributed to it, and flags that its body could not be re-read at verification time.
What the makers learned · 制作者总结
GitHub Next describes the project as being for people who have difficulty typing, and notes it was formerly known as "Hey, GitHub!".
GitHub Next states that the learning and feedback from the preview were transferred to the VS Code Speech extension, which is generally available.
Independent reporting states that GitHub told preview participants the tool would not become a company product, and that the successor extension lacked full feature parity at that point.
The project changed names, so an archive entry written from either name alone would miss half of its public history; both names are recorded here as aliases.
The March 2024 press headline is a news outlet's framing. GitHub's own wording is that a technical preview concluded, which is the wording used for the recorded status.
The interesting part is where the work went. A voice interface for coding was not discontinued as an idea — it was absorbed into the editor that already had a microphone, and the experiment's job was to find out which spoken commands were worth keeping. For an accessibility tool the risk is asymmetrical: shipping a partial version and calling it done is worse for the people it targets than saying the preview has ended, which is what the page does.
If someone tried again · 重做问题
VS Code Speech continued the work without full feature parity at the time of the handover. The open question is whether a general-purpose editor's speech layer can match a purpose-built voice session for developers who cannot use a keyboard — and who measures that, if anyone does.
Sources and verification · 来源与核验
- Status evidence
- [githubnext-copilot-voice] [vsm-copilot-voice]
- Added
- 2026-09-13
- Entry updated
- 2026-09-13
- Last verified
- 2026-09-13
- Project period
- 2022-11 → 2024-04-03
Supports: The end of the technical preview on 3 April 2024, the transfer of learning and feedback to the VS Code Speech extension, the accessibility purpose, and the former name "Hey, GitHub!". The page carries no publication date, so it is recorded as undated.
Supports: The March 2024 report that GitHub told preview participants the preview was ending and the tool would not become a product, and that the successor extension lacked full feature parity. Verification limit: the article body is served behind bot protection; the headline and the claims attributed to it were confirmed from search results and the GitHub Next page, not by re-reading the article body.