Archive no. MY-0004
AI Shell (PowerShell)
AI Shell（PowerShell）
A shell that put an LLM chat pane next to your PowerShell prompt. It shipped as a public preview, reached preview 8, and was archived in January 2026 without ever releasing a stable version.
Original intent · 初衷
The target was the gap between knowing roughly what you want a shell to do and remembering the exact syntax. An agent in a side pane could draft a command, explain an error, or answer a question about the current session without leaving the terminal, and the PowerShell module let the same agents be addressed from scripts. The project also existed to explore what an AI-assisted terminal experience could look like at all, which is how Microsoft framed it when thanking contributors at the end.
Timeline · 时间线
-
2024-11-19 · date-level
Microsoft's PowerShell team announces the public preview of AI Shell.
-
2025-08-05 · date-level
Preview 6 adds support for MCP, extending the set of tools an agent can reach from the shell.
-
2026-01-30 · date-level
A project status notice is added to the repository stating that AI Shell is no longer maintained: no future releases are expected, issues and pull requests are not monitored, and no new features or bug fixes are planned.
-
2026-01-30 · date-level
The repository is archived by its owner and becomes read-only.
Dates are shown at the precision the sources provide; nothing is rounded up to a full date.
What happened · 后来发生了什么
The public preview was announced in November 2024. Feature work continued at least into 2025, including support for MCP in the sixth preview. In January 2026 the repository received a status update stating that the project is no longer actively maintained, that future releases are unlikely, that issues and pull requests are not monitored, that no new features or bug fixes are planned, and that it should be considered archived from an engineering standpoint. The repository itself is now marked as archived and read-only.
Why it stopped · 停止原因
Microsoft's notice states the status change and thanks contributors; it does not give a reason. The museum records the end without a cause, because no source states one. The notice does say it will be updated if the project's status changes.
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: the useful signal is that a well-maintained Microsoft project shipped eight previews over more than a year and never cut a stable release. That pattern usually means the shape of the product was still unsettled, and the closing notice's wording about exploring possibilities fits it. This is our interpretation; Microsoft states the outcome, not this reading.
What remains · 留下了什么
The repository stays online in read-only form, so the source, the history and the closing notice all remain available for reading.
The Microsoft Learn page for AI Shell also carries the notice, so documentation and repository agree on the status.
A short link installer continues to resolve to the installation script in the archived repository, so installation still works even though the project is unmaintained.
What the makers learned · 制作者总结
Microsoft's notice states that the project should be considered archived from an engineering standpoint and that the notice will be updated if the status changes.
The notice thanks the people who experimented with the project, filed issues and gave feedback, and describes their engagement as helping to explore what AI-assisted terminal experiences could look like.
The notice contains no reason for the ending; this entry therefore shows the recorded status without a cause.
The archive banner with the January 2026 date was observed on the repository page at verification time; the repository's own API metadata could not be re-read during this verification pass, so the date is recorded from the page and the README notice.
The notice is unusually clear about what 'no longer maintained' means in practice — unmonitored issues, no fixes planned, no future releases — which is more useful to a user deciding whether to install it than the word 'archived' alone. The second lesson is about the installation path: a tool that never left prerelease still shipped a one-line installer that keeps working after the project ends, so the artefact outlives the maintenance promise attached to it.
If someone tried again · 重做问题
AI Shell explored one shape of an AI-assisted terminal and stopped at preview 8. Whatever a terminal assistant looks like next, the open question this archive leaves is the same one the notice names: who maintains the assistant inside the tool where people spend their day — and what happens to installed users when the answer is nobody.
Sources and verification · 来源与核验
- Status evidence
- [aishell-readme] [aishell-repo]
- Added
- 2026-09-13
- Entry updated
- 2026-09-13
- Last verified
- 2026-09-13
- Project period
- 2024-11-19 → 2026-01-30
Supports: The end: the notice that AI Shell is no longer maintained as of January 2026, that future releases are unlikely, that issues and pull requests are not monitored, that no new features or bug fixes are planned, and that the project should be considered archived from an engineering standpoint. The raw README is cited so the notice text can be read without the repository UI.
Supports: The archive state: the repository page shows that it was archived by the owner on 30 January 2026 and is now read-only, which is what makes the recorded status 'discontinued' rather than an inference from inactivity.
Supports: The start of the public preview and what the tool was for. The post carries a publication timestamp of 19 November 2024, which is the precision recorded here.
Supports: That development was still shipping new capability in mid-2025, roughly five months before the archive notice — evidence against reading the ending as a long, silent abandonment.
Supports: That Microsoft's documentation for the module is still published. Verification limit: at the time of verification this page did not carry the same 'no longer maintained' text as the repository README, so the notice is cited from the README rather than from this page.