No catch. Loophole is open-source under an MIT-style licence — you can read every line of code on GitHub. We don't charge for the editor. The only costs you'll ever pay are directly to your chosen AI provider for API usage, and those bills go straight to them, not through us.
No. Your API keys are stored locally on your machine in your own config file and are never sent to Loophole's servers — because Loophole doesn't have servers. Requests go directly from your editor to your provider's endpoint. We never see your keys, your prompts, or your code.
It depends entirely on which model you pick and how much you use it. Light everyday work on a model like Claude Haiku or Gemini Flash costs pennies per day. Heavy agentic sessions with frontier models can be a few dollars per session. You can also run entirely free using local models via Ollama or vLLM at zero cost per token.
Yes. Loophole supports any OpenAI-compatible endpoint, which means Ollama, vLLM, LM Studio, and any other local inference server work out of the box. You get the full editor experience — inline diffs, Plan mode, agentic runs — at zero token cost and complete air-gap privacy.
Currently, nothing. Both are the same open-source build downloaded from GitHub. The distinction exists to prepare for the Team plan launch, which will add shared infrastructure on top of the existing free core. Every feature you see today is in both and always will be.
We're actively building it but haven't set a date or price yet. Join the waitlist on the GitHub Discussions page and you'll be the first to know. We're committed to keeping it affordable — our philosophy is that tooling shouldn't eat your AI budget.
Only to the AI provider you explicitly configure. Your code is sent to whichever endpoint you've pointed Loophole at — OpenAI, Anthropic, your own Ollama instance, or anyone else. Nothing is sent to Loophole. The editor has no telemetry, no analytics, and no call-home to our infrastructure.
Absolutely. Loophole is built on Void, itself a fork of VS Code, and the entire codebase is on GitHub. PRs, issues, and forks are all welcome. If you build something interesting on top of Loophole, share it in Discussions — we actively spotlight community work.
