Tempr vs Continue
Continue, the open-source bring-your-own-key assistant for VS Code and JetBrains IDEs, was acquired by Cursor in June 2026, and its repository is no longer maintained. If you're looking for a replacement that keeps your own keys and your IDE, here's how Tempr compares.
The short answer
- Stay on Continue for now if it still does what you need and you're comfortable running software that no longer gets updates; it won't be fixed when providers change their APIs.
- Move to Tempr if you want chat, the agent, and inline completion on your own keys in VS Code and JetBrains IDEs, plus Visual Studio, from an actively developed product.
Side by side
| Tempr | Continue | |
|---|---|---|
| Status | Actively developed | Acquired by Cursor in June 2026; the repository is read-only and no longer maintained; hosted services have shut down |
| Last release | Regular releases | VS Code: June 19, 2026; JetBrains: March 27, 2026 |
| IDEs | Visual Studio 2022 and 2026, VS Code, JetBrains IDEs | VS Code and JetBrains IDEs; no Visual Studio |
| Your own key | About 30 providers, plus your own OpenAI-compatible endpoints on Pro | 50+ providers, including local models such as Ollama |
| Inline completion on your own key | Yes | Yes |
| Setup | Add keys once in the Tempr Portal; every IDE and the CLI use them | A config.yaml file on each machine |
| Price | Standard $15/mo, Pro $20/mo; 7-day free trial | Free and open source (Apache 2.0) |
| Where requests go | Through Tempr's servers to your provider | Straight from your machine to your provider |
| Local models | Your own OpenAI-compatible server, reachable over public HTTPS with an API key (Pro and Teams) | Local servers such as Ollama on your machine |
What happened to Continue
Cursor acquired Continue in June 2026. The repository is now read-only and marked as no longer maintained, the last VS Code release was on June 19, 2026, and the last JetBrains release on March 27, 2026. Continue's hosted services have shut down. The extension still runs with a local config.yaml, but it won't get fixes or updates as providers and IDEs change.
Moving from Continue to Tempr
Install Tempr from the Visual Studio Marketplace, Open VSX, or the JetBrains Marketplace, and start the 7-day free trial. Add the same provider keys you had in config.yaml in the Tempr Portal once; Visual Studio, VS Code, JetBrains IDEs, and the CLI all use them. Then pick models for chat, the agent, and inline completion. The IDE quickstart walks through it.
Two differences to plan for. Tempr relays requests through its servers rather than calling providers from your machine. And because of that, a model server running only on your machine, such as Ollama on localhost, can't be used directly: Tempr's custom models need an OpenAI-compatible endpoint reachable over public HTTPS with an API key, on the Pro and Teams plans.
What you give up, and what you gain
You give up an open-source, free extension and a fully local data path. You gain an actively developed product with inline completion, an agent with Interactive, Bypass, and Autopilot modes and personas, MCP servers, chats that sync between machines on Standard and higher plans, Visual Studio support, and Teams features such as SSO and centrally managed keys. Tempr doesn't use your prompts, code, or chats to train models; the Privacy Policy covers what's stored and for how long.
Staying on Continue for now?
You can point Continue at the Tempr Gateway through its apiBase setting, so one key reaches every model on your Gateway allowlist while you decide.
Questions
How we checked
Everything about Continue comes from its own pricing pages, documentation, and release notes, checked on September 21, 2026. These products change quickly, so prices and features may have moved since. Spotted something out of date? Tell us and we'll fix it.
Sources: continue.dev · source code · configuration · model providers · The New Stack
Try Tempr on your own keys
Every paid Chat plan starts with a 7-day free trial, and the CLI is included.