voideditor/void

Void is a deprecated fork of Visual Studio Code designed to integrate AI agents directly into the code editing workflow.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 6 minutes ago
Added to GitGenius on June 24th, 2026
Created on September 11th, 2024
Open Issues & Pull Requests: 306 (+0)
GitHub issues: Enabled
Number of forks: 2,652
Total Stargazers: 28,796 (+1)
Total Subscribers: 165 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 23.6 hours
Mean response time: 9.4 days
90th percentile: 24.8 days
Tracked items: 498

How this project is maintained

100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "probably-fixed" is answered fastest, typically in about 4 hours, while "pre-1.2.5" waits about 7 days. Three people close 76% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 252
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 391 days
Stale 30+ days: 252
Stale 90+ days: 252

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • good first issue (25)
  • high priority (25)
  • pre-1.2.5 (24)
  • probably-fixed (15)
  • question (14)
  • help wanted (10)
  • roadmap-under consideration (8)
  • medium priority (3)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Void is a deprecated fork of Visual Studio Code designed to integrate AI agents directly into the code editing workflow. The project is no longer accepting contributions, though it remains open source and serves as a reference implementation for developers forking VS Code. The repository contains the complete source code for Void's desktop application, written primarily in TypeScript.

The core purpose of Void was to enable users to leverage AI models for coding tasks while maintaining full control over their data. The editor supported multiple AI providers and allowed users to run models locally or bring their own providers. A key architectural feature was that Void sent messages directly to providers without retaining user data on its own servers. The platform emphasized checkpoint and visualization capabilities, allowing developers to track and review AI-assisted changes to their codebase.

Void's technical implementation involved several custom extensions to the VS Code foundation. The team mounted React and Tailwind CSS into the editor, which required extending the standard VS Code build pipeline to compile React and scope Tailwind CSS using a custom tool. This represented a significant departure from plain VS Code's architecture. The project also implemented custom GitHub Actions for packaging, signing, and auto-updating the application, addressing a gap in VS Code's private build pipeline that normally makes these tasks difficult for forks.

The AI integration layer was built from scratch rather than relying on existing VS Code patterns. Void's AI provider code supported autocomplete through fill-in-the-middle functionality and custom response types, with exposed grammars for common patterns like thinking tags and tool tags. The implementation used inter-process communication and satisfied content security policy requirements. Two custom services handled code editing: EditCodeService enabled displaying diffs as code streams token by token, while VoidModelService allowed background file editing with synchronization between OS files and text buffers.

The project overlapped with contributors from langgenius/dify, rust-lang/rust, and anomalyco/opencode.

For developers interested in forking VS Code, Void provides extensive documentation including a Codebase Guide and How to Contribute documentation. The project maintains a list of active Void forks and previous releases for reference. The complete Void ecosystem spans multiple repositories under the voideditor organization, with void-builder available as a tool for developing custom versions. Community support was available through a Discord server and email contact at [email protected].