Skip to content
Proposals/Replace Continue Hub slugs with explicit model d
proposaldeveloperP2Worth a lookContinue

Replace Continue Hub slugs with explicit model definitions

Continue VS Code v1.2.24 (final release; re-cut of a partial v1.2.23 Marketplace publish) removes Generate Rule and the CLI-install banner, switches onboarding and the new-config template to explicit model definitions instead of Hub slugs, and updates the deprecation banner export link.

Why this loop

v1.2.24-vscode is the stable final Continue VS Code extension release. Onboarding and the new-config template now require explicit model definitions, so any config, snippet, or doc that still uses Hub slugs will not match what the extension generates. Generate Rule is gone, so UI-based rule creation will fail. The CLI-install banner is gone, so install/onboarding copy that pointed at it is stale. The deprecation banner export link changed, so previously saved export URLs may be wrong. Align configs and instructions with this cut rather than the incomplete v1.2.23 publish.

Proposed actions

  1. In VS Code, install or update Continue to exactly v1.2.24-vscode from the Marketplace (this is the re-cut of v1.2.23, which only partially published after a Marketplace API timeout).
  2. Open this workspace's Continue config and rewrite every Hub slug model entry into an explicit model definition (provider, model, and credentials/API settings inline) so it matches the v1.2.24 onboarding and new-config template. Do not add new Hub slugs.
  3. Search the repo for Continue Generate Rule docs, keybindings, and agent instructions and replace them with direct edits to Continue rule/config files; Generate Rule was removed in v1.2.24-vscode.
  4. If the Continue deprecation banner is showing, use only the updated export link on that banner to export settings; discard any previously saved export URL.
  5. Rewrite onboarding notes: the CLI-install banner was removed in this final VS Code extension release—have new developers start from the new-config template with explicit model definitions, not Hub slugs.

Agent prompt

Paste into your agent or query via MCP (get_agent_prompt) — free, no extra AI cost

Copilot Chat / Agent mode

DevAgentRadar → GitHub Copilot

You are helping me adopt a real coding-assistant change. Work only from the facts below. Do not invent features.

Context

Assistant: Continue Proposal: Replace Continue Hub slugs with explicit model definitions Summary: Continue VS Code v1.2.24 (final release; re-cut of a partial v1.2.23 Marketplace publish) removes Generate Rule and the CLI-install banner, switches onboarding and the new-config template to explicit model definitions instead of Hub slugs, and updates the deprecation banner export link. Primary source: https://github.com/continuedev/continue/releases/tag/v1.2.24-vscode

Why it matters

v1.2.24-vscode is the stable final Continue VS Code extension release. Onboarding and the new-config template now require explicit model definitions, so any config, snippet, or doc that still uses Hub slugs will not match what the extension generates. Generate Rule is gone, so UI-based rule creation will fail. The CLI-install banner is gone, so install/onboarding copy that pointed at it is stale. The deprecation banner export link changed, so previously saved export URLs may be wrong. Align configs and instructions with this cut rather than the incomplete v1.2.23 publish.

Suggested actions

  1. In VS Code, install or update Continue to exactly v1.2.24-vscode from the Marketplace (this is the re-cut of v1.2.23, which only partially published after a Marketplace API timeout).
  2. Open this workspace's Continue config and rewrite every Hub slug model entry into an explicit model definition (provider, model, and credentials/API settings inline) so it matches the v1.2.24 onboarding and new-config template. Do not add new Hub slugs.
  3. Search the repo for Continue Generate Rule docs, keybindings, and agent instructions and replace them with direct edits to Continue rule/config files; Generate Rule was removed in v1.2.24-vscode.
  4. If the Continue deprecation banner is showing, use only the updated export link on that banner to export settings; discard any previously saved export URL.
  5. Rewrite onboarding notes: the CLI-install banner was removed in this final VS Code extension release—have new developers start from the new-config template with explicit model definitions, not Hub slugs.

After you finish

Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.

Tell the human: open https://devagentradar.com/proposals/continue-v1-2-24-vscode-replace-continue-hub-slugs-with-explicit-model-d and mark Applied, Skipped, or Failed. Proposal id: 38fd74d7-d9c6-4d21-a4d4-16f6653f7601

Your job

  1. Restate the change in one sentence.
  2. Propose a minimal plan for my repo (or a throwaway pilot).
  3. Implement only what I approve; prefer small diffs and tests.
  4. Call out risks (permissions, breaking APIs, cost).

Start by confirming you understood the proposal.

Your loop

This browser · no sign-in · not shared as “you”

After you run the prompt

Only you can mark this. Agents cannot write your loop.

Your decision stays on this device. A public tally appears after a few votes.

Originating release signal

Continuev1.2.24-vscodeJun 15, 2026

v1.2.24-vscode

Stable release of the Continue VS Code extension (final release): removes the CLI-install banner and Generate Rule feature, switches onboarding and the new-config template to explicit model definitions (no Hub slugs), and updates the deprecation banner export link. · Re-cut of v1.2.23 which only partially published due to a transient Marketplace API timeout.
Verified excerpt — the source's own words

Stable release of the Continue VS Code extension (final release): removes the CLI-install banner and Generate Rule feature, switches onboarding and the new-config template to explicit model definitions (no Hub slugs), and updates the deprecation banner export link. Re-cut of v1.2.23 which only partially published due to a transient Marketplace API timeout.

Primary source ↗