Void editor alternatives after the archive: where to migrate

Void editor is discontinued: the voideditor/void repository was archived by its owner on June 2, 2026 and its README says "Void is now deprecated". The maintained alternatives that keep Void's direct-to-provider model are VS Code's built-in Bring Your Own Key, Cline and Zed; Cursor is the managed option, and its own-key documentation covers five first-party providers with no custom base URL.

The reason this is still confusing is that Void's two official properties disagree. The repository is read-only, Apache-2.0, about 28.8k stars, last pushed June 2, 2026, and its banner reads "This repository was archived by the owner on Jun 2, 2026. It is now read-only." (checked September 19, 2026). The marketing site, checked the same day, still headlines "The open source AI code editor", still serves a Download button, and carries no notice of any kind under a "© 2026 Glass Devtools, Inc." footer. Where two official sources disagree, the repository wins: an archive flag is a state GitHub enforces, a marketing page is copy nobody updated.

One disambiguation before the tables, because search results mix them. This page is about the AI code editor at voideditor.com. It is not about Void Linux, not about the software agency that also trades as VOID, not about Void Analytics, not about the game Voices of the Void, and not about the void keyword. Directory sites publish "Void pricing" pages assembled from those; the editor never had a price.

Void editor discontinued: the dated evidence

So the product stopped shipping roughly a year before the formal archive, and the archive was never reflected on the site. The README's only forward path is a fork list that describes itself as "maintained by AI", unreviewed and "unaffiliated with the original Void project" — not a recommended successor. No dated explanation of why the project was deprecated exists on any Glass Devtools property that this page could find, so treat any cause-of-death story you read elsewhere as unsourced.

What breaks if you stay on the frozen build

Void's base is code-oss-dev version 1.99.3 (package.json, read September 19, 2026), which is VS Code 1.99 from April 2025. Current VS Code is 1.138, released September 16, 2026 (release notes). That is roughly 39 minor releases of upstream editor and Electron work that Void will never receive, and with the repository read-only there is no route for a security fix either.

Two decay paths run independently of that. First, Void ships the official Microsoft extension gallery (extensionsGallery.serviceUrl in its product.json), and Microsoft enforces a first-party-only check in its closed-source extensions — C/C++, Pylance, C#, Remote-* — which began breaking VS Code forks with C/C++ v1.24.5 in April 2025 (The Register, April 24, 2025). That dated report is the evidence; Microsoft's current enforcement scope was not re-checked for this page. Second, Void's built-in model lists are frozen at mid-2025 ids — claude-opus-4-0, claude-sonnet-4-0, gpt-4.1, o3, o4-mini (modelCapabilities.ts, read September 19, 2026). Anything newer exists only as a hand-typed custom model.

Void vs Cursor, and why Cursor is not the default answer

The brief version of this comparison is that it no longer has two live sides. The more useful version is that Cursor solves a different problem from the one Void existed to solve. Void's homepage pitch was an editor that "doesn't send your messages through a private backend like Cursor or Windsurf"; Cursor's documented own-key support is the narrowest in this set.

Cursor's own-key limits are quoted from its API keys documentation (checked September 18, 2026). Its price list needs a caveat: cursor.com/pricing is JavaScript-rendered with a monthly/yearly toggle, and two readings a day apart returned different tier sets — a September 18 reading showed Hobby free, $20, $60 and $200 individual tiers with a contact-sales team plan, while a September 19 reading showed Hobby free, a $20 individual plan and Teams at $40 per user per month. The free tier and the $20 plan appear in both. Confirm the tier you actually want in Cursor's own checkout rather than trusting either reading, including this one.

Maintained Void editor alternatives, by the reason you used Void

Prices for Zed, Cline and Kilo checked September 19, 2026 on the pages linked above; VS Code's BYOK terms from its own documentation the same day. Two caveats worth carrying. Kilo Code was acquired by Anaconda in an announcement dated July 15, 2026 and read on September 18, 2026, which says Kilo "remains available today with no changes to existing products, plans, or support for current users" — fine, but it is a live ownership change and you should know about it before standardising on it. And VS Code's BYOK covers chat and utility tasks only: its documentation states that "some features still require a GitHub account: semantic search, inline suggestions (code completions), and features that rely on embeddings".

Kunavo serves no embedding model. That step is not something Kunavo serves, on this page or anywhere else — a workflow that needs one runs it locally or against an outside provider, whichever tool you land on.

Three destinations to avoid, all of which still appear in "Void alternatives" lists. Roo Code is archived: the GitHub API reported the repository archived when checked on September 19, 2026, its last push is dated May 15, 2026, and its README points readers at Zoo Code and Cline. Continue's README states that the repository "is no longer actively maintained and is read-only for all users", and continue.dev announces "Continue has joined Cursor"; both read September 19, 2026. And the Void forks are disclaimed by the official list itself, as quoted above.

