Cloud Parts

VoidArchived

An open-source, VS Code-based AI editor that sent prompts straight to any model provider; paused in August 2025 and deprecated and archived in June 2026.

What it is
Editors and terminals (code editors),AI coding agents
Part of
Fork of Visual Studio Code
Type
Open source
Made by
Glass Devtools, Inc.
License
Apache 2.0
Status
Archived since 2 June 2026
Facts checked
9 October 2026
Website Source code (archived)

What it is

Void billed itself as the open-source alternative to Cursor: a fork of VS Code with Tab autocomplete, inline Quick Edit, a chat with an agent mode, and checkpoints for reviewing what the model changed. The difference was the backend, or the lack of one. Void sent requests directly from the editor to whichever provider you picked, a frontier API or a model you host yourself, and its site said it did not retain your data. Its team, from Glass Devtools and backed by Y Combinator according to its site, mounted React and Tailwind inside the VS Code workbench and wrote its own provider code to support fill-in-the-middle autocomplete and diffs that stream in token by token.

Development stopped in stages. On August 1, 2025 the README announced that work was paused while the team explored new AI coding ideas. In January 2026 it added that features might stop working without maintenance and that Void might not resume as an IDE. On June 2, 2026 it declared Void deprecated and the repository was archived. The last binary build was published on June 23, 2025. The team now presents the code as a reference for anyone forking VS Code, including its GitHub Actions for packaging, signing and auto-updating, which VS Code’s private build pipeline doesn’t provide.

Why teams pick it

  • Fully open source under Apache 2.0, including all of its AI code
  • Any model, local or hosted, with no vendor backend in the middle
  • Still a useful reference for forking VS Code: a documented codebase guide plus build, signing and update pipelines

Watch out for

  • Deprecated and archived since June 2026: no fixes, no new releases, and no upstream VS Code updates after its last build in June 2025
  • Its build points the extension gallery at Microsoft’s Visual Studio Marketplace, whose terms reserve Marketplace extensions for Microsoft’s own products
  • A small team’s project: when its makers moved on, users were left to community forks

Alternatives, recommended first

What all code editors have in common →
ZedOpen sourceA code editor written from scratch in Rust by the team behind Atom, drawn on the GPU, with its own agent and the Agent Client Protocol for outside ones.ClineOpen sourceAn open-source coding agent that started as a VS Code extension and now runs the same engine in JetBrains, a terminal CLI, a desktop app and an SDK, with whatever model you bring.+1 Roo CodeVisual Studio CodeOpen sourceMicrosoft’s free, extensible editor and the most used one by far, built on the MIT-licensed Code - OSS project that Cursor, Windsurf and Void forked.+3 Cursor, Void, Windsurf (now Devin Desktop)CursorCommercialForksThe best-known AI fork of VS Code, with agents, its own coding models and PR review built in; acquired by SpaceX in August 2026.Windsurf (now Devin Desktop)RenamedCommercialForksCodeium’s agentic fork of VS Code, bought by Cognition in July 2025 and renamed Devin Desktop on June 2, 2026.

See it in a real stack

No architecture uses Void yet. Drop it into the playground and wire it up yourself.Open playground →
Where it came from2024–2026

By 2024 the popular AI editors, Cursor and Windsurf, were closed forks of VS Code, and Void’s makers pointed out that both sent messages through a private backend. Void set out to be the open alternative: the same kind of fork, but fully open source and able to talk to any model directly, including ones running on your own machine. The repository opened in September 2024 and the first beta, version 1.0.0, followed in January 2025.

The team rebuilt a lot of plumbing that VS Code doesn’t offer to forks. It extended the build to compile React and Tailwind inside the workbench, wrote its own provider layer for autocomplete and tool calls, and built services to stream edits into files as diffs. It also had to package, sign and auto-update the app itself, since Microsoft’s build pipeline is private.

In August 2025 the team paused Void to experiment with new AI coding ideas. By January 2026 it said it wanted to focus on innovation over feature parity and warned that Void might not return as an IDE, and in June 2026 it deprecated the project and archived the repository, leaving the code as open-source reference material and a list of community forks.

Why it’s built this way

Fork VS Code
Starting from VS Code meant developers could bring over all their themes, keybindings and settings in one click.
No private backend
Void wanted users in full control of their data and their model choice, so the editor connects straight to providers or to self-hosted open models instead of a company server.
Provider code written from scratch
Owning the provider layer let Void support fill-in-the-middle autocomplete and custom response formats across many models.
React and Tailwind inside the workbench
Plain VS Code has no way to mount React UI in its workbench, so the team extended the build pipeline to compile React and scope Tailwind itself.

Timeline

  1. 2024

    Repository created in September as an open-source fork of VS Code

  2. 2025

    Version 1.0.0, the first beta release, in January

  3. 2025

    Last binary build published on June 23

  4. 2025

    Work paused on August 1

  5. 2026

    README warns in January that Void may not resume as an IDE

  6. 2026

    Deprecated and repository archived on June 2

Sources10 · facts checked 9 October 2026

Improve this page on GitHub