Continue.dev、VS Code拡張機能 v1.3.40-vscode をプレリリース公開Continue.dev Releases v1.3.40-vscode

Continue.dev has published version 1.3.40-vscode of its Visual Studio Code extension as a release">pre-release, a maintenance-focused update that the project describes primarily as cleanup ahead of a forthcoming stable release. For developers who rely on Continue as their in-editor AI assistant, the build offers an early look at refinements that are expected to land in the next general-availability version, even if it introduces few user-facing features on its own.

Continue is an open-source coding assistant that integrates with editors such as VS Code and JetBrains IDEs, positioning itself as a customizable alternative to proprietary tools like GitHub Copilot. Its core capabilities include inline chat, codebase-aware question answering, autocomplete suggestions, and increasingly agentic workflows that can read files, run commands, and apply edits. A defining characteristic is that users can connect their own models, whether commercial APIs from providers like OpenAI, Anthropic, or Mistral, or locally hosted models served through runtimes such as Ollama. That flexibility has made Continue popular among teams that want control over which model processes their code and where that data is sent.

The "release">pre-release" label is meaningful in the VS Code ecosystem. The Visual Studio Marketplace supports a formal release">pre-release channel that publishers use to ship test builds to users who opt in, separate from the stable track that most people receive automatically. Installing a release">pre-release typically means accepting that the version may be less polished, but it allows early adopters to validate fixes and surface regressions before they reach the wider audience. Builds tagged with cleanup work, as this one appears to be, often consolidate earlier changes, remove deprecated code paths, tidy configuration handling, or address minor bugs rather than introduce major new functionality. Users seeking maximum stability are generally advised to remain on the standard release.

The versioning here reflects Continue's practice of distinguishing its editor extensions. The "-vscode" suffix separates this build from the project's JetBrains plugin and from the underlying core libraries that power both. Continue maintains its codebase as a monorepo, so improvements to shared components frequently propagate to multiple targets, and the project tends to iterate quickly with frequent point releases. A jump to a patch-level number such as 1.3.40 is consistent with incremental hardening rather than a feature milestone, which aligns with the stated goal of preparing for a final release.

Context from the broader market helps explain why these incremental updates matter. AI-assisted coding has become one of the most competitive areas in developer tooling, with GitHub Copilot, Cursor, Windsurf, and a range of other assistants vying for adoption. Within that field, Continue's open-source model and bring-your-own-model approach give it a distinct niche, particularly for organizations with privacy, compliance, or cost constraints that make sending source code to a single vendor undesirable. The project has also moved toward more autonomous agent features and configurable assistants, mirroring an industry-wide shift from simple autocomplete toward systems that can plan and execute multi-step tasks. Standards efforts such as Anthropic's Model Context Protocol, which Continue and other tools have adopted to connect assistants to external data sources and services, sit alongside this trend.

For users considering whether to install this build, the practical takeaway is modest. release">Pre-release cleanup versions are most useful for contributors, plugin authors, and developers who want to test their setups against upcoming changes or confirm that a previously reported issue has been resolved. Those who depend on Continue for daily work without a specific reason to test early changes can reasonably wait for the corresponding stable release, which is likely to follow once the cleanup is complete and validated. As always with rapidly evolving tooling, reviewing the project's published release notes and changelog is the most reliable way to confirm exactly what a given build modifies, since summaries of maintenance releases can understate or omit smaller adjustments.

Continue's frequent release cadence underscores how actively the project is developed and how closely it tracks the fast-moving requirements of AI-powered development environments.