What migrates out of Void, and what does not

Storage keys read from Void's storageKeys.ts, voidSettingsService.ts and chatThreadService.ts on September 19, 2026. Exact on-disk paths per operating system are deliberately absent here: Void's product.json gives applicationName: "void" and dataFolderName: ".void-editor", but no published documentation confirms the per-OS user-settings path, so use the editor's own command instead of a path copied from a blog.

Backup and rollback. Copy settings.json and keybindings.json somewhere outside the editor before you touch anything, and keep the Void installer you already have rather than relying on a download surviving. Because keys cannot be exported, the safe order is: issue a fresh key for the new tool, get one task working there, then revoke the key Void was holding. That way a rollback costs you a key rotation, not a lost credential — and it is the right moment to retire any key that has sat in an unmaintained editor for a year.

Configuring a gateway endpoint in the replacement

Whichever tool you land on, the shape is the same: a base URL, a key, and a model id you type yourself. Kunavo's OpenAI-compatible base URL is https://api.kunavo.com/v1 — the /v1 is part of it — and its Anthropic-compatible surface is the bare origin, https://api.kunavo.com. In Zed that is one block in settings.json, with the key entered in the provider settings UI rather than the file — Zed's documentation says "Do not put API keys in settings.json":

{
  "language_models": {
    "openai_compatible": {
      "kunavo": {
        "api_url": "https://api.kunavo.com/v1",
        "available_models": [
          {
            "name": "claude-sonnet-5",
            "display_name": "Claude Sonnet 5",
            "max_tokens": 200000,
            "max_output_tokens": 64000,
            "capabilities": { "tools": true, "images": true }
          }
        ]
      }
    }
  }
}

In Cline, pick the OpenAI Compatible provider and fill in Base URL, API Key and Model ID, plus the optional context-window and input/output price fields its model configuration exposes. In VS Code, open Chat: Manage Language Models, choose Custom Endpoint, and select the API type that matches the surface you are pointing at; VS Code then writes chatLanguageModels.json with the model id, url, apiType and token limits — its apiType takes chat-completions, responses or messages, so one VS Code entry can point at either surface. Zed reaches both too, through separate openai_compatible and anthropic_compatible blocks; Cline's OpenAI Compatible provider is the OpenAI surface only.

A detail specific to Void, if you are keeping it running while you migrate: its openAICompatible provider passes your endpoint to the SDK verbatim, with nothing appended, unlike its LiteLLM, vLLM, LM Studio and Ollama providers which add /v1 themselves. So the full https://api.kunavo.com/v1 goes in that field. It also has no model discovery — list: null in its provider table — so model ids are typed by hand, and Void's own maintainers left a comment on that code path warning that the OpenAI SDK route "might not do tools, reasoning, FIM etc correctly". Its Anthropic provider is hard-wired: the client is constructed with an API key and no base URL and the settings schema has no endpoint field, so an Anthropic-compatible gateway is unreachable from Void's settings. All read from the archived sendLLMMessage.impl.ts on September 19, 2026, and none of it runtime-tested — Void was never tested against Kunavo, and it cannot be tested reliably now.

What the model bill looks like after the move

These are illustrative token arithmetic, not measured task costs and not a bill ceiling. Assume one session that sends 200,000 uncached input tokens and receives 12,000 output tokens. Rates are live Kunavo catalog prices per million tokens.

Scale by your own sessions per day before treating that as a budget, and note that a subscription editor and a metered key are different shapes of spend: a $20 monthly plan is fixed whether you use it or not, while a prepaid balance is only drawn down by work you actually run. Kunavo's catalog amount is a billing floor rather than a cap — when the upstream reports its charge, the bill is the greater of catalog cost and upstream cost times the applicable markup. Cache charges and external tools sit outside this example. The minimum top-up is $10 in prepaid credit, a funding minimum rather than a task fee or a subscription; see billing details.

Kunavo publishes setup guides for several of the tools above. Those are configuration references rather than compatibility tests — nothing on this page was runtime-tested against these clients. Start at the Cline setup or the Zed setup, keep a working route available while you try it, run one bounded task, then read the charge your account recorded for it. Create a Kunavo account when you are ready to fund a key.

Still weighing editors rather than endpoints? Cursor alternatives covers the managed-versus-BYOK choice in more detail, Cline vs Cursor compares an agent with an IDE, and the OpenAI-compatible API guide explains what that base URL actually has to serve.

FAQ

Void's repository, README, marketing site, changelog, binaries and source files checked September 19, 2026; Cursor, Zed, Cline, Kilo, VS Code and the Roo Code, Zoo Code and Continue repositories checked September 18–19, 2026. Void's behaviour is read from its archived source and was not runtime-tested, here or against Kunavo. Kunavo token rates come from the live catalog, and every dollar example is illustrative token arithmetic.