Continue.dev、VS Code拡張機能 v1.2.24-vscode をリリースContinue.dev Releases v1.2.24-vscode

Continue.dev has published version 1.2.24-vscode of its open-source AI coding assistant for Visual Studio Code, a stable, maintenance-oriented update that removes two features and reworks how newcomers connect their language models. The release matters because Continue is among the more widely adopted open alternatives to proprietary assistants such as GitHub Copilot, and even small changes to its onboarding flow shape the first impression for developers evaluating the tool.

Continue is an extension that brings chat, inline code editing, autocomplete, and agent-style workflows directly into the editor. Unlike closed assistants that bind users to a single vendor's models, Continue is provider-agnostic: developers point it at hosted APIs from companies like OpenAI, Anthropic, Mistral, or Google, or at locally running models served through tools such as Ollama or LM Studio. That flexibility is configured through a settings file, historically a config.json and more recently a YAML-based assistant configuration, where models, roles, and context providers are declared.

According to the release notes, this version switches the onboarding experience and the new-configuration template to an explicit model definition approach. In practice this appears to mean that the default starting configuration now spells out the model provider, model name, and associated parameters rather than relying on implicit defaults or auto-selected entries. The intent is likely to make a user's setup more transparent and reproducible, reducing confusion about which model is actually answering a request or generating completions. For teams that share configurations across a project, explicit definitions also tend to be easier to audit and version-control.

The update also removes the CLI-install banner that previously surfaced inside the extension. Continue has been expanding beyond the editor with a command-line interface, and the banner appears to have served as a prompt encouraging users to install that companion tool. Eliminating it declutters the interface and suggests the project is moving CLI discovery out of the in-editor prompts, though the CLI itself remains a separate offering. The change is cosmetic in functional terms but reduces friction for users who only want the editor integration.

Alongside that, the Generate Rule feature has been removed. Rules in Continue are persistent instructions that steer the assistant's behavior, similar in spirit to system prompts or the rule files used by other AI coding tools, letting developers encode conventions such as preferred frameworks, coding style, or project-specific constraints. The Generate Rule capability appeared to automate the creation of such a rule from existing context or a conversation. Its removal does not necessarily indicate that manual rules are going away; rather, the automated generation path has been retired, possibly because it was underused or is being reconsidered. The release notes do not detail a replacement.

Taken together, the changes point to a consolidation phase rather than a feature expansion. Removing a banner and an auto-generation helper while standardizing on explicit configuration suggests the maintainers are prioritizing clarity and a leaner default experience over breadth. That aligns with a broader pattern in the AI coding-assistant space, where rapid feature accumulation is periodically followed by simplification as projects settle on conventions. The version label itself, a patch-level increment within the 1.2 line, is consistent with an incremental stable release rather than a major architectural shift.

For context, the assistant category has grown crowded and competitive. GitHub Copilot remains the most recognized commercial option, Cursor has gained traction as an AI-native editor fork, and tools like Cline, Aider, and Tabby occupy adjacent niches spanning agentic workflows and self-hosted deployments. Continue's distinguishing position is its open-source license and model-agnostic design, which appeal to developers wary of vendor lock-in or those who must keep code on local infrastructure for privacy or compliance reasons. Decisions about onboarding and default configuration are therefore consequential, since they influence how easily new users reach a working setup.

Existing users upgrading to 1.2.24-vscode should review their configuration if they relied on the removed Generate Rule feature, and may notice the streamlined onboarding when creating a fresh setup. As always with extension updates, consulting the official changelog and configuration documentation is advisable before adopting the release in a production workflow.