Show HN: Void, an open-source Cursor/GitHub Copilot alternative

Original Article ↗ Hacker News Discussion ↗

Comparison to Existing AI Coding Tools

  • Many compare Void to Cursor, Continue.dev, Codeium, Cody, Copilot, etc.
  • Cursor is repeatedly praised for:
    • Extremely strong tab-autocomplete and “tab-tab-tab full-file autofix”.
    • The “apply/merge” workflow that edits multiple files cleanly.
    • RAG-powered side chat that handles large codebases.
  • Several feel other tools (Continue, JetBrains AI, some chat-first assistants) are unstable, clunky, or weaker on UX and quality.
  • Some say local models are currently far worse than hosted LLMs for coding, unless you have strong hardware.

VSCode Fork vs Extension Debate

  • A major thread questions why Void (and Cursor) fork VSCode rather than ship extensions.
  • Arguments for a fork:
    • VSCode extension APIs limit deep UI control (e.g., native-feeling diff views, command workflows like Cmd+K/Cmd+L).
    • Extensions often feel buggy or unnatural (quick-pick prompts, broken selections, crude diff markers).
  • Counterarguments:
    • Forks must track upstream VSCode, increasing maintenance and security burden.
    • Extensions like Cody show powerful features are possible without a fork.
    • Users and enterprises already invested in existing IDEs resist switching editors.

Target Users, Monetization, and Privacy

  • Void plans to monetize via enterprises, emphasizing on-prem deployments and repo privacy.
  • Some note competitors already offer on-prem or BYO-key options.
  • Home/OSS users hope the tool remains free while enterprises pay.

Maturity, Open Source, and Access

  • The repo is public, but the product is early: current extension is described as a minimal weekend project.
  • Commenters criticize:
    • Waitlist + Discord gatekeeping despite open source code.
    • Weak CI, direct commits to main, and disabled checks—seen as a barrier to serious contributors.
  • There is some confusion over what “open source” should imply (offline use, model training data, etc.).

Ecosystem, Competition, and Saturation

  • Thread notes a crowded field: multiple VSCode forks and AI assistants (Cursor, PearAI, Continue, double.bot, etc.).
  • Some welcome competition and innovation in AI editors; others express fatigue with VC-backed, near-duplicate tools and “spray-and-pray” investing.

Other Editors and Alternatives

  • Strong demand for similar capabilities in JetBrains IDEs, Neovim, Zed, and non-Electron/native editors.
  • Several tools/plugins for these ecosystems are mentioned, with mixed reviews on quality and integration.