“UX risk” Over the last year and a half of developing features that users didn’t like, finding out they didn’t like them, and then trying again, we’ve built a better idea of what will and won’t fly. Among the biggest predictors is what I call “UX

Continue is the leading open-source AI code assistant, already having tens of thousands of users, nearly 200 contributors, and a vibrant, growing community. We envision an ecosystem of products that build with and around Continue, and that is part of why we released our project under an Apache 2.0

If you interpreted “root path” as the root directory of your computer, don’t worry! Continue wants nothing to do with this. What we’re going to share is our strategy for gathering (and caching) autocomplete context, which relies heavily on the root path: the path from a node in

Throughout hundreds of conversations with users, we’ve heard lots about what they need in a great AI code assistant. In this post we’ll share a set of criteria that are representative of those we find companies caring about the most, especially once they have the hindsight of running

To automatically determine the most important context from your codebase, we've just released v1 of Continue's codebase retrieval feature. You can ask questions like “where do I add a new endpoint to the server?”, “what scripts are used to build this project?”, or “where do I