20 ms·
Show HN: Continue – Open-source coding autopilot
Hi HN, we’re Nate and Ty, co-founders of Continue, an open-source autopilot for software development built to be deeply customizable and continuously learn from development data. It consists of an extended language server and (to start) a VS Code extension.
Our GitHub is https://github.com/continuedev/continue https://github.com/continuedev/continue. You can watch a demo of Continue and download the extension at https://continue.dev https://continue.dev
— — —
A growing number of developers are replacing Google + Stack Overflow with Large Language Models (LLMs) as their primary approach to get help, similar to how developers previously replaced reference manuals with Google + Stack Overflow.
However, existing LLM developer tools are cumbersome black boxes. Developers are stuck copy/pasting from ChatGPT and guessing what context Copilot uses to make a suggestion. As we use these products, we expose how we build software and give implicit feedback that is used to improve their LLMs, yet we don’t benefit from this data nor get to keep it.
The solution is to give developers what they need: transparency, hackability, and control. Every one of us should be able to reason about what’s going on, tinker, and have control over our own development data. This is why we created Continue.
— — —
At its most basic, Continue removes the need for copy/pasting from ChatGPT—instead, you collect context by highlighting and then ask questions in the sidebar or have an edit streamed directly to your editor.
But Continue also provides powerful tools for managing context. For example, type ‘@issue’ to quickly reference a GitHub issue as you are prompting the LLM, ‘@README.md’ to reference such a file, or ‘@google’ to include the results of a Google search.
And there’s a ton of room for further customization. Today, you can write your own
- slash commands (e.g. ‘/commit’ to write a summary and commit message for staged changes, ‘/docs’ to grab the contents of a file and update documentation pages that depend on it, ‘/ticket’ to generate a full-featured ticket with relevant files and high-level instructions from a short description)
- context sources (e.g. GitHub issues, Jira, local files, StackOverflow, documentation pages)
- templated system message (e.g. “Always give maximally concise answers. Adhere to the following style guide whenever writing code: {{ /Users/nate/repo/styleguide.md }}”)
- tools (e.g. add a file, run unit tests, build and watch for errors)
- policies (e.g. define a goal-oriented agent that works in a write code, run code, read errors, fix code, repeat loop)
Continue works with any LLM, including local models using ggml or open-source models hosted on your own cloud infrastructure, allowing you to remain 100% private. While OpenAI and Anthropic perform best today, we are excited to support the progress of open-source as it catches up (https://continue.dev/docs/customization#change-the-default-llm https://continue.dev/docs/customization#change-the-default-l...).
When you use Continue, you automatically collect data on how you build software. By default, this development data is saved to `.continue/dev_data` on your local machine. When combined with the code that you ultimately commit, it can be used to improve the LLM that you or your team use (if you allow).
You can read more about how development data is generated as a byproduct of LLM-aided development and why we believe that you should start collecting it now: https://medium.com/@continuedev/its-time-to-collect-data-on-how-you-build-software-197d12a020d5 https://medium.com/@continuedev/its-time-to-collect-data-on-...
Continue has an Apache 2.0 license. We plan to make money by offering organizations a paid development data engine—a continuous feedback loop that ensures the LLMs always have fresh information and code in their preferred style.
— — —
We’d love for you to try out Continue and give us feedback! Let us know what you think in the comments : )
- weekay 3y agoSeems interesting will definitely give it a try. Few observations/ questions from reading the documentation- > Continue will only be as helpful as the LLM you are using to power the edits and explanations Are there any others apart from gpt4 suitable for programming copilot tasks ? > If files get too large, it can be difficult for Continue to fit them into the limited LLM context windows. Try to highlight the section of code that include the relevant context. It's rare that you need the entire file. Most of the value and real world use case benefits come from usage in a brownfield development where a legacy code isn’t well understood and is large (exceed current LLM context ?) > telemetry through posthog Can organisations setup their own telemetry and development data collection to further analyse how and where the Copilot is being used ? > Finops How does one get visibility of token / api usage and track api spends ?
- sestinj 3y agoAppreciate the deep read into the docs! > We've found claude-2 very capable, especially for chat functionality, and especially in situations where you're looking for the equivalent of a faster Google search, even smaller models will do. For inline edits, gpt4 well outperforms others, but we've only optimized the prompt for gpt4. There's a LOT of tinkering to be done here, and it seems clear that OSS models will be capable soon. > Definitely value there. We have an embeddings search plugin heading out the door soon, but we very consciously avoided this for a while - it obstructs understanding of what code enters the context window, and we think transparency is underrated. > Yes! You could have your own PostHog telemetry by simply switching out the key, but we also deposit higher quality development data on your machine (we never see it). Benefits being both 1) understanding ROI of the tool, and 2) being able to train custom models. > This is a reasonable request! We'll add a feature for this. Right now, you can use the usage dashboard of whichever provider's key you use.
- jierlich 3y agoBeen using Continue for a few weeks in combination with GH co-pilot. Overall it's been a solid experience. After a few days of adjusting, it's become my go to because I don't feel like I need to leave VSCode to get questions answered. Although there are constraints, the edit functionality works ~80% of the time after figuring out how to prompt it. It's clear the team is shipping a ton too since almost every day I see VSCode popup about restarting my editor for the new version of Continue. Excited to see where things go with this!