111 - #13204
Open
minghaoxia61-web wants to merge 12 commits into
Open
Conversation
…boarding/config models, deprecation link (continuedev#12634) * chore: remove CLI-install banner and Generate Rule feature, use explicit onboarding models - Remove CliInstallBanner component, test, and dismissal localStorage key - Remove "Generate Rule" button, GenerateRuleDialog, command, and protocol message - Convert onboarding and new-assistant template off Hub `uses:` slugs to explicit model definitions - Update deprecation banner export link to https://continue.dev/export Co-authored-by: Cursor <cursoragent@cursor.com> * chore: bump vscode extension version to 1.3.40 Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
Updated the bug report template to modify the wording of the first checkbox and remove the second checkbox.
…12636) Change the no-match fallback in DocsShell findActiveTab to return the first nav tab (IDE Extensions) instead of the last (CLI), so the docs root defaults to IDE Extensions. Add app/favicon.ico so /favicon.ico requests resolve via App Router metadata instead of falling through the optional catch-all route. Co-authored-by: Cursor <cursoragent@cursor.com>
…uedev#12637) Hub/WorkOS authentication was already stubbed out so the CLI runs fully unauthenticated using local config.yaml / API keys / env vars. This removes the now-dead login code paths that remained: - Delete unused `login`/`logout` command modules (no longer registered in the CLI and not imported anywhere). - Remove the unreachable "Login Required" TUI screen and its token-prompt handlers (handleLoginPrompt / handleLoginTokenSubmit / useLoginHandlers), which were never triggered now that login is impossible. - Drop the dead "login" navigation screen and update NavigationContext tests to use other screens. No auth gating remains on startup, headless, TUI, or standard mode. Co-authored-by: Cursor <cursoragent@cursor.com>
…2638) The docs site is served from the /continue/ subpath on GitHub Pages but next.config.js set no basePath, so /_next CSS/JS, the search index, and images were requested from the domain root and 404'd (unstyled site). - Add basePath/assetPrefix of /continue, gated on GITHUB_ACTIONS so local dev still serves from root - Expose NEXT_PUBLIC_BASE_PATH and add a withBasePath helper for raw absolute asset paths that Next doesn't prefix automatically - Prefix the search-index fetch, logo, and MDX doc images - Guard against double /images/docs/ rewrite in the MDX img component Co-authored-by: Cursor <cursoragent@cursor.com>
…continuedev#12639) * test(cli): isolate GlobalContext to fix flaky model-persistence tests The model-persistence test files set process.env.CONTINUE_GLOBAL_DIR in beforeEach to isolate their GlobalContext store, but core/util/paths.ts resolves CONTINUE_GLOBAL_DIR into a module-level constant at import time, so those per-test reassignments had no effect. As a result every test file (across parallel Vitest worker processes) read/wrote the same globalContext.json on disk, racing each other and intermittently failing "should clear model selection when set to null". Add a dedicated first setup file (vitest.global-dir-setup.ts) that creates a unique temp dir via fs.mkdtemp and sets CONTINUE_GLOBAL_DIR before any module imports paths.ts, giving each worker process its own isolated GlobalContext. Wire it in as the first entry in setupFiles and stop hardcoding the shared /tmp/continue-test dir in vitest.setup.ts. Co-authored-by: Cursor <cursoragent@cursor.com> * style(cli): remove blank line in array to fix prettier-check Pre-existing prettier-check failure on main: a blank line inside the `screens` array literal in NavigationContext.test.tsx is removed by the Prettier version CI runs. Drop the blank line so the file is formatted. Co-authored-by: Cursor <cursoragent@cursor.com> * chore: retrigger CI Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
… Hub slugs (continuedev#12804) * fix(cli): use explicit model definitions in default config instead of Hub slugs The CLI onboarding wrote a default ~/.continue/config.yaml using slug-based blocks (`uses: anthropic/claude-sonnet-4-6` with `with: { ANTHROPIC_API_KEY }`). Slug/Hub resolution has been removed, so the CLI errored at runtime with "Failed to unroll block ... Slug-based package resolution is not supported". Replace the slug block with explicit Anthropic model definitions (Claude Sonnet 4.6 + Claude Opus 4.6), mirroring core/config/onboarding.ts. Legacy slug-based anthropic blocks in an existing config are now migrated to explicit defs. Co-authored-by: Cursor <cursoragent@cursor.com> * test(cli): update headless e2e for explicit default model With the default config now creating an explicit Anthropic model (instead of an unresolvable slug), the headless run reaches the provider and fails on the invalid API key rather than failing earlier with "no model specified". Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
…tinuedev#12802) * fix(gui): remove awkward inner scroll on onboarding API-key card In the empty chat state, `main` is a fixed-height (100vh) flex scroll container. Its children (the StepsDiv banner area and the input/onboarding section) were allowed to flex-shrink, and StepsDiv's always-on `overflow-y-scroll` turned into a cramped nested scrollbox. This trapped the onboarding API-key card in a small inner scroll area instead of letting it lay out naturally. Only enable StepsDiv's overflow scroll when there is chat history (when it is `flex-1`), and mark both the empty-state StepsDiv and the input section `shrink-0` so the onboarding card keeps its natural height and the panel scrolls as one. Chat layout (history present) is unchanged. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(gui): remove empty onboarding route scroll trap Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(gui): remove GitHub issue reporting entrypoints Co-authored-by: Cursor <cursoragent@cursor.com> * style(gui): format stream error dialog Co-authored-by: Cursor <cursoragent@cursor.com> * fix(vscode): restore package metadata Co-authored-by: Cursor <cursoragent@cursor.com> * fix(gui): keep generic issue links Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
Move the docs GitHub Pages deployment from the project-page subpath (continuedev.github.io/continue) to the custom domain docs.continue.dev, served at the domain root. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
docs: serve docs site at docs.continue.dev (custom domain)
docs: remove Sign in link (login flow retired after acquisition)
Author
|
111 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
[ What changed? Feel free to be brief. ]
AI Code Review
@continue-reviewChecklist
Screen recording or screenshot
[ When applicable, please include a short screen recording or screenshot - this makes it much easier for us as contributors to review and understand your changes. See this PR as a good example. ]
Tests
[ What tests were added or updated to ensure the changes work as expected? ]