diff --git a/README.md b/README.md index 6ad3b5c017c..ccc192c52fa 100644 --- a/README.md +++ b/README.md @@ -33,11 +33,11 @@ Get started in [Mission Control](https://hub.continue.dev/agents), [CLI (Headless Mode)](https://docs.continue.dev/cli/quick-start#headless-mode), or [CLI (TUI mode)](https://docs.continue.dev/cli/quick-start#tui-mode) -## Background Agents +## Cloud Agents Set workflows to run automatically on [PR opens](https://docs.continue.dev/guides/continuous-ai#pattern-2-the-pr-review-agent), [schedules](https://docs.continue.dev/guides/continuous-ai#pattern-1-the-async-triage-bot), or [any event trigger](https://docs.continue.dev/cli/quick-start#headless-mode) -![Background Agents](docs/images/background-agent.gif) +![Cloud Agents](docs/images/background-agent.gif) ## CLI Agents diff --git a/binary/package-lock.json b/binary/package-lock.json index 2a7345a428e..c72b22f24fb 100644 --- a/binary/package-lock.json +++ b/binary/package-lock.json @@ -19,7 +19,7 @@ "node-fetch": "^3.3.2", "posthog-node": "^3.6.3", "system-ca": "^1.0.2", - "tar": "^7.4.3", + "tar": "^7.5.1", "undici": "^7.10.0", "uuid": "^9.0.1", "vectordb": "^0.4.20", @@ -171,7 +171,6 @@ "version": "1.1.2", "resolved": "https://registry.npmjs.org/@75lb/deep-merge/-/deep-merge-1.1.2.tgz", "integrity": "sha512-08K9ou5VNbheZFxM5tDWoqjA3ImC50DiuuJ2tj1yEPRfkp8lLLg6XAaJ4On+a0yAXor/8ay5gHnAIshRM44Kpw==", - "peer": true, "dependencies": { "lodash": "^4.17.21", "typical": "^7.1.1" @@ -184,7 +183,6 @@ "version": "7.1.1", "resolved": "https://registry.npmjs.org/typical/-/typical-7.1.1.tgz", "integrity": "sha512-T+tKVNs6Wu7IWiAce5BgMd7OZfNYUndHwc5MknN+UHOudi7sGZzuHdCadllRuqJ3fPtgFtIH9+lt9qRv6lmpfA==", - "peer": true, "engines": { "node": ">=12.17" } @@ -247,6 +245,7 @@ "resolved": "https://registry.npmjs.org/@babel/core/-/core-7.24.7.tgz", "integrity": "sha512-nykK+LEK86ahTkX/3TgauT0ikKoNCfKHEaZYTUVupJdTLzGNvrblu4u6fa7DhZONAltdf8e662t/abY8idrd/g==", "dev": true, + "peer": true, "dependencies": { "@ampproject/remapping": "^2.2.0", "@babel/code-frame": "^7.24.7", @@ -2108,6 +2107,7 @@ "version": "5.2.0", "resolved": "https://registry.npmjs.org/@octokit/core/-/core-5.2.0.tgz", "integrity": "sha512-1LFfa/qnMQvEOAdzlQymH0ulepxbxnCYAKJZfMci/5XJyIHWgEYnDmgnKakbTh7CH2tFQ5O60oYDvns4i9RAIg==", + "peer": true, "dependencies": { "@octokit/auth-token": "^4.0.0", "@octokit/graphql": "^7.1.0", @@ -2360,14 +2360,12 @@ "node_modules/@types/command-line-args": { "version": "5.2.0", "resolved": "https://registry.npmjs.org/@types/command-line-args/-/command-line-args-5.2.0.tgz", - "integrity": "sha512-UuKzKpJJ/Ief6ufIaIzr3A/0XnluX7RvFgwkV89Yzvm77wCh1kFaFmqN8XEnGcN62EuHdedQjEMb8mYxFLGPyA==", - "peer": true + "integrity": "sha512-UuKzKpJJ/Ief6ufIaIzr3A/0XnluX7RvFgwkV89Yzvm77wCh1kFaFmqN8XEnGcN62EuHdedQjEMb8mYxFLGPyA==" }, "node_modules/@types/command-line-usage": { "version": "5.0.2", "resolved": "https://registry.npmjs.org/@types/command-line-usage/-/command-line-usage-5.0.2.tgz", - "integrity": "sha512-n7RlEEJ+4x4TS7ZQddTmNSxP+zziEG0TNsMfiRIxcIVXt71ENJ9ojeXmGO3wPoTdn7pJcU2xc3CJYMktNT6DPg==", - "peer": true + "integrity": "sha512-n7RlEEJ+4x4TS7ZQddTmNSxP+zziEG0TNsMfiRIxcIVXt71ENJ9ojeXmGO3wPoTdn7pJcU2xc3CJYMktNT6DPg==" }, "node_modules/@types/follow-redirects": { "version": "1.14.4", @@ -2429,8 +2427,7 @@ "node_modules/@types/pad-left": { "version": "2.1.1", "resolved": "https://registry.npmjs.org/@types/pad-left/-/pad-left-2.1.1.tgz", - "integrity": "sha512-Xd22WCRBydkGSApl5Bw0PhAOHKSVjNL3E3AwzKaps96IMraPqy5BvZIsBVK6JLwdybUzjHnuWVwpDd0JjTfHXA==", - "peer": true + "integrity": "sha512-Xd22WCRBydkGSApl5Bw0PhAOHKSVjNL3E3AwzKaps96IMraPqy5BvZIsBVK6JLwdybUzjHnuWVwpDd0JjTfHXA==" }, "node_modules/@types/stack-utils": { "version": "2.0.3", @@ -2577,7 +2574,6 @@ "version": "3.1.0", "resolved": "https://registry.npmjs.org/array-back/-/array-back-3.1.0.tgz", "integrity": "sha512-TkuxA4UCOvxuDK6NZYXCalszEzj+TLszyASooky+i742l9TqsOdYCMJJupxRic61hwquNtppB3hgcuq9SVSH1Q==", - "peer": true, "engines": { "node": ">=6" } @@ -2837,6 +2833,7 @@ "url": "https://github.com/sponsors/ai" } ], + "peer": true, "dependencies": { "caniuse-lite": "^1.0.30001629", "electron-to-chromium": "^1.4.796", @@ -2971,7 +2968,6 @@ "version": "0.4.0", "resolved": "https://registry.npmjs.org/chalk-template/-/chalk-template-0.4.0.tgz", "integrity": "sha512-/ghrgmhfY8RaSdeo43hNXxpoHAtxdbskUHjPpfqUWGttFgycUhYPGx3YZBCnUCvOa7Doivn1IZec3DEGFoMgLg==", - "peer": true, "dependencies": { "chalk": "^4.1.2" }, @@ -3134,7 +3130,6 @@ "version": "5.2.1", "resolved": "https://registry.npmjs.org/command-line-args/-/command-line-args-5.2.1.tgz", "integrity": "sha512-H4UfQhZyakIjC74I9d34fGYDwk3XpSr17QhEd0Q3I9Xq1CETHo4Hcuo87WyWHpAF1aSLjLRf5lD9ZGX2qStUvg==", - "peer": true, "dependencies": { "array-back": "^3.1.0", "find-replace": "^3.0.0", @@ -3149,7 +3144,6 @@ "version": "7.0.1", "resolved": "https://registry.npmjs.org/command-line-usage/-/command-line-usage-7.0.1.tgz", "integrity": "sha512-NCyznE//MuTjwi3y84QVUGEOT+P5oto1e1Pk/jFPVdPPfsG03qpTIl3yw6etR+v73d0lXsoojRpvbru2sqePxQ==", - "peer": true, "dependencies": { "array-back": "^6.2.2", "chalk-template": "^0.4.0", @@ -3164,7 +3158,6 @@ "version": "6.2.2", "resolved": "https://registry.npmjs.org/array-back/-/array-back-6.2.2.tgz", "integrity": "sha512-gUAZ7HPyb4SJczXAMUXMGAvI976JoK3qEx9v1FTmeYuJj0IBiaKttG1ydtGKdkfqWkIkouke7nG8ufGy77+Cvw==", - "peer": true, "engines": { "node": ">=12.17" } @@ -3173,7 +3166,6 @@ "version": "7.1.1", "resolved": "https://registry.npmjs.org/typical/-/typical-7.1.1.tgz", "integrity": "sha512-T+tKVNs6Wu7IWiAce5BgMd7OZfNYUndHwc5MknN+UHOudi7sGZzuHdCadllRuqJ3fPtgFtIH9+lt9qRv6lmpfA==", - "peer": true, "engines": { "node": ">=12.17" } @@ -3710,7 +3702,6 @@ "version": "3.0.0", "resolved": "https://registry.npmjs.org/find-replace/-/find-replace-3.0.0.tgz", "integrity": "sha512-6Tb2myMioCAgv5kfvP5/PkZZ/ntTpVK39fHY7WkWBgvbeE+VHd/tZuZ4mrC+bxh4cfOZeYKVPaJIZtZXV7GNCQ==", - "peer": true, "dependencies": { "array-back": "^3.0.1" }, @@ -3734,8 +3725,7 @@ "node_modules/flatbuffers": { "version": "23.5.26", "resolved": "https://registry.npmjs.org/flatbuffers/-/flatbuffers-23.5.26.tgz", - "integrity": "sha512-vE+SI9vrJDwi1oETtTIFldC/o9GsVKRM+s6EL0nQgxXlYV1Vc4Tk30hj4xGICftInKQKj1F3up2n8UbIVobISQ==", - "peer": true + "integrity": "sha512-vE+SI9vrJDwi1oETtTIFldC/o9GsVKRM+s6EL0nQgxXlYV1Vc4Tk30hj4xGICftInKQKj1F3up2n8UbIVobISQ==" }, "node_modules/follow-redirects": { "version": "1.15.6", @@ -4411,6 +4401,7 @@ "resolved": "https://registry.npmjs.org/jest/-/jest-29.7.0.tgz", "integrity": "sha512-NIy3oAFp9shda19hy4HK0HRTWKtPJmGdnvywu01nOqNC2vZg+Z+fvJDxpMQA88eb2I9EcafcdjYgsDthnYTvGw==", "dev": true, + "peer": true, "dependencies": { "@jest/core": "^29.7.0", "@jest/types": "^29.6.3", @@ -5193,7 +5184,6 @@ "version": "0.0.3", "resolved": "https://registry.npmjs.org/json-bignum/-/json-bignum-0.0.3.tgz", "integrity": "sha512-2WHyXj3OfHSgNyuzDbSxI1w2jgw5gkWSWhS7Qg4bWXx1nLk3jnbwfUeS0PSba3IzpTUWdHxBieELUzXRjQB2zg==", - "peer": true, "engines": { "node": ">=0.8" } @@ -5267,14 +5257,12 @@ "node_modules/lodash": { "version": "4.17.21", "resolved": "https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz", - "integrity": "sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==", - "peer": true + "integrity": "sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==" }, "node_modules/lodash.camelcase": { "version": "4.3.0", "resolved": "https://registry.npmjs.org/lodash.camelcase/-/lodash.camelcase-4.3.0.tgz", - "integrity": "sha512-TwuEnCnxbc3rAvhf/LbG7tJUDzhqXyFnv3dtzLOPgCG/hODL7WFnsbwktkD7yUV0RrreP/l1PALq/YSg6VvjlA==", - "peer": true + "integrity": "sha512-TwuEnCnxbc3rAvhf/LbG7tJUDzhqXyFnv3dtzLOPgCG/hODL7WFnsbwktkD7yUV0RrreP/l1PALq/YSg6VvjlA==" }, "node_modules/lodash.memoize": { "version": "4.1.2", @@ -5451,9 +5439,9 @@ } }, "node_modules/minizlib": { - "version": "3.0.2", - "resolved": "https://registry.npmjs.org/minizlib/-/minizlib-3.0.2.tgz", - "integrity": "sha512-oG62iEk+CYt5Xj2YqI5Xi9xWUeZhDI8jjQmC5oThVH5JGCTgIjr7ciJDzC7MBzYd//WvR1OTmP5Q38Q8ShQtVA==", + "version": "3.1.0", + "resolved": "https://registry.npmjs.org/minizlib/-/minizlib-3.1.0.tgz", + "integrity": "sha512-KZxYo1BUkWD2TVFLr0MQoM8vUUigWD3LlD83a/75BqC+4qE0Hb1Vo5v1FgcfaNXvfXzr+5EhQ6ing/CaBijTlw==", "license": "MIT", "dependencies": { "minipass": "^7.1.2" @@ -5462,21 +5450,6 @@ "node": ">= 18" } }, - "node_modules/mkdirp": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-3.0.1.tgz", - "integrity": "sha512-+NsyUUAZDmo6YVHzL/stxSu3t9YS1iljliy3BSDrXJ/dkn1KYdmtZODGGjLcc9XLgVVpH4KshHB8XmZgMhaBXg==", - "license": "MIT", - "bin": { - "mkdirp": "dist/cjs/src/bin.js" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, "node_modules/mkdirp-classic": { "version": "0.5.3", "resolved": "https://registry.npmjs.org/mkdirp-classic/-/mkdirp-classic-0.5.3.tgz", @@ -5729,7 +5702,6 @@ "version": "2.1.0", "resolved": "https://registry.npmjs.org/pad-left/-/pad-left-2.1.0.tgz", "integrity": "sha512-HJxs9K9AztdIQIAIa/OIazRAUW/L6B9hbQDxO4X07roW3eo9XqZc2ur9bn1StH9CnbbI9EgvejHQX7CBpCF1QA==", - "peer": true, "dependencies": { "repeat-string": "^1.5.4" }, @@ -6115,7 +6087,6 @@ "version": "1.6.1", "resolved": "https://registry.npmjs.org/repeat-string/-/repeat-string-1.6.1.tgz", "integrity": "sha512-PV0dzCYDNfRi1jCDbJzpW7jNNDRuCOG/jI5ctQcGKt/clZD+YcPS3yIlWuTJMmESC8aevCFmWJy5wjAFgNqN6w==", - "peer": true, "engines": { "node": ">=0.10" } @@ -6416,7 +6387,6 @@ "version": "3.0.1", "resolved": "https://registry.npmjs.org/stream-read-all/-/stream-read-all-3.0.1.tgz", "integrity": "sha512-EWZT9XOceBPlVJRrYcykW8jyRSZYbkb/0ZK36uLEmoWVO5gxBOnntNTseNzfREsqxqdfEGQrD8SXQ3QWbBmq8A==", - "peer": true, "engines": { "node": ">=10" } @@ -6623,7 +6593,6 @@ "version": "3.0.2", "resolved": "https://registry.npmjs.org/table-layout/-/table-layout-3.0.2.tgz", "integrity": "sha512-rpyNZYRw+/C+dYkcQ3Pr+rLxW4CfHpXjPDnG7lYhdRoUcZTUt+KEsX+94RGp/aVp/MQU35JCITv2T/beY4m+hw==", - "peer": true, "dependencies": { "@75lb/deep-merge": "^1.1.1", "array-back": "^6.2.2", @@ -6644,7 +6613,6 @@ "version": "6.2.2", "resolved": "https://registry.npmjs.org/array-back/-/array-back-6.2.2.tgz", "integrity": "sha512-gUAZ7HPyb4SJczXAMUXMGAvI976JoK3qEx9v1FTmeYuJj0IBiaKttG1ydtGKdkfqWkIkouke7nG8ufGy77+Cvw==", - "peer": true, "engines": { "node": ">=12.17" } @@ -6653,22 +6621,20 @@ "version": "7.1.1", "resolved": "https://registry.npmjs.org/typical/-/typical-7.1.1.tgz", "integrity": "sha512-T+tKVNs6Wu7IWiAce5BgMd7OZfNYUndHwc5MknN+UHOudi7sGZzuHdCadllRuqJ3fPtgFtIH9+lt9qRv6lmpfA==", - "peer": true, "engines": { "node": ">=12.17" } }, "node_modules/tar": { - "version": "7.4.3", - "resolved": "https://registry.npmjs.org/tar/-/tar-7.4.3.tgz", - "integrity": "sha512-5S7Va8hKfV7W5U6g3aYxXmlPoZVAwUMy9AOKyF2fVuZa2UD3qZjg578OrLRt8PcNN1PleVaL/5/yYATNL0ICUw==", - "license": "ISC", + "version": "7.5.2", + "resolved": "https://registry.npmjs.org/tar/-/tar-7.5.2.tgz", + "integrity": "sha512-7NyxrTE4Anh8km8iEy7o0QYPs+0JKBTj5ZaqHg6B39erLg0qYXN3BijtShwbsNSvQ+LN75+KV+C4QR/f6Gwnpg==", + "license": "BlueOak-1.0.0", "dependencies": { "@isaacs/fs-minipass": "^4.0.0", "chownr": "^3.0.0", "minipass": "^7.1.2", - "minizlib": "^3.0.1", - "mkdirp": "^3.0.1", + "minizlib": "^3.1.0", "yallist": "^5.0.0" }, "engines": { @@ -6890,8 +6856,7 @@ "node_modules/tslib": { "version": "2.6.2", "resolved": "https://registry.npmjs.org/tslib/-/tslib-2.6.2.tgz", - "integrity": "sha512-AEYxH93jGFPn/a2iVAwW87VuUIkR1FVUKB77NwMF7nBTDkDrrT/Hpt/IrCJ0QXhW27jTBDcf5ZY7w6RiqTMw2Q==", - "peer": true + "integrity": "sha512-AEYxH93jGFPn/a2iVAwW87VuUIkR1FVUKB77NwMF7nBTDkDrrT/Hpt/IrCJ0QXhW27jTBDcf5ZY7w6RiqTMw2Q==" }, "node_modules/tunnel-agent": { "version": "0.6.0", @@ -6932,6 +6897,7 @@ "integrity": "sha512-CWBzXQrc/qOkhidw1OzBTQuYRbfyxDXJMVJ1XNwUHGROVmuaeiEm3OslpZ1RV96d7SKKjZKrSJu3+t/xlw3R9A==", "dev": true, "license": "Apache-2.0", + "peer": true, "bin": { "tsc": "bin/tsc", "tsserver": "bin/tsserver" @@ -6944,7 +6910,6 @@ "version": "4.0.0", "resolved": "https://registry.npmjs.org/typical/-/typical-4.0.0.tgz", "integrity": "sha512-VAH4IvQ7BDFYglMd7BPRDfLgxZZX4O4TFcRDA6EN5X7erNJJq+McIEp8np9aVtxrCJ6qx4GTYVfOWNjcqwZgRw==", - "peer": true, "engines": { "node": ">=8" } @@ -7148,7 +7113,6 @@ "version": "5.1.0", "resolved": "https://registry.npmjs.org/wordwrapjs/-/wordwrapjs-5.1.0.tgz", "integrity": "sha512-JNjcULU2e4KJwUNv6CHgI46UvDGitb6dGryHajXTDiLgg1/RiGoPSDw4kZfYnwGtEXf2ZMeIewDQgFGzkCB2Sg==", - "peer": true, "engines": { "node": ">=12.17" } diff --git a/docs/CONTRIBUTING.mdx b/docs/CONTRIBUTING.mdx index 6a01562e217..6f1483c7460 100644 --- a/docs/CONTRIBUTING.mdx +++ b/docs/CONTRIBUTING.mdx @@ -91,8 +91,8 @@ We strongly encourage using Continue's AI assistance to maintain consistency and The easiest way to get started is using our pre-configured documentation agent: - - Visit [the Docs Assistant - Mintlify in the Hub](https://hub.continue.dev/continuedev/docs-mintlify) and click "Install" to add it to your Continue setup. This agent comes pre-configured with all our documentation standards. + + Visit [the Docs Assistant - Mintlify in Mission Control](https://hub.continue.dev/continuedev/docs-mintlify) and click "Install" to add it to your Continue setup. This agent comes pre-configured with all our documentation standards. Learn more about Continue Configs in our [config documentation](/guides/understanding-configs). @@ -139,13 +139,13 @@ If you want more control or customization, you can create your own documentation - Install from Continue Hub: https://hub.continue.dev/continuedev/continue-docs-mcp + Install from Continue Mission Control: https://hub.continue.dev/continuedev/continue-docs-mcp This MCP provides context about Continue's documentation structure and standards. - Install from Continue Hub: https://hub.continue.dev/mintlify/technical-writing-rule + Install from Continue Mission Control: https://hub.continue.dev/mintlify/technical-writing-rule This rule ensures proper Mintlify component formatting. @@ -339,7 +339,7 @@ Learn more about linking PRs to issues in the [GitHub documentation](https://doc ## 🆘 Getting Help - **Start a Discussion**: Use [GitHub Discussions](https://github.com/continuedev/continue/discussions) for documentation issues, suggestions, or questions -- **Continue agent questions**: Check the [Continue Hub page](https://hub.continue.dev/continuedev/docs-mintlify) +- **Continue agent questions**: Check the [Continue Mission Control page](https://hub.continue.dev/continuedev/docs-mintlify) - **Discord community**: Join our Discord for real-time help - **Existing docs**: Review similar pages for formatting examples --- diff --git a/docs/hub/agents/create-and-edit.mdx b/docs/agents/create-and-edit.mdx similarity index 97% rename from docs/hub/agents/create-and-edit.mdx rename to docs/agents/create-and-edit.mdx index 58be7b5ea66..79becb4a668 100644 --- a/docs/hub/agents/create-and-edit.mdx +++ b/docs/agents/create-and-edit.mdx @@ -1,11 +1,11 @@ --- title: "Create and Edit Agents" -description: "Build custom AI workflows with prompts, rules, and tools through the Continue Hub interface" +description: "Build custom AI workflows with prompts, rules, and tools through the Continue Mission Control interface" sidebarTitle: "Create & Edit" --- - You can only create and edit Agents through Mission Control in the Continue Hub web interface. + You can only create and edit Agents through Mission Control in the Continue Mission Control web interface. This ensures proper validation, versioning, and team collaboration features. @@ -90,7 +90,7 @@ Before creating your own agent, let's see one in action! The fastest way to expe - From the Continue Hub top navigation bar, select **"+"** → **"New Agent"**. + From the Continue Mission Control top navigation bar, select **"+"** → **"New Agent"**. This opens the **Create an Agent (beta)** form with all required fields. @@ -101,7 +101,7 @@ Before creating your own agent, let's see one in action! The fastest way to expe | Field | What to Enter | Example | |-------|---------------|---------| - | **Name** | Display name shown in the Hub | `GitHub PR Agent` | + | **Name** | Display name shown in Mission Control | `GitHub PR Agent` | | **Prompt** | First instruction the agent receives | `Open a GitHub PR to fix the specified issue.` | | **Description** | What the agent does | `Creates a pull request and includes AI-generated summaries.` | | **Tools (MCPs)** | Select built-in or custom MCPs | `GitHub, PostHog, Supabase` | diff --git a/docs/hub/agents/intro.mdx b/docs/agents/intro.mdx similarity index 98% rename from docs/hub/agents/intro.mdx rename to docs/agents/intro.mdx index 7cfb49b1eb6..b7484351eaf 100644 --- a/docs/hub/agents/intro.mdx +++ b/docs/agents/intro.mdx @@ -15,7 +15,7 @@ sidebarTitle: "Getting Started" Use Mission Control to kick off agents for: - **Bug fixes & code quality** - Address nitpicks and technical debt - **Feature development** - Build boilerplate-heavy features -- **Security & compliance** - [Automated vulnerability scanning](../../guides/snyk-mcp-continue-cookbook) +- **Security & compliance** - [Automated vulnerability scanning](../guides/snyk-mcp-continue-cookbook) - **Investigation & analysis** - Research issues to kickstart your work - **Custom workflows** - Run repeatable tasks with your own rules and prompts @@ -173,7 +173,7 @@ The practice of using agents (Continuous AI) requires thoughtful setup of guardr - Test with [Continue CLI](../../guides/cli) in TUI mode before deploying automation. + Test with [Continue CLI](../guides/cli) in TUI mode before deploying automation. diff --git a/docs/hub/agents/overview.mdx b/docs/agents/overview.mdx similarity index 86% rename from docs/hub/agents/overview.mdx rename to docs/agents/overview.mdx index e4dc90a02f8..037b91b14f4 100644 --- a/docs/hub/agents/overview.mdx +++ b/docs/agents/overview.mdx @@ -6,7 +6,7 @@ sidebarTitle: "Overview" Agents are custom AI workflows that combine a prompt, rules, and tools (MCPs and more) to complete specific, repeatable tasks. - They live in the Continue Hub and can be executed from Mission Control (web interface), TUI mode, or headless automation. + They live in the Continue Mission Control and can be executed from Mission Control (web interface), TUI mode, or headless automation. ## What Are Agents? @@ -35,7 +35,7 @@ You can run Agents in three main ways: **Interactive web interface** - Trigger from the Continue Hub and review results in real-time. + Trigger from the Continue Mission Control and review results in real-time. ```bash # Navigate to hub.continue.dev/agents @@ -170,9 +170,36 @@ Agents are organizational assets — once created, everyone in your org can use +## Monitoring + +You can monitor all activity for your Agents directly in **Mission Control**. + + + + + The **Inbox** shows every Task or Workflow run, and you can filter by Agent. + + + + Click any session in the Inbox to open the Detail page. + + Each session includes: + - **Summary** — what the agent did and why + - **Diff** — generated code changes + - **Logs** — full execution trace, tool calls, and reasoning + + This is the best way to review output, debug issues, or confirm correctness. + + + + + +All monitoring is scoped to your current workspace. + + ## Best Practices -The practice of using background agents, which we call Continuous AI, requires forethought to set up the right guardrails: +The practice of using cloud agents, which we call Continuous AI, requires forethought to set up the right guardrails: - **Start Small**: Begin with tasks you're confident Continue can accomplish - **Use Thorough Prompts**: Agents can run for extended periods, so invest in detailed instructions diff --git a/docs/cli/install.mdx b/docs/cli/install.mdx index 9f0df099726..ae8574c2550 100644 --- a/docs/cli/install.mdx +++ b/docs/cli/install.mdx @@ -76,7 +76,7 @@ For interactive development and exploration: ```bash cn login ``` -This will open your browser to authenticate with Continue Hub. +This will open your browser to authenticate with Continue Mission Control. @@ -101,7 +101,7 @@ For automation workflows and scripting: For automation workflows, get an API key: -1. Visit [Continue Hub API Keys](https://hub.continue.dev/settings/api-keys) +1. Visit [Continue Mission Control API Keys](https://hub.continue.dev/settings/api-keys) 2. Click **"+ New API Key"** 3. Copy the API key immediately (you won't see it again!) 4. Login using your Continue account @@ -109,7 +109,7 @@ For automation workflows, get an API key: Store secure credentials for CLI workflows: -1. Visit [Continue Hub Secrets](https://hub.continue.dev/settings/secrets) +1. Visit [Continue Mission Control Secrets](https://hub.continue.dev/settings/secrets) 2. Add your API keys and sensitive data 3. Reference in configurations with `${{ secrets.SECRET_NAME }}` diff --git a/docs/cli/overview.mdx b/docs/cli/overview.mdx index f0b56c642a5..f2063b60587 100644 --- a/docs/cli/overview.mdx +++ b/docs/cli/overview.mdx @@ -20,7 +20,7 @@ sidebarTitle: "Overview" Prerequisites: - [Node.js 18 or newer](https://nodejs.org/en/download/) -- A [Continue Hub](https://hub.continue.dev) account (recommended) or local configuration +- A [Continue Mission Control](https://hub.continue.dev) account (recommended) or local configuration ```bash npm # Install Continue CLI @@ -132,17 +132,17 @@ cn -p "Update documentation based on recent code changes" - Switch between models with `/model` command - Use any model configured in your `config.yaml` -- Access Continue Hub models and configurations +- Access Continue Mission Control models and configurations -## Continue Hub Integration +## Continue Mission Control Integration -Continue CLI integrates seamlessly with [Continue Hub](https://hub.continue.dev) for: +Continue CLI integrates seamlessly with [Continue Mission Control](https://hub.continue.dev) for: ### API Access Get an API key for automation workflows: -1. Visit [Continue Hub API Keys](https://hub.continue.dev/settings/api-keys) +1. Visit [Continue Mission Control API Keys](https://hub.continue.dev/settings/api-keys) 2. Create a new API key 3. Use with `cn login` or in your automation scripts @@ -150,7 +150,7 @@ Get an API key for automation workflows: Store secure credentials for CLI workflows: -1. Visit [Continue Hub Secrets](https://hub.continue.dev/settings/secrets) +1. Visit [Continue Mission Control Secrets](https://hub.continue.dev/settings/secrets) 2. Add your API keys and sensitive data 3. Reference in configurations with `${{ secrets.SECRET_NAME }}` diff --git a/docs/customization/models.mdx b/docs/customization/models.mdx index 7c9fd9f442c..f705d39080b 100644 --- a/docs/customization/models.mdx +++ b/docs/customization/models.mdx @@ -33,57 +33,57 @@ Read more about [model roles](/customize/model-roles), [model capabilities](/cus [Claude 4 Sonnet](https://hub.continue.dev/anthropic/claude-4-sonnet) from Anthropic 1. Get your API key from [Anthropic](https://console.anthropic.com/) -2. Add [Claude 4 Sonnet](https://hub.continue.dev/anthropic/claude-4-sonnet) to a config on Continue Hub -3. Add `ANTHROPIC_API_KEY` as a [User Secret](https://docs.continue.dev/hub/secrets/secret-types#user-secrets) on Continue Hub [here](https://hub.continue.dev/settings/secrets) +2. Add [Claude 4 Sonnet](https://hub.continue.dev/anthropic/claude-4-sonnet) to a config on Continue Mission Control +3. Add `ANTHROPIC_API_KEY` as a [User Secret](https://docs.continue.dev/mission-control/secrets/secret-types#user-secrets) on Continue Mission Control [here](https://hub.continue.dev/settings/secrets) 4. Click `Reload config` in the config selector in the Continue IDE extension [Qwen Coder 3 480B](https://hub.continue.dev/openrouter/qwen3-coder) from Qwen 1. Get your API key from [OpenRouter](https://openrouter.ai/settings/keys) -2. Add [Qwen Coder 3 480B](https://hub.continue.dev/openrouter/qwen3-coder) a config on Continue Hub -3. Add `OPENROUTER_API_KEY` as a [User Secret](https://docs.continue.dev/hub/secrets/secret-types#user-secrets) on Continue Hub [here](https://hub.continue.dev/settings/secrets) +2. Add [Qwen Coder 3 480B](https://hub.continue.dev/openrouter/qwen3-coder) a config on Continue Mission Control +3. Add `OPENROUTER_API_KEY` as a [User Secret](https://docs.continue.dev/mission-control/secrets/secret-types#user-secrets) on Continue Mission Control [here](https://hub.continue.dev/settings/secrets) 4. Click `Reload config` in the config selector in the Continue IDE extension [GPT-5](https://hub.continue.dev/openai/gpt-5) from OpenAI 1. Get your API key from [OpenAI](https://platform.openai.com) -2. Add [GPT-5](https://hub.continue.dev/openai/gpt-5) a config on Continue Hub -3. Add `OPENAI_API_KEY` as a [User Secret](https://docs.continue.dev/hub/secrets/secret-types#user-secrets) on Continue Hub [here](https://hub.continue.dev/settings/secrets) +2. Add [GPT-5](https://hub.continue.dev/openai/gpt-5) a config on Continue Mission Control +3. Add `OPENAI_API_KEY` as a [User Secret](https://docs.continue.dev/mission-control/secrets/secret-types#user-secrets) on Continue Mission Control [here](https://hub.continue.dev/settings/secrets) 4. Click `Reload config` in the config selector in the Continue IDE extension [Kimi K2](https://hub.continue.dev/openrouter/kimi-k2) from Moonshot AI 1. Get your API key from [OpenRouter](https://openrouter.ai/settings/keys) -2. Add [Kimi K2](https://hub.continue.dev/openrouter/kimi-k2) a config on Continue Hub -3. Add `OPENROUTER_API_KEY` as a [User Secret](https://docs.continue.dev/hub/secrets/secret-types#user-secrets) on Continue Hub [here](https://hub.continue.dev/settings/secrets) +2. Add [Kimi K2](https://hub.continue.dev/openrouter/kimi-k2) a config on Continue Mission Control +3. Add `OPENROUTER_API_KEY` as a [User Secret](https://docs.continue.dev/mission-control/secrets/secret-types#user-secrets) on Continue Mission Control [here](https://hub.continue.dev/settings/secrets) 4. Click `Reload config` in the config selector in the Continue IDE extension [Gemini 2.5 Pro](https://hub.continue.dev/google/gemini-2.5-pro) from Google 1. Get your API key from [Google AI Studio](https://aistudio.google.com) -2. Add [Gemini 2.5 Pro](https://hub.continue.dev/google/gemini-2.5-pro) a config on Continue Hub -3. Add `GEMINI_API_KEY` as a [User Secret](https://docs.continue.dev/hub/secrets/secret-types#user-secrets) on Continue Hub [here](https://hub.continue.dev/settings/secrets) +2. Add [Gemini 2.5 Pro](https://hub.continue.dev/google/gemini-2.5-pro) a config on Continue Mission Control +3. Add `GEMINI_API_KEY` as a [User Secret](https://docs.continue.dev/mission-control/secrets/secret-types#user-secrets) on Continue Mission Control [here](https://hub.continue.dev/settings/secrets) 4. Click `Reload config` in the config selector in the Continue IDE extension [Grok Code Fast 1](https://hub.continue.dev/xai/grok-code-fast-1) from xAI 1. Get your API key from [xAI](https://console.x.ai/) -2. Add [Grok Code Fast 1](https://hub.continue.dev/xai/grok-code-fast-1) a config on Continue Hub -3. Add `XAI_API_KEY` as a [User Secret](https://docs.continue.dev/hub/secrets/secret-types#user-secrets) on Continue Hub [here](https://hub.continue.dev/settings/secrets) +2. Add [Grok Code Fast 1](https://hub.continue.dev/xai/grok-code-fast-1) a config on Continue Mission Control +3. Add `XAI_API_KEY` as a [User Secret](https://docs.continue.dev/mission-control/secrets/secret-types#user-secrets) on Continue Mission Control [here](https://hub.continue.dev/settings/secrets) 4. Click `Reload config` in the config selector in the Continue IDE extension [Devstral Medium](https://hub.continue.dev/mistral/devstral-medium) from Mistral AI 1. Get your API key from [Mistral AI](https://console.mistral.ai/) -2. Add [Devstral Medium](https://hub.continue.dev/mistral/devstral-medium) a config on Continue Hub -3. Add `MISTRAL_API_KEY` as a [User Secret](https://docs.continue.dev/hub/secrets/secret-types#user-secrets) on Continue Hub [here](https://hub.continue.dev/settings/secrets) +2. Add [Devstral Medium](https://hub.continue.dev/mistral/devstral-medium) a config on Continue Mission Control +3. Add `MISTRAL_API_KEY` as a [User Secret](https://docs.continue.dev/mission-control/secrets/secret-types#user-secrets) on Continue Mission Control [here](https://hub.continue.dev/settings/secrets) 4. Click `Reload config` in the config selector in the Continue IDE extension [gpt-oss-120b](https://hub.continue.dev/openrouter/gpt-oss-120b) from OpenAI 1. Get your API key from [OpenRouter](https://openrouter.ai/settings/keys) -2. Add [gpt-oss-120b](https://hub.continue.dev/openrouter/gpt-oss-120b) a config on Continue Hub -3. Add `OPENROUTER_API_KEY` as a [User Secret](https://docs.continue.dev/hub/secrets/secret-types#user-secrets) on Continue Hub [here](https://hub.continue.dev/settings/secrets) +2. Add [gpt-oss-120b](https://hub.continue.dev/openrouter/gpt-oss-120b) a config on Continue Mission Control +3. Add `OPENROUTER_API_KEY` as a [User Secret](https://docs.continue.dev/mission-control/secrets/secret-types#user-secrets) on Continue Mission Control [here](https://hub.continue.dev/settings/secrets) 4. Click `Reload config` in the config selector in the Continue IDE extension ### Local Models @@ -98,36 +98,36 @@ Their limited tool calling and reasoning capabilities will make it challenging t [Qwen3 Coder 30B](https://hub.continue.dev/ollama/qwen3-coder-30b) -1. Add [Qwen3 Coder 30B](https://hub.continue.dev/ollama/qwen3-coder-30b) a config on Continue Hub +1. Add [Qwen3 Coder 30B](https://hub.continue.dev/ollama/qwen3-coder-30b) a config on Continue Mission Control 2. Run the model with [Ollama](https://docs.continue.dev/guides/ollama-guide#using-ollama-with-continue-a-developers-guide) 3. Click `Reload config` in the config selector in the Continue IDE extension [gpt-oss-20b](https://hub.continue.dev/ollama/gpt-oss-20b) -1. Add [gpt-oss-20b](ttps://hub.continue.dev/ollama/gpt-oss-20b) a config on Continue Hub +1. Add [gpt-oss-20b](https://hub.continue.dev/ollama/gpt-oss-20b) a config on Continue Mission Control 2. Run the model with [Ollama](https://docs.continue.dev/guides/ollama-guide#using-ollama-with-continue-a-developers-guide) 3. Click `Reload config` in the config selector in the Continue IDE extension [Devstral Small 27B](https://hub.continue.dev/ollama/devstral) -1. Add [Devstral Small](https://hub.continue.dev/ollama/devstral) a config on Continue Hub +1. Add [Devstral Small](https://hub.continue.dev/ollama/devstral) a config on Continue Mission Control 2. Run the model with [Ollama](https://docs.continue.dev/guides/ollama-guide#using-ollama-with-continue-a-developers-guide) 3. Click `Reload config` in the config selector in the Continue IDE extension [Qwen2.5-Coder 7B](https://hub.continue.dev/ollama/qwen2.5-coder-7b) from Qwen -1. Add [Qwen2.5-Coder 7B](https://hub.continue.dev/ollama/qwen2.5-coder-7b) a config on Continue Hub +1. Add [Qwen2.5-Coder 7B](https://hub.continue.dev/ollama/qwen2.5-coder-7b) a config on Continue Mission Control 2. Run the model with [Ollama](https://docs.continue.dev/guides/ollama-guide#using-ollama-with-continue-a-developers-guide) 3. Click `Reload config` in the config selector in the Continue IDE extension [Gemma 3 4B](https://hub.continue.dev/ollama/gemma3-4b) from Google -1. Add [Gemma 3 4B](https://hub.continue.dev/ollama/gemma3-4b) a config on Continue Hub +1. Add [Gemma 3 4B](https://hub.continue.dev/ollama/gemma3-4b) a config on Continue Mission Control 2. Run the model with [Ollama](https://docs.continue.dev/guides/ollama-guide#using-ollama-with-continue-a-developers-guide) 3. Click `Reload config` in the config selector in the Continue IDE extension [Qwen2.5-Coder 1.5B](https://hub.continue.dev/ollama/qwen2.5-coder-1.5b) from Qwen -1. Add [Qwen2.5-Coder 1.5B](https://hub.continue.dev/ollama/qwen2.5-coder-1.5b) a config on Continue Hub +1. Add [Qwen2.5-Coder 1.5B](https://hub.continue.dev/ollama/qwen2.5-coder-1.5b) a config on Continue Mission Control 2. Run the model with [Ollama](https://docs.continue.dev/guides/ollama-guide#using-ollama-with-continue-a-developers-guide) 3. Click `Reload config` in the config selector in the Continue IDE extension diff --git a/docs/customization/rules.mdx b/docs/customization/rules.mdx index 0cd8d45db4d..d1b528ffdc7 100644 --- a/docs/customization/rules.mdx +++ b/docs/customization/rules.mdx @@ -27,7 +27,7 @@ Your agent detects rules and applies the specified rules while in [Agent](/ide-e -- Manage on [Continue Hub](https://hub.continue.dev) +- Manage on [Continue Mission Control](https://hub.continue.dev) - Reference in config.yaml with `uses:` - Share with team and community - Easy to include in multiple agents diff --git a/docs/customize/deep-dives/autocomplete.mdx b/docs/customize/deep-dives/autocomplete.mdx index b18672f8315..6648c80e141 100644 --- a/docs/customize/deep-dives/autocomplete.mdx +++ b/docs/customize/deep-dives/autocomplete.mdx @@ -122,7 +122,7 @@ Then, in the continue panel, select this model as the default model for autocomp ## Autocomplete Configuration Options in Continue -### Autocomplete Models Available on the Continue Hub +### Autocomplete Models Available on the Continue Mission Control Explore autocomplete model configurations on [the hub](https://hub.continue.dev/explore/models?roles=autocomplete) diff --git a/docs/customize/deep-dives/mcp.mdx b/docs/customize/deep-dives/mcp.mdx index b804ca4c107..2ad80571159 100644 --- a/docs/customize/deep-dives/mcp.mdx +++ b/docs/customize/deep-dives/mcp.mdx @@ -154,7 +154,7 @@ For detailed information about transport mechanisms and their use cases, refer t ### How to Work with Secrets in MCP Servers With some MCP servers you will need to use API keys or other secrets. You can leverage locally stored environments secrets -as well as access hosted secrets in the Continue Hub. To leverage Hub secrets, you can use the `inputs` property in your MCP env block instead of `secrets`. +as well as access hosted secrets in the Continue Mission Control. To leverage Hub secrets, you can use the `inputs` property in your MCP env block instead of `secrets`. ```yaml # ... diff --git a/docs/customize/deep-dives/prompts.mdx b/docs/customize/deep-dives/prompts.mdx index 204f5bab157..0e9e03bbe8b 100644 --- a/docs/customize/deep-dives/prompts.mdx +++ b/docs/customize/deep-dives/prompts.mdx @@ -70,7 +70,7 @@ prompts: ... ``` -If you are using Continue Hub, you can add it to your config by selecting "Use Rule" [here](https://hub.continue.dev/supabase/create-functions) +If you are using Continue Mission Control, you can add it to your config by selecting "Use Rule" [here](https://hub.continue.dev/supabase/create-functions) To use this prompt, you can open Chat / Agent / Edit, type /, select the prompt, and type out any additional instructions you'd like to add. diff --git a/docs/customize/deep-dives/rules.mdx b/docs/customize/deep-dives/rules.mdx index d897edab42f..a065a158d24 100644 --- a/docs/customize/deep-dives/rules.mdx +++ b/docs/customize/deep-dives/rules.mdx @@ -37,7 +37,7 @@ Continue supports two types of rules with different behaviors: -- **Location**: Stored on Continue Hub, referenced in config.yaml +- **Location**: Stored on Continue Mission Control, referenced in config.yaml - **Visibility**: Only appear when referenced in assistant configuration - **Creation**: Created directly on Hub or copied from local rules - **File Management**: No local files created, managed through Hub interface @@ -92,7 +92,7 @@ For example, you can say "Create a rule for this", and a rule will be created fo ### Creating Hub Rules -Rules can also be created and managed on the Continue Hub: +Rules can also be created and managed on the Continue Mission Control: 1. **Browse existing rules**: [Explore available rules](https://hub.continue.dev/explore?type=rules) 2. **Create new rules**: [Create your own](https://hub.continue.dev/new?type=block&blockType=rules) in the Hub @@ -239,7 +239,7 @@ globs: ["**/*.ts", "**/*.tsx"] **Workaround**: 1. **For local rules**: Navigate directly to `.continue/rules/` folder and edit the `.md` file -2. **For Hub rules**: Go directly to your assistant page on [Continue Hub](https://hub.continue.dev) and edit from there +2. **For Hub rules**: Go directly to your assistant page on [Continue Mission Control](https://hub.continue.dev) and edit from there 3. Keep track of which rules are local vs Hub-based to avoid confusion diff --git a/docs/customize/model-providers/top-level/tetrate_agent_router_service.mdx b/docs/customize/model-providers/top-level/tetrate_agent_router_service.mdx index 6d307d377bb..fbd18880719 100644 --- a/docs/customize/model-providers/top-level/tetrate_agent_router_service.mdx +++ b/docs/customize/model-providers/top-level/tetrate_agent_router_service.mdx @@ -8,7 +8,7 @@ The **Tetrate Agent Router Service** provides a unified Gateway for accessing va This gateway acts as an intelligent router that can distribute requests across multiple model providers, offering enterprise-grade reliability and performance optimization. -Want to get started quickly? Sign up for the [Tetrate Agent Router Service](https://router.tetrate.ai/) to get an API key, then use [Tetrate on Continue Hub](https://hub.continue.dev/tetrate) to get started fast. +Want to get started quickly? Sign up for the [Tetrate Agent Router Service](https://router.tetrate.ai/) to get an API key, then use [Tetrate on Continue Mission Control](https://hub.continue.dev/tetrate) to get started fast. ## Setup @@ -32,13 +32,13 @@ Go to the [API keys page](https://router.tetrate.ai/api-keys) to get your key -### Quickstart with Continue Hub +### Quickstart with Continue Mission Control -Fastest way: use preconfigured models from Tetrate on Continue Hub +Fastest way: use preconfigured models from Tetrate on Continue Mission Control -Open [Tetrate on Continue Hub](https://hub.continue.dev/tetrate) and pick a model (e.g., [Claude Sonnet 4](https://hub.continue.dev/tetrate/claude-sonnet-4)) +Open [Tetrate on Continue Mission Control](https://hub.continue.dev/tetrate) and pick a model (e.g., [Claude Sonnet 4](https://hub.continue.dev/tetrate/claude-sonnet-4)) @@ -46,14 +46,14 @@ Click "Use Model", or "Remix" to change the model ID if needed -Add your API key to Continue. See [adding secrets in Continue Hub](/hub/secrets/secret-types) and [managing local secrets in the FAQ](/faqs#managing-local-secrets-and-environment-variables) +Add your API key to Continue. See [adding secrets in Continue Mission Control](/hub/secrets/secret-types) and [managing local secrets in the FAQ](/faqs#managing-local-secrets-and-environment-variables) -Add it as a Continue Hub secret named `TETRATE_API_KEY` to reuse across projects. +Add it as a Continue Mission Control secret named `TETRATE_API_KEY` to reuse across projects. -![Remix a model from Tetrate on Continue Hub](../assets/tetrate-remix.png) +![Remix a model from Tetrate on Continue Mission Control](../assets/tetrate-remix.png) If a model is missing, remix a similar one and set the `model` field to the target ID. @@ -65,7 +65,7 @@ If a model is missing, remix a similar one and set the `model` field to the targ Use a Tetrate model block from the Hub or define it directly in your local agent configuration. - + Use a Tetrate model block from the Hub or define your own on the Hub. @@ -130,7 +130,7 @@ context: - provider: codebase ``` - + **When to use**: Share configurations across teams or contribute to the community. **The Model Block:** @@ -151,7 +151,7 @@ models: capabilities: - tool_use ``` -View the model block `tetrate/claude-sonnet-4` on the [Continue Hub](https://hub.continue.dev/tetrate/claude-sonnet-4). +View the model block `tetrate/claude-sonnet-4` on the [Continue Mission Control](https://hub.continue.dev/tetrate/claude-sonnet-4). **Reference it in your Agent configuration:** @@ -172,7 +172,7 @@ context: -**When to use**: Reuse configurations across agents and keep them local or in GitHub (not on Continue Hub). +**When to use**: Reuse configurations across agents and keep them local or in GitHub (not on Continue Mission Control). **The Local Model Block:** diff --git a/docs/docs.json b/docs/docs.json index 210d06c6c48..952b3f9f728 100644 --- a/docs/docs.json +++ b/docs/docs.json @@ -23,48 +23,61 @@ "pages": ["index"] }, { - "group": "Hub", + "group": "Mission Control", "icon": "globe", "pages": [ - "hub/introduction", + "mission-control", + "mission-control/tasks", + "mission-control/workflows", + "mission-control/metrics", + "mission-control/sharing", { - "group": "Configs", - "icon": "book", + "group": "Governance", + "icon": "building", "pages": [ - "hub/configs/intro", - "hub/configs/use-a-config", - "hub/configs/create-a-config", - "hub/configs/edit-a-config" + "mission-control/governance/creating-an-org", + "mission-control/governance/org-permissions", + "mission-control/governance/pricing" ] }, + { - "group": "Governance", - "icon": "building", + "group": "Integrations", + "icon": "plug", "pages": [ - "hub/governance/creating-an-org", - "hub/governance/org-permissions", - "hub/governance/pricing" + "mission-control/integrations", + "mission-control/integrations/github", + "mission-control/integrations/sentry", + "mission-control/integrations/slack-agent" ] }, { "group": "Secrets", "icon": "key", "pages": [ - "hub/secrets/secret-types", - "hub/secrets/secret-resolution" + "mission-control/secrets/secret-types", + "mission-control/secrets/secret-resolution" ] }, { - "group": "Agents", - "icon": "robot", + "group": "Configs", + "icon": "book", "pages": [ - "hub/agents/intro", - "hub/agents/overview", - "hub/agents/create-and-edit", - "hub/agents/slack-agent" + "mission-control/configs/intro", + "mission-control/configs/use-a-config", + "mission-control/configs/create-a-config", + "mission-control/configs/edit-a-config" ] - }, - "hub/sharing" + } + ] + }, + { + "group": "Agents", + "icon": "robot", + "pages": [ + "agents/intro", + "agents/overview", + "agents/create-and-edit" ] }, { @@ -86,6 +99,7 @@ "ide-extensions/quick-start", { "group": "Agent", + "expanded": false, "icon": "robot", "pages": [ "ide-extensions/agent/quick-start", @@ -98,6 +112,7 @@ }, { "group": "Chat", + "expanded": false, "icon": "messages", "pages": [ "ide-extensions/chat/quick-start", @@ -109,6 +124,8 @@ }, { "group": "Autocomplete", + "expanded": false, + "icon": "sparkles", "pages": [ "ide-extensions/autocomplete/quick-start", @@ -121,6 +138,8 @@ }, { "group": "Edit", + "expanded": false, + "icon": "pen-to-square", "pages": [ "ide-extensions/edit/quick-start", @@ -372,39 +391,91 @@ "redirects": [ { "source": "/hub", - "destination": "/hub/introduction" + "destination": "/mission-control" + }, + { + "source": "/hub/introduction", + "destination": "/mission-control" + }, + { + "source": "/hub/configs/intro", + "destination": "/mission-control/configs/intro" + }, + { + "source": "/hub/configs/use-a-config", + "destination": "/mission-control/configs/use-a-config" + }, + { + "source": "/hub/configs/create-a-config", + "destination": "/mission-control/configs/create-a-config" + }, + { + "source": "/hub/configs/edit-a-config", + "destination": "/mission-control/configs/edit-a-config" }, { "source": "/hub/governance", - "destination": "/hub/governance/org-permissions" + "destination": "/mission-control/governance/org-permissions" + }, + { + "source": "/hub/governance/creating-an-org", + "destination": "/mission-control/governance/creating-an-org" + }, + { + "source": "/hub/governance/org-permissions", + "destination": "/mission-control/governance/org-permissions" + }, + { + "source": "/hub/governance/pricing", + "destination": "/mission-control/governance/pricing" }, { "source": "/hub/secrets", - "destination": "/hub/secrets/secret-types" + "destination": "/mission-control/secrets/secret-types" + }, + { + "source": "/hub/secrets/secret-types", + "destination": "/mission-control/secrets/secret-types" + }, + { + "source": "/hub/secrets/secret-resolution", + "destination": "/mission-control/secrets/secret-resolution" + }, + { + "source": "/hub/sharing", + "destination": "/mission-control/sharing" + }, + { + "source": "/hub/source-control", + "destination": "/mission-control" }, { "source": "/hub/blocks", - "destination": "/hub/introduction" + "destination": "/mission-control" }, { "source": "/hub/blocks/intro", - "destination": "/hub/introduction" + "destination": "/mission-control" }, { "source": "/hub/blocks/use-a-block", - "destination": "/hub/introduction" + "destination": "/mission-control" }, { "source": "/hub/blocks/block-types", - "destination": "/hub/introduction" + "destination": "/mission-control" }, { "source": "/hub/workflows/intro", - "destination": "/hub/agents/intro" + "destination": "/agents/intro" }, { "source": "/hub/blocks/create-a-block", - "destination": "/hub/introduction" + "destination": "/mission-control" + }, + { + "source": "/hub/blocks/bundles", + "destination": "/mission-control" }, { "source": "/customize", @@ -1074,10 +1145,7 @@ "source": "/guides/build-your-own-context-provider", "destination": "/customize/deep-dives/custom-providers" }, - { - "source": "/hub/blocks/bundles", - "destination": "/hub/introduction" - }, + { "source": "/customize/settings", "destination": "/customize/overview" @@ -1232,31 +1300,31 @@ }, { "source": "/hub/assistants/intro", - "destination": "/hub/configs/intro" + "destination": "/mission-control/configs/intro" }, { "source": "/hub/assistants/use-an-assistant", - "destination": "/hub/configs/use-a-config" + "destination": "/mission-control/configs/use-a-config" }, { "source": "/hub/assistants/create-an-assistant", - "destination": "/hub/configs/create-a-config" + "destination": "/mission-control/configs/create-a-config" }, { "source": "/hub/assistants/edit-an-assistant", - "destination": "/hub/configs/edit-a-config" + "destination": "/mission-control/configs/edit-a-config" }, { "source": "/hub/agents/use-an-agent", - "destination": "/hub/configs/use-a-config" + "destination": "/mission-control/configs/use-a-config" }, { "source": "/hub/agents/create-an-agent", - "destination": "/hub/configs/create-a-config" + "destination": "/mission-control/configs/create-a-config" }, { "source": "/hub/agents/edit-an-agent", - "destination": "/hub/configs/edit-a-config" + "destination": "/mission-control/configs/edit-a-config" }, { "source": "/guides/understanding-assistants", @@ -1361,6 +1429,34 @@ { "source": "/getting-started/quick-start", "destination": "/ide-extensions/quick-start" + }, + { + "source": "/hub/agents/intro", + "destination": "/agents/intro" + }, + { + "source": "/hub/agents/overview", + "destination": "/agents/overview" + }, + { + "source": "/hub/agents/create-and-edit", + "destination": "/agents/create-and-edit" + }, + { + "source": "/hub/agents/slack-agent", + "destination": "/mission-control/integrations/slack-agent" + }, + { + "source": "/hub/integrations/slack-agent", + "destination": "/mission-control/integrations/slack-agent" + }, + { + "source": "/hub/integrations/github", + "destination": "/mission-control/integrations/github" + }, + { + "source": "/hub/integrations/sentry", + "destination": "/mission-control/integrations/sentry" } ] } diff --git a/docs/faqs.mdx b/docs/faqs.mdx index 34e6ab9c70e..23a3cf22349 100644 --- a/docs/faqs.mdx +++ b/docs/faqs.mdx @@ -291,7 +291,7 @@ models: apiKey: ${{ secrets.OPENAI_API_KEY }} ``` -#### Hub-managed secrets +#### Mission Control-managed secrets For centralized team secret management, use `${{ inputs.SECRET_NAME }}` syntax in your config.yaml and manage them at [https://hub.continue.dev/settings/secrets](https://hub.continue.dev/settings/secrets): ```yaml @@ -318,12 +318,12 @@ If your API keys aren't being recognized: ### Using Model Addons Locally -You can leverage model addons from the Continue Hub in your local configurations using the `uses:` syntax. This allows you to reference pre-configured model blocks without duplicating configuration. +You can leverage model addons from the Continue Mission Control in your local configurations using the `uses:` syntax. This allows you to reference pre-configured model blocks without duplicating configuration. #### Requirements - You must be logged in to Continue -- Internet connection is required (model addons are fetched from the hub) +- Internet connection is required (model addons are fetched from Mission Control) #### Usage diff --git a/docs/guides/atlassian-mcp-continue-cookbook.mdx b/docs/guides/atlassian-mcp-continue-cookbook.mdx index 9b4b8cc9c3d..dcfd64a996f 100644 --- a/docs/guides/atlassian-mcp-continue-cookbook.mdx +++ b/docs/guides/atlassian-mcp-continue-cookbook.mdx @@ -66,7 +66,7 @@ For all options, first: - Visit the [Atlassian Continuous AI - Jira Agent](https://hub.continue.dev/continuedev/atlassian-continuous-ai-jira-agent) on Continue Hub. This agent is optimized for: + Visit the [Atlassian Continuous AI - Jira Agent](https://hub.continue.dev/continuedev/atlassian-continuous-ai-jira-agent) on Continue Mission Control. This agent is optimized for: - Searching and filtering Jira issues - Creating and updating issues - Sprint planning and workload analysis @@ -100,7 +100,7 @@ For all options, first: - Visit the [Atlassian Continuous AI - Confluence Agent](https://hub.continue.dev/continuedev/atlassian-continuous-ai-confluence-agent) on Continue Hub. This agent is optimized for: + Visit the [Atlassian Continuous AI - Confluence Agent](https://hub.continue.dev/continuedev/atlassian-continuous-ai-confluence-agent) on Continue Mission Control. This agent is optimized for: - Searching and summarizing documentation - Creating and updating Confluence pages - Managing spaces and content @@ -133,8 +133,8 @@ For all options, first: - - Go to the [Continue Hub](https://hub.continue.dev) and [create a new agent](https://hub.continue.dev/new?type=agent). + + Go to the [Continue Mission Control](https://hub.continue.dev) and [create a new agent](https://hub.continue.dev/new?type=agent). @@ -168,7 +168,7 @@ For all options, first: To use Atlassian MCP with Continue CLI, you need either: - **Continue CLI Pro Plan** with the models add-on, OR - - **Your own API keys** added to Continue Hub secrets + - **Your own API keys** added to Continue Mission Control secrets The agent will automatically detect and use your configuration along with the Atlassian MCP for Jira, Confluence, and Compass operations. @@ -485,7 +485,7 @@ After completing this guide, you have a complete **AI-powered Atlassian workflow How MCP works with Continue agents - + Create and manage your agents diff --git a/docs/guides/chrome-devtools-mcp-performance.mdx b/docs/guides/chrome-devtools-mcp-performance.mdx index 8e185ef4a14..d63e7c5d08c 100644 --- a/docs/guides/chrome-devtools-mcp-performance.mdx +++ b/docs/guides/chrome-devtools-mcp-performance.mdx @@ -65,7 +65,7 @@ After completing **Quick Setup** above, you have two paths to get started: - Visit the [Chrome Dev Tools Agent](https://hub.continue.dev/continuedev/chrome-dev-tools-agent) on Continue Hub and click **"Install Agent"** or run: + Visit the [Chrome Dev Tools Agent](https://hub.continue.dev/continuedev/chrome-dev-tools-agent) on Continue Mission Control and click **"Install Agent"** or run: ```bash cn --agent continuedev/chrome-dev-tools-agent @@ -96,7 +96,7 @@ After completing **Quick Setup** above, you have two paths to get started: - Visit the [Chrome DevTools MCP](https://hub.continue.dev/google/chrome-devtools-mcp) on Continue Hub and add it to your assistant, or add this to your configuration: + Visit the [Chrome DevTools MCP](https://hub.continue.dev/google/chrome-devtools-mcp) on Continue Mission Control and add it to your assistant, or add this to your configuration: ```yaml name: Chrome DevTools MCP @@ -140,7 +140,7 @@ After completing **Quick Setup** above, you have two paths to get started: To use the pre-built agent, you need either: - **Continue CLI Pro Plan** with the models add-on, OR - - **Your own API keys** added to Continue Hub secrets + - **Your own API keys** added to Continue Mission Control secrets - **Chrome browser** installed on your system - **Node.js 20+** to run the MCP via npx @@ -786,7 +786,7 @@ Set up automated regression detection: Official Chrome DevTools MCP repository - + Explore more MCP integrations diff --git a/docs/guides/cli.mdx b/docs/guides/cli.mdx index ac54e632f4b..d3584f8836a 100644 --- a/docs/guides/cli.mdx +++ b/docs/guides/cli.mdx @@ -52,7 +52,7 @@ echo "$(git diff) Generate a conventional commit name for the current git change ## How to Configure Continue CLI -`cn` uses [`config.yaml`](/reference), the exact same configuration file as Continue. This means that you can log in to [Continue Hub](/hub/introduction) or use your existing local configuration. +`cn` uses [`config.yaml`](/reference), the exact same configuration file as Continue. This means that you can log in to [Continue Mission Control](/hub/introduction) or use your existing local configuration. To switch between configurations, you can use the `/config` slash command in `cn`, or you can start it with the `--config` flag (e.g. `cn --config continuedev/default-agent` or `cn --config ~/.continue/config.yaml`). @@ -62,7 +62,7 @@ Learn how to add custom models [here](/customize/overview). Then, you can use th ### How to Configure Rules -`cn` supports [rules](/customize/deep-dives/rules) in the same way as the Continue IDE extensions. You can also use the `--rule` flag to manually include a rule from the hub. For example, `cn --rule nate/spanish` will tell `cn` to use [this rule](https://hub.continue.dev/nate/spanish) to always speak in Spanish. +`cn` supports [rules](/customize/deep-dives/rules) in the same way as the Continue IDE extensions. You can also use the `--rule` flag to manually include a rule from Mission Control. For example, `cn --rule nate/spanish` will tell `cn` to use [this rule](https://hub.continue.dev/nate/spanish) to always speak in Spanish. ### How to Configure Tools diff --git a/docs/guides/configuring-models-rules-tools.mdx b/docs/guides/configuring-models-rules-tools.mdx index 76d69e3045b..5a6cec90dee 100644 --- a/docs/guides/configuring-models-rules-tools.mdx +++ b/docs/guides/configuring-models-rules-tools.mdx @@ -176,6 +176,6 @@ models: Now that you understand how models, rules, and tools work, explore: - **[Config Reference](/reference)**: Detailed documentation of all available properties -- **[Continue Hub](https://hub.continue.dev)**: Browse community models, rules, and tools +- **[Continue Mission Control](https://hub.continue.dev)**: Browse community models, rules, and tools - **[Custom Context Providers](/customize/deep-dives/custom-providers)**: Create advanced context integrations - **[Model Roles](/customize/model-roles/intro)**: Understanding how different models work together diff --git a/docs/guides/continue-docs-mcp-cookbook.mdx b/docs/guides/continue-docs-mcp-cookbook.mdx index e3218c60561..e58d9c3e14b 100644 --- a/docs/guides/continue-docs-mcp-cookbook.mdx +++ b/docs/guides/continue-docs-mcp-cookbook.mdx @@ -478,8 +478,8 @@ Want to create documentation MCPs for your own projects? Mintlify makes it easy: [Learn more about Mintlify MCP generation →](https://www.mintlify.com/blog/generate-mcp-servers-for-your-docs) - - Share your docs MCP on [Continue Hub](https://hub.continue.dev/new?type=mcp) so others can use it with Continue agents. + + Share your docs MCP on [Continue Mission Control](https://hub.continue.dev/new?type=mcp) so others can use it with Continue agents. diff --git a/docs/guides/dlt-mcp-continue-cookbook.mdx b/docs/guides/dlt-mcp-continue-cookbook.mdx index 9c044688141..40346d9e4f8 100644 --- a/docs/guides/dlt-mcp-continue-cookbook.mdx +++ b/docs/guides/dlt-mcp-continue-cookbook.mdx @@ -80,14 +80,14 @@ After ensuring you meet the **Prerequisites** above, you have two paths to get s - - Go to the [Continue Hub](https://hub.continue.dev) and [create a new agent](https://hub.continue.dev/new?type=agent). + + Go to the [Continue Mission Control](https://hub.continue.dev) and [create a new agent](https://hub.continue.dev/new?type=agent). - - Visit the [dlt MCP on Continue Hub](https://hub.continue.dev/dlthub/dlt-mcp) and click **Install** to add it to the agent you created in the step above. + + Visit the [dlt MCP on Continue Mission Control](https://hub.continue.dev/dlthub/dlt-mcp) and click **Install** to add it to the agent you created in the step above. - This will add dlt MCP to your agent's available tools. The Hub listing automatically configures the MCP command. + This will add dlt MCP to your agent's available tools. The Mission Control listing automatically configures the MCP command. **Alternative installation methods:** @@ -119,7 +119,7 @@ After ensuring you meet the **Prerequisites** above, you have two paths to get s To use the pre-built [dlt Agent](https://hub.continue.dev/continuedev/dlt-agent), you need either: - **Continue CLI Pro Plan** with the models add-on, OR - - **Your own API keys** added to Continue Hub secrets (same as manual setup) + - **Your own API keys** added to Continue Mission Control secrets (same as manual setup) The agent will automatically detect and use your configuration along with the pre-configured dlt MCP for pipeline operations. @@ -152,7 +152,7 @@ After ensuring you meet the **Prerequisites** above, you have two paths to get s Now you can use natural language prompts to develop and debug your dlt pipelines. The Continue agent automatically calls the appropriate dlt MCP tools. -You can add prompts to your agent's configuration for easy access in future sessions. Go to your agent in the [Continue Hub](https://hub.continue.dev), click **Edit**, and add prompts under the **Prompts** section. +You can add prompts to your agent's configuration for easy access in future sessions. Go to your agent in the [Continue Mission Control](https://hub.continue.dev), click **Edit**, and add prompts under the **Prompts** section. @@ -400,7 +400,7 @@ Test the connection and report any issues." **Verification Steps:** - - dlt MCP is installed via [Continue Hub](https://hub.continue.dev/dlthub/dlt-mcp) + - dlt MCP is installed via [Continue Mission Control](https://hub.continue.dev/dlthub/dlt-mcp) - Pipeline directory is accessible - Destination database credentials are configured - Pipeline has been run at least once @@ -436,7 +436,7 @@ After completing this guide, you have a complete **AI-powered data pipeline deve Complete dlt platform documentation - + Explore more MCP integrations and agents - Get your API key from [Continue Hub](https://hub.continue.dev/settings/api-keys) and set: + Get your API key from [Continue Mission Control](https://hub.continue.dev/settings/api-keys) and set: ```bash export CONTINUE_API_KEY=your_key_here ``` @@ -355,7 +355,7 @@ Ready to implement automated documentation with Continue CLI? Here are some help Checkout this video from Tetrate about using Continue Agents to help with writing your docs. - + Browse pre-built agents and configurations from the Continue community. diff --git a/docs/guides/github-mcp-continue-cookbook.mdx b/docs/guides/github-mcp-continue-cookbook.mdx index 4af46d931ec..b994025de5d 100644 --- a/docs/guides/github-mcp-continue-cookbook.mdx +++ b/docs/guides/github-mcp-continue-cookbook.mdx @@ -33,7 +33,7 @@ For all options, first: - Add your `GITHUB_TOKEN` to your [Continue Hub agent's environment variables](https://hub.continue.dev/settings). + Add your `GITHUB_TOKEN` to your [Continue Mission Control agent's environment variables](https://hub.continue.dev/settings). @@ -45,7 +45,7 @@ For all options, first: ## GitHub MCP Workflow Options - Use the GitHub MCP from Continue Hub for one-click setup, or add it via CLI. + Use the GitHub MCP from Continue Mission Control for one-click setup, or add it via CLI. After ensuring you meet the **Prerequisites** above, you have two paths to get started: @@ -53,8 +53,8 @@ After ensuring you meet the **Prerequisites** above, you have two paths to get s - - Visit the [GitHub Project Manager Agent](https://hub.continue.dev/continuedev/github-project-manager-agent) on Continue Hub and click **Install** to add it to your agent. + + Visit the [GitHub Project Manager Agent](https://hub.continue.dev/continuedev/github-project-manager-agent) on Continue Mission Control and click **Install** to add it to your agent. The listing provides a pre-configured MCP block; add your `GITHUB_TOKEN` in Hub. @@ -75,8 +75,8 @@ After ensuring you meet the **Prerequisites** above, you have two paths to get s - - Go to the [Continue Hub](https://hub.continue.dev) and [create a new agent](https://hub.continue.dev/new?type=agent). + + Go to the [Continue Mission Control](https://hub.continue.dev) and [create a new agent](https://hub.continue.dev/new?type=agent). @@ -112,7 +112,7 @@ After ensuring you meet the **Prerequisites** above, you have two paths to get s To use GitHub MCP with Continue CLI, you need either: - **Continue CLI Pro Plan** with the models add-on, OR - - **Your own API keys** added to Continue Hub secrets + - **Your own API keys** added to Continue Mission Control secrets The agent will automatically detect and use your configuration along with the GitHub MCP for issue and PR operations. @@ -298,7 +298,7 @@ jobs: - **Missing or invalid token:** Ensure `GITHUB_TOKEN` is set and has the required scopes. Try a minimal test: “List 3 open issues in this repo”. - **Permissions errors on comment:** Your token must include `public_repo` (public) or `repo` (private) to write comments. - **Rate limiting:** Reduce frequency or filter queries; consider using a PAT distinct from the default Actions token when running in CI. -- **MCP connection timeout:** If using custom YAML, increase `connectionTimeout` or verify the `command`/`args` from the Hub listing. +- **MCP connection timeout:** If using custom YAML, increase `connectionTimeout` or verify the `command`/`args` from Mission Control listing. ## What You've Built @@ -328,13 +328,13 @@ After completing this guide, you have a complete **AI-powered GitHub workflow sy - Anthropic GitHub MCP on Continue Hub + Anthropic GitHub MCP on Continue Mission Control How MCP works with Continue agents - Pre-configured agent on Continue Hub + Pre-configured agent on Continue Mission Control Official GitHub MCP server README diff --git a/docs/guides/github-pr-review-bot.mdx b/docs/guides/github-pr-review-bot.mdx index d95a7c12049..f4e853d25b6 100644 --- a/docs/guides/github-pr-review-bot.mdx +++ b/docs/guides/github-pr-review-bot.mdx @@ -494,7 +494,7 @@ After completing this setup, you have an **AI-powered code review system** that: Learn more about Continue CLI capabilities - + Browse shared configs and create your own diff --git a/docs/guides/netlify-mcp-continuous-deployment.mdx b/docs/guides/netlify-mcp-continuous-deployment.mdx index 6bc19d5a166..830fcc730a8 100644 --- a/docs/guides/netlify-mcp-continuous-deployment.mdx +++ b/docs/guides/netlify-mcp-continuous-deployment.mdx @@ -82,7 +82,7 @@ After completing **Quick Setup** above, you have two paths to get started: - Visit the [Netlify Continuous AI Agent](https://hub.continue.dev/continuedev/netlify-continuous-ai-agent) on Continue Hub and click **"Install Agent"** or run: + Visit the [Netlify Continuous AI Agent](https://hub.continue.dev/continuedev/netlify-continuous-ai-agent) on Continue Mission Control and click **"Install Agent"** or run: ```bash cn --agent continuedev/netlify-continuous-ai-agent @@ -128,7 +128,7 @@ After completing **Quick Setup** above, you have two paths to get started: Install the [Netlify Development Rules](https://hub.continue.dev/netlify/netlify-development) bundle for best practices: - 1. Visit the bundle page on Continue Hub + 1. Visit the bundle page on Continue Mission Control 2. Click **"Install Rules"** 3. Rules automatically apply to your agent @@ -157,7 +157,7 @@ After completing **Quick Setup** above, you have two paths to get started: To use the pre-built agent, you need either: - **Continue CLI Pro Plan** with the models add-on, OR - - **Your own API keys** added to Continue Hub secrets + - **Your own API keys** added to Continue Mission Control secrets The agent will automatically detect and use your configuration along with the Netlify MCP for deployment operations. @@ -705,14 +705,14 @@ The Netlify Performance Rules enforce: ## Next Steps -- Install [Netlify MCP](https://hub.continue.dev/netlify/netlify-mcp) from Continue Hub +- Install [Netlify MCP](https://hub.continue.dev/netlify/netlify-mcp) from Continue Mission Control - Set up [Performance Monitoring](https://docs.netlify.com/analytics/get-started/) - Configure [A/B Testing](https://docs.netlify.com/split-testing/overview/) - Join the [Continue Discord](https://discord.gg/continue) for support ## Resources -- [Netlify MCP on Continue Hub](https://hub.continue.dev/netlify/netlify-mcp) +- [Netlify MCP on Continue Mission Control](https://hub.continue.dev/netlify/netlify-mcp) - [Core Web Vitals Guide](https://web.dev/vitals/) - [Netlify Analytics Documentation](https://docs.netlify.com/analytics/) - [Continue Performance Guides](https://docs.continue.dev/guides) diff --git a/docs/guides/ollama-guide.mdx b/docs/guides/ollama-guide.mdx index 77ca3fd0acb..e8dfe798f69 100644 --- a/docs/guides/ollama-guide.mdx +++ b/docs/guides/ollama-guide.mdx @@ -84,7 +84,7 @@ There are multiple ways to configure Ollama models in Continue: ### Method 1: Using Hub Model Blocks in Local config.yaml -The easiest way is to use [pre-configured model blocks](/reference#local-blocks) from the Continue Hub in your local configuration: +The easiest way is to use [pre-configured model blocks](/reference#local-blocks) from the Continue Mission Control in your local configuration: ```yaml title="~/.continue/configs/config.yaml" name: My Local Config @@ -97,11 +97,11 @@ models: ``` - **Important**: Hub blocks only provide configuration - you still need to pull - the model locally. The hub block `ollama/deepseek-r1-32b` configures Continue + **Important**: Blocks only provide configuration - you still need to pull + the model locally. The block `ollama/deepseek-r1-32b` configures Continue to use `model: deepseek-r1:32b`, but the actual model must be installed: ```bash - # Check what the hub block expects (view on hub.continue.dev) + # Check what the block expects (view on hub.continue.dev) # Then pull that exact model tag locally ollama pull deepseek-r1:32b # Required for ollama/deepseek-r1-32b hub block ``` @@ -146,7 +146,7 @@ You can update `apiBase` with the IP address of a remote machine serving Ollama. ### Method 3: Manual Configuration -For custom configurations or models not on the hub: +For custom configurations or models not in Mission Control: ```yaml models: diff --git a/docs/guides/overview.mdx b/docs/guides/overview.mdx index 214c9d996f8..9d32a0cbbf5 100644 --- a/docs/guides/overview.mdx +++ b/docs/guides/overview.mdx @@ -54,8 +54,8 @@ Step-by-step guides for integrating Model Context Protocol (MCP) servers with Co Automated error analysis with Sentry MCP to identify patterns and create actionable GitHub issues - - Integrate Snyk MCP via Continue Hub to scan code, deps, IaC, and containers + + Integrate Snyk MCP via Continue Mission Control to scan code, deps, IaC, and containers diff --git a/docs/guides/posthog-github-continuous-ai.mdx b/docs/guides/posthog-github-continuous-ai.mdx index 621e4b51dcf..157b3c823e0 100644 --- a/docs/guides/posthog-github-continuous-ai.mdx +++ b/docs/guides/posthog-github-continuous-ai.mdx @@ -98,9 +98,9 @@ First, you'll need to gather your PostHog and GitHub API credentials and add the See https://docs.continue.dev/hub/secrets/secret-types#secret-types for adding secrets -You only need to configure the PostHog MCP credential - it automatically handles project selection. To add environment variables to your Continue Hub account: +You only need to configure the PostHog MCP credential - it automatically handles project selection. To add environment variables to your Continue Mission Control account: -1. Go to the [Continue Hub](https://hub.continue.dev) +1. Go to the [Continue Mission Control](https://hub.continue.dev) 2. Sign in to your account 3. Navigate to your user settings 4. Look for the "Secrets" section @@ -134,7 +134,7 @@ You only need to configure the PostHog MCP credential - it automatically handles - Visit the [PostHog Continuous AI Agent](https://hub.continue.dev/continuedev/posthog-continuous-ai-agent) on Continue Hub and click **"Install Agent"** or run: + Visit the [PostHog Continuous AI Agent](https://hub.continue.dev/continuedev/posthog-continuous-ai-agent) on Continue Mission Control and click **"Install Agent"** or run: ```bash cn --agent continuedev/posthog-continuous-ai-agent @@ -171,7 +171,7 @@ You only need to configure the PostHog MCP credential - it automatically handles ``` - In the Continue Hub, add the [PostHog GitHub Continuous AI Rules](https://hub.continue.dev/bekah-hawrot-weigel/posthog-github-continuous-ai-rules) to your account for better formatting and error handling. + In the Continue Mission Control, add the [PostHog GitHub Continuous AI Rules](https://hub.continue.dev/bekah-hawrot-weigel/posthog-github-continuous-ai-rules) to your account for better formatting and error handling. Use this prompt with Continue CLI to analyze PostHog data and create GitHub issues: @@ -203,7 +203,7 @@ You only need to configure the PostHog MCP credential - it automatically handles To use the pre-built agent, you need either: - **Continue CLI Pro Plan** with the models add-on, OR - - **Your own API keys** added to Continue Hub secrets + - **Your own API keys** added to Continue Mission Control secrets The agent will automatically detect and use your configuration. @@ -355,6 +355,6 @@ Consider enhancing your workflow with these advanced Continue CLI prompts: - [PostHog Feature Flags](https://posthog.com/docs/feature-flags) - [PostHog Error Tracking](https://posthog.com/docs/error-tracking) - [GitHub CLI Documentation](https://cli.github.com/) -- [GitHub MCP on Continue Hub](https://hub.continue.dev/github/github-mcp) (alternative option) +- [GitHub MCP on Continue Mission Control](https://hub.continue.dev/github/github-mcp) (alternative option) - [Continue CLI Guide](https://docs.continue.dev/guides/cli) - [Continuous AI Best Practices](https://blog.continue.dev/what-is-continuous-ai-a-developers-guide/) diff --git a/docs/guides/sanity-mcp-continue-cookbook.mdx b/docs/guides/sanity-mcp-continue-cookbook.mdx index c5a92b6f707..9e01aba862f 100644 --- a/docs/guides/sanity-mcp-continue-cookbook.mdx +++ b/docs/guides/sanity-mcp-continue-cookbook.mdx @@ -72,7 +72,7 @@ After ensuring you meet the **Prerequisites** above, you have two paths to get s - Visit the [Sanity Assistant Agent](https://hub.continue.dev/continuedev/sanity-assistant-agent) on Continue Hub and click **"Install Config"** or run: + Visit the [Sanity Assistant Agent](https://hub.continue.dev/continuedev/sanity-assistant-agent) on Continue Mission Control and click **"Install Config"** or run: ```bash cn --agent continuedev/sanity-assistant-agent @@ -110,14 +110,14 @@ After ensuring you meet the **Prerequisites** above, you have two paths to get s - - Go to the [Continue Hub](https://hub.continue.dev) and [create a new agent](https://hub.continue.dev/new?type=agent). + + Go to the [Continue Mission Control](https://hub.continue.dev) and [create a new agent](https://hub.continue.dev/new?type=agent). - - Visit the [Sanity MCP on Continue Hub](https://hub.continue.dev/sanity/sanity-mcp) and click **"Install"** to add it to the agent you created in the step above. + + Visit the [Sanity MCP on Continue Mission Control](https://hub.continue.dev/sanity/sanity-mcp) and click **"Install"** to add it to the agent you created in the step above. - This will add Sanity MCP to your agent's available tools. The Hub listing automatically configures the MCP connection. + This will add Sanity MCP to your agent's available tools. The Mission Control listing automatically configures the MCP connection. **Alternative installation methods:** @@ -158,7 +158,7 @@ After ensuring you meet the **Prerequisites** above, you have two paths to get s To use the pre-built Sanity Assistant agent, you need either: - **Continue CLI Pro Plan** with the models add-on, OR - - **Your own API keys** added to Continue Hub secrets + - **Your own API keys** added to Continue Mission Control secrets The agent will automatically detect and use your configuration along with the pre-configured Sanity MCP for content operations. Note that OAuth authentication will be required on first use. @@ -219,7 +219,7 @@ With everything set up, you're ready for your first AI-powered content conversat Now you can use natural language prompts to manage your Sanity content and schemas. The Continue agent automatically calls the appropriate Sanity MCP tools. -You can add prompts to your agent's configuration for easy access in future sessions. Go to your agent in the [Continue Hub](https://hub.continue.dev), click **Edit**, and add prompts under the **Prompts** section. +You can add prompts to your agent's configuration for easy access in future sessions. Go to your agent in the [Continue Mission Control](https://hub.continue.dev), click **Edit**, and add prompts under the **Prompts** section. @@ -509,7 +509,7 @@ then provide a corrected version that achieves the intended result." **Verification Steps:** - - Sanity MCP is installed via [Continue Hub](https://hub.continue.dev/sanity/sanity-mcp) + - Sanity MCP is installed via [Continue Mission Control](https://hub.continue.dev/sanity/sanity-mcp) - Project is authenticated with Sanity - Schema files are present and valid - Dataset permissions are correctly configured @@ -545,7 +545,7 @@ After completing this guide, you have a complete **AI-powered content management Complete Sanity platform documentation - + Explore more MCP integrations and agents - Visit the [Sentry Continuous AI Agent](https://hub.continue.dev/continuedev/sentry-continuous-ai-agent) on Continue Hub and click **"Install Agent"** or run: + Visit the [Sentry Continuous AI Agent](https://hub.continue.dev/continuedev/sentry-continuous-ai-agent) on Continue Mission Control and click **"Install Agent"** or run: ```bash cn --agent continuedev/sentry-continuous-ai-agent @@ -219,7 +219,7 @@ First, you'll need to gather your Sentry and GitHub API credentials. To use the pre-built agent, you need either: - **Continue CLI Pro Plan** with the models add-on, OR - - **Your own API keys** added to Continue Hub secrets (same as Step 1) + - **Your own API keys** added to Continue Mission Control secrets (same as Step 1) The agent will automatically detect and use your configuration. For Sentry MCP: - **Sentry account** with at least one project diff --git a/docs/guides/snyk-mcp-continue-cookbook.mdx b/docs/guides/snyk-mcp-continue-cookbook.mdx index efc900a29ac..06c50645ad4 100644 --- a/docs/guides/snyk-mcp-continue-cookbook.mdx +++ b/docs/guides/snyk-mcp-continue-cookbook.mdx @@ -104,14 +104,14 @@ After ensuring you meet the **Prerequisites** above, you have two paths to get s - - Go to the [Continue Hub](https://hub.continue.dev) and [create a new agent](https://hub.continue.dev/new?type=agent). + + Go to the [Continue Mission Control](https://hub.continue.dev) and [create a new agent](https://hub.continue.dev/new?type=agent). - + Visit the [Snyk Continuous AI Agent](https://hub.continue.dev/continuedev/snyk-continuous-ai-agent) and click **Install** to add it to the agent you created in the step above. - This will add Snyk MCP to your agent's available tools. The Hub listing automatically configures the MCP command: + This will add Snyk MCP to your agent's available tools. The Mission Control listing automatically configures the MCP command: ```bash npx -y snyk@latest mcp -t stdio ``` @@ -132,7 +132,7 @@ After ensuring you meet the **Prerequisites** above, you have two paths to get s - Install the [Snyk Secure-at-Inception rules](https://hub.continue.dev/snyk/secure-at-inception) from the Hub to enable automatic security scanning. + Install the [Snyk Secure-at-Inception rules](https://hub.continue.dev/snyk/secure-at-inception) from Mission Control to enable automatic security scanning. **How to add rules to your agent:** 1. Visit the rules link above and click **Install** @@ -161,7 +161,7 @@ After ensuring you meet the **Prerequisites** above, you have two paths to get s To use the pre-built agent, you need either: - **Continue CLI Pro Plan** with the models add-on, OR - - **Your own API keys** added to Continue Hub secrets (same as manual setup) + - **Your own API keys** added to Continue Mission Control secrets (same as manual setup) The agent will automatically detect and use your configuration along with the pre-configured Snyk MCP for security scanning operations. @@ -174,7 +174,7 @@ After ensuring you meet the **Prerequisites** above, you have two paths to get s Now you can use natural language prompts to run comprehensive security scans. The Continue agent automatically calls the appropriate Snyk MCP tools. -You can add prompts to your agent's configuration for easy access in future sessions. Go to your agent in the [Continue Hub](https://hub.continue.dev), click **Edit**, and add prompts under the **Prompts** section. +You can add prompts to your agent's configuration for easy access in future sessions. Go to your agent in the [Continue Mission Control](https://hub.continue.dev), click **Edit**, and add prompts under the **Prompts** section. @@ -594,7 +594,7 @@ jobs: Implement automated security policies using Continue's rule system. See the [Rules deep dive](/customize/deep-dives/rules) for authoring tips. - **Coming Soon**: These security guardrail prompts will be available as pre-configured rules on the Continue Hub for easy installation. + **Coming Soon**: These security guardrail prompts will be available as pre-configured rules on the Continue Mission Control for easy installation. @@ -627,7 +627,7 @@ Implement automated security policies using Continue's rule system. See the [Rul - Enable the **Secure-at-Inception** rules from the Hub to automatically apply + Enable the **Secure-at-Inception** rules from Mission Control to automatically apply these guardrails to all code generation and modifications. @@ -687,7 +687,7 @@ After completing this guide, you have a complete **AI-powered security system** Complete Snyk platform documentation - + Explore more MCP integrations and agents - Visit the [Supabase Agent](https://hub.continue.dev/continuedev/supabase-agent) on Continue Hub and click **"Install Agent"** or run: + Visit the [Supabase Agent](https://hub.continue.dev/continuedev/supabase-agent) on Continue Mission Control and click **"Install Agent"** or run: ```bash cn --agent continuedev/supabase-agent @@ -208,7 +208,7 @@ First, you'll need to set up access to your Supabase project. To use the pre-built agent, you need either: - **Continue CLI Pro Plan** with the models add-on, OR - - **Your own API keys** added to Continue Hub secrets + - **Your own API keys** added to Continue Mission Control secrets The agent will automatically detect and use your configuration. For Supabase MCP: - **Supabase account** with at least one project diff --git a/docs/guides/understanding-configs.mdx b/docs/guides/understanding-configs.mdx index 115e2114048..6d4c451d7ac 100644 --- a/docs/guides/understanding-configs.mdx +++ b/docs/guides/understanding-configs.mdx @@ -35,7 +35,7 @@ Before we dive into the specifics, let's understand how to access your configura ## What Are Hub Configurations: The Managed Experience -Hub Configurations represent the "it just works" philosophy. When you [sign in to Continue Hub](https://auth.continue.dev/), you gain access to a curated ecosystem of established configurations that sync seamlessly across all your development environments. +Hub Configurations represent the "it just works" philosophy. When you [sign in to Continue Mission Control](https://auth.continue.dev/), you gain access to a curated ecosystem of established configurations that sync seamlessly across all your development environments. ### Why Should You Choose Hub Configs? @@ -43,7 +43,7 @@ Hub Configurations represent the "it just works" philosophy. When you [sign in t - **Instant Setup**: Browse the [configuration marketplace](https://hub.continue.dev) and add any config to your account with a single click - **Web-Based Management**: Configure models, add secrets, and customize settings through an intuitive web interface—no JSON editing required -- **Automatic Synchronization**: Make a change on the hub, and it reflects immediately across all your IDE instances +- **Automatic Synchronization**: Make a change on Mission Control, and it reflects immediately across all your IDE instances - **Team Collaboration**: Share custom configurations with your team, ensuring everyone uses the same optimized configurations ![nextjs config](/images/nextjs-assistant.png) @@ -54,14 +54,14 @@ The journey from zero to AI-powered coding takes just four steps: 1. **Select Your Config**: Click the config selector in your IDE's Continue panel 2. **Explore or Create**: Browse community configurations or craft your own specialized setup -3. **Secure Your Keys**: Add API keys as [User Secrets](https://hub.continue.dev/settings/secrets) in the hub—they're encrypted and never exposed +3. **Secure Your Keys**: Add API keys as [User Secrets](https://hub.continue.dev/settings/secrets) in Mission Control—they're encrypted and never exposed 4. **Sync and Code**: Click "Reload config" to pull your latest settings Pro tip: Hub configurations are perfect for teams. Create a custom config with your team's coding standards, preferred models, and context sources, then share it with a simple link. ### How to Manage Hub Configs -All Hub config management happens through [the Hub](https://hub.continue.dev). For detailed customization, see our guide on [Editing a Config](/hub/configs/edit-a-config). +All Hub config management happens through [Mission Control](https://hub.continue.dev). For detailed customization, see our guide on [Editing a Config](/hub/configs/edit-a-config). ## What Are Local Configs: The Power User's Choice @@ -183,7 +183,7 @@ You can switch between them seamlessly using the configs selector in your IDE. **Config Not Available?** -- Verify it's added to your account on the hub +- Verify it's added to your account on Mission Control - Check if it requires specific API keys ### Local Config Issues diff --git a/docs/home.mdx b/docs/home.mdx index 63280ca849b..06e8c05ae02 100644 --- a/docs/home.mdx +++ b/docs/home.mdx @@ -19,4 +19,4 @@ description: "Learn how Continue enables developers to embrace continuous AI, en 2. Try out [Continue CLI (cn)](https://docs.continue.dev/guides/cli) and give us feedback -3. Discover the models, prompts, rules, MCP tools, and agents you need to automate your workflows with AI on [Continue Hub](https://hub.continue.dev/) +3. Discover the models, prompts, rules, MCP tools, and agents you need to automate your workflows with AI on [Continue Mission Control](https://hub.continue.dev/) diff --git a/docs/hub/introduction.mdx b/docs/hub/introduction.mdx deleted file mode 100644 index 3ae6e5d9448..00000000000 --- a/docs/hub/introduction.mdx +++ /dev/null @@ -1,114 +0,0 @@ ---- -title: "Continue Hub" -description: "Central platform for discovering, creating, and sharing AI coding configurations, agents, and components with organization-level governance" ---- - -[Continue Hub](https://hub.continue.dev) is your central platform for AI-powered development. Discover pre-built configurations, create custom agents, and manage components that power your coding workflow. - -## What You Can Do on the Hub - -![Continue Hub Overview](/images/hub/assets/images/hub-overview.jpg) - - - - - Manage organizations, API keys, secrets, and integrations. Configure models, MCP servers, and connected tools all in one place. - - - Search existing agents or build custom, reusable agents. Standardize prompts, rules, and tools to match your workflows and share with your team. - - - Launch and monitor agents across your repositories. Trigger on events or schedules and track performance. - - - - -## Hub Components - -Agents are built from reusable components that you can create, share, and customize: - - - - - - Large Language Models from various providers (OpenAI, Anthropic, etc.) configured for specific roles like chat, autocomplete, or editing - - - - - - Model Context Protocol servers that provide tools and capabilities like database access, web search, or custom functions - - - - - - Guidelines that shape AI behavior - coding standards, constraints, or specific instructions for your domain - - - - - - Reusable instructions for common tasks, optimized for specific workflows or coding patterns - - - - - -## Creating Components - - - - Components are the building blocks for agents. When you create a component on the hub, it becomes available according to the permissions you set. - - - - - - - - Start with a blank template: - - - Select New Rules, Prompts, Configs, or Agents from the Hub navigation - - Click 'New' to start with a blank template - - Configure by filling in the inputs to create your markdown configuration - ![hub navigation new](../images/hub/hub-nav.png) - - - - - - Customize an existing component: - - - Browse the [Hub](https://hub.continue.dev/) for what you need - - Click 'Remix' to create a copy that you can customize - - Modify the configuration for your specific needs - - Save your customized version - ![hub remix button](../images/hub/block-remix-button.png) - - - - - - -### Component Permissions - -Set visibility for your components: - -- **Personal**: Only you can see and use -- **Public**: Anyone can discover and use -- **Organization**: Team members can access - -### Component Inputs - -Some components can receive values, including secrets, as inputs through templating. For values that the user needs to set, you can use template variables (e.g. `${{ inputs.API_KEY}}`). Then, the user can set `API_KEY: ${{ secrets.MY_API_KEY }}` in the `with` clause of their agent or config. - - -**Choosing between `secrets.` and `inputs.`** - -When creating blocks for the hub: -- Use `${{ inputs.INPUT_NAME }}` in your block definition when you want users to be able to customize which secret is used -- Users will then map their own secrets using `${{ secrets.SECRET_NAME }}` in the `with` clause - -For personal or single-use configurations, you can skip the inputs layer and reference `${{ secrets.SECRET_NAME }}` directly in your block. - diff --git a/docs/hub/sharing.mdx b/docs/hub/sharing.mdx deleted file mode 100644 index 93a7a9de3f2..00000000000 --- a/docs/hub/sharing.mdx +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: "Sharing" -description: "Connect with the Continue community to discover, share, and collaborate on AI development tools." ---- - -## Community - -Join thousands of developers using Continue. Share experiences, get help, and contribute to the ecosystem. - -[Join our Discord Community →](https://discord.gg/vapESyrFmJ) - -## Publishing - -Share your custom assistants, blocks, and configurations with the Continue community. - -[Visit the Hub →](https://hub.continue.dev) - -## Browse Configurations - -Explore assistants created by the community for specific use cases and workflows. - -[Browse Configurations →](https://hub.continue.dev) - -## Using Configurations - -Learn how to discover, install, and use community-created assistants in your projects. - -[Learn About Configurations →](/hub/configs/intro) - ---- - -The Continue Hub makes it easy to leverage community knowledge and share your innovations with fellow developers. diff --git a/docs/ide-extensions/agent/how-to-customize.mdx b/docs/ide-extensions/agent/how-to-customize.mdx index b5ebb5272cb..c087a42bfd0 100644 --- a/docs/ide-extensions/agent/how-to-customize.mdx +++ b/docs/ide-extensions/agent/how-to-customize.mdx @@ -6,7 +6,7 @@ sidebarTitle: "Customize Agent Mode" ## How to Add Rules Blocks -Adding Rules can be done in your configuration locally or in the Hub. You can explore Rules on the Continue Hub and refer to the [Rules deep dive](/customize/deep-dives/rules) for more details. +Adding Rules can be done in your configuration locally or in Mission Control. You can explore Rules on the Continue Mission Control and refer to the [Rules deep dive](/customize/deep-dives/rules) for more details. ## How to Customize System Messages @@ -25,7 +25,7 @@ models: ## How to Add MCP Tools -You can add MCP servers to your configuration to give Agent mode access to more tools. Explore [MCP Servers on the Hub](https://hub.continue.dev/explore?type=mcpServers) and consult the [MCP guide](/customize/deep-dives/mcp) for more details. +You can add MCP servers to your configuration to give Agent mode access to more tools. Explore [MCP Servers on Mission Control](https://hub.continue.dev/explore?type=mcpServers) and consult the [MCP guide](/customize/deep-dives/mcp) for more details. ## How to Configure Tool Policies diff --git a/docs/ide-extensions/install.mdx b/docs/ide-extensions/install.mdx index ea413a8ba03..2b50cb1817b 100644 --- a/docs/ide-extensions/install.mdx +++ b/docs/ide-extensions/install.mdx @@ -34,7 +34,7 @@ The Continue logo will appear on the left sidebar. For a better experience, move -[Sign in to the hub](https://auth.continue.dev/) to get started +[Sign in to Mission Control](https://auth.continue.dev/) to get started @@ -64,7 +64,7 @@ Click `Install`, which will cause the Continue logo to show up on the right tool -[Sign in to the hub](https://auth.continue.dev/) to get started +[Sign in to Mission Control](https://auth.continue.dev/) to get started @@ -78,6 +78,6 @@ Click `Install`, which will cause the Continue logo to show up on the right tool ## Signing in -Click "Get started" to sign in to the hub and get started. +Click "Get started" to sign in to Mission Control and get started. ![Hub Onboarding in the Extension](../images/getting-started/images/hub-onboarding-card-81abd457b6d131c4b0aa89a5a6d647d3.png) diff --git a/docs/images/hub/assets/images/hub-overview.jpg b/docs/images/hub/assets/images/hub-overview.jpg deleted file mode 100644 index adbf435c1bc..00000000000 Binary files a/docs/images/hub/assets/images/hub-overview.jpg and /dev/null differ diff --git a/docs/index.mdx b/docs/index.mdx index 343eef56e52..6c4a2f2dc68 100644 --- a/docs/index.mdx +++ b/docs/index.mdx @@ -1,20 +1,54 @@ --- title: "Welcome to Continue" icon: book-open -description: "Kick off agents from the terminal, IDE, or Mission Control" +description: "Create, run, and automate AI agents across Mission Control, terminal, and CI/CD" --- +## Mission Control - **Launch background agents, iterate in terminal, and deploy workflows in CI/CD** + Central dashboard for managing Agents, Tasks, Workflows, and Integrations. + + + Trigger your Agent with a prompt, tools, and rules to complete a specific job. + + • Run manually or from your Inbox
+ • Reuse and share with teammates + + + Schedule recurring Tasks or connect webhooks to trigger Agents automatically. + + • Cron or webhook-based triggers
+ • Ideal for daily audits or status checks + + + +## Integrations + + Connect Continue to your existing developer tools to power Tasks and Workflows. + + + + + Enable repository access for Agents to read and create PRs. + + + Mention @Continue in Slack to trigger Agents and receive updates. + + + Automatically generate PRs to fix new issues from Sentry alerts. + + + + ## Continue CLI -Terminal-native AI coding assistance with TUI and headless modes. +Terminal-native AI coding assistance with TUI and headless modes. @@ -39,7 +73,7 @@ description: "Kick off agents from the terminal, IDE, or Mission Control" href="/cli/overview#tui-mode%3A-interactive-development" > Interactive terminal interface for development workflows -
+ • Automate builds & refactoring
• Pre-commit hooks & scripted fixes @@ -52,7 +86,7 @@ description: "Kick off agents from the terminal, IDE, or Mission Control" href="/cli/overview#headless-mode%3A-production-automation" > Automated AI coding for CI/CD and server environments -
+ • Run in CI/CD pipelines
• Batch processing & bulk operations @@ -63,10 +97,10 @@ description: "Kick off agents from the terminal, IDE, or Mission Control" ## IDE Extensions - - **Complement your CLI workflow** - Rich editor integrations for interactive - development. - + + Optional IDE extensions for real-time code editing and assistance. + + Install from VS Code Marketplace -
Real-time coding assistance and refactoring Install from JetBrains Plugin Repository -
- Autocomplete and multi-file edits - - - -## Core Features - - - - Multi-step workflows and complex task automation - - - Ask questions and explore your codebase - - - In-place code editing without breaking flow - - - Inline AI suggestions as you type - - - -## Configuration - - - - Connect your preferred AI models - - - Configure AI behavior and constraints - - - Extend functionality with MCP tools + Community supported for autocomplete and multi-file edits ## Resources - - Community models, rules, and tools + + Create your agents, run tasks, add workflows and integrations - TUI and headless workflow examples + Connect GitHub, Slack, and Sentry to power your automations. diff --git a/docs/hub/configs/create-a-config.mdx b/docs/mission-control/configs/create-a-config.mdx similarity index 89% rename from docs/hub/configs/create-a-config.mdx rename to docs/mission-control/configs/create-a-config.mdx index 04a7a026ee5..33845b71103 100644 --- a/docs/hub/configs/create-a-config.mdx +++ b/docs/mission-control/configs/create-a-config.mdx @@ -1,6 +1,6 @@ --- title: "How to Create a Config" -description: "Learn how to create custom AI coding configs in Continue Hub by remixing existing configs or building new ones from scratch with reusable blocks and YAML configuration." +description: "Learn how to create custom AI coding configs in Continue Mission Control by remixing existing configs or building new ones from scratch with reusable blocks and YAML configuration." sidebarTitle: "Create a Config" --- diff --git a/docs/hub/configs/edit-a-config.mdx b/docs/mission-control/configs/edit-a-config.mdx similarity index 77% rename from docs/hub/configs/edit-a-config.mdx rename to docs/mission-control/configs/edit-a-config.mdx index 5e1dd3c1446..7542a34d1b6 100644 --- a/docs/hub/configs/edit-a-config.mdx +++ b/docs/mission-control/configs/edit-a-config.mdx @@ -3,9 +3,9 @@ title: "How to Edit a Config" description: "New versions of a config can be created and published using the sidebar." --- -First, select a config either from the Hub search or one that you've installed. +First, select a config either from Mission Control search or one that you've installed. -While editing a config, you can explore the hub and click "+" to add it to your config. +While editing a config, you can explore Mission Control and click "+" to add it to your config. For tools or models that require secret values like API keys, you will see a small notification on its tile that will indicate if action is needed. diff --git a/docs/hub/configs/intro.mdx b/docs/mission-control/configs/intro.mdx similarity index 90% rename from docs/hub/configs/intro.mdx rename to docs/mission-control/configs/intro.mdx index 69094b8e708..2d07e581b16 100644 --- a/docs/hub/configs/intro.mdx +++ b/docs/mission-control/configs/intro.mdx @@ -70,7 +70,7 @@ You can interact with configs in three main ways: - Browse the [Continue Hub](https://hub.continue.dev/explore?type=assistants) to see what configs others have built + Browse the [Continue Mission Control](https://hub.continue.dev/explore?type=assistants) to see what configs others have built @@ -96,5 +96,5 @@ You can interact with configs in three main ways: ## Config Format -All configs follow the [`config.yaml`](/reference) format, whether you're using the hub interface or editing files locally. This ensures consistency between hub-managed and local configurations. +All configs follow the [`config.yaml`](/reference) format, whether you're using Mission Control interface or editing files locally. This ensures consistency between Mission Control-managed and local configurations. diff --git a/docs/hub/configs/use-a-config.mdx b/docs/mission-control/configs/use-a-config.mdx similarity index 97% rename from docs/hub/configs/use-a-config.mdx rename to docs/mission-control/configs/use-a-config.mdx index 1785adee5a2..2b69018fb86 100644 --- a/docs/hub/configs/use-a-config.mdx +++ b/docs/mission-control/configs/use-a-config.mdx @@ -5,7 +5,7 @@ description: "Learn how to add and use a custom configuration in Continue, inclu ## Steps to use a custom configuration in Continue -Once you've found the configuration you want to use on Continue Hub: +Once you've found the configuration you want to use on Continue Mission Control: 1. Click “Add Config” on its page 2. Add any required inputs (e.g. secrets like API keys) diff --git a/docs/hub/governance/creating-an-org.mdx b/docs/mission-control/governance/creating-an-org.mdx similarity index 95% rename from docs/hub/governance/creating-an-org.mdx rename to docs/mission-control/governance/creating-an-org.mdx index f8da55c3581..002e1a0a3e4 100644 --- a/docs/hub/governance/creating-an-org.mdx +++ b/docs/mission-control/governance/creating-an-org.mdx @@ -5,7 +5,7 @@ description: "To Create an Organization, click the organization selector in the ![create an org selector](/images/hub/governance/images/org-selector-4ea627afc7c0765633780920a0fbe16e.png) -1. Choose a name, which will be used as the display name for your organization throughout the hub +1. Choose a name, which will be used as the display name for your organization throughout Mission Control 2. Add a slug, which will be used for your org URL and as the prefix to all organization configuration slugs 3. Select an icon for your organization using the image uploader 4. Finally, add a Biography, which will be displayed on your org Home Page diff --git a/docs/hub/governance/org-permissions.mdx b/docs/mission-control/governance/org-permissions.mdx similarity index 100% rename from docs/hub/governance/org-permissions.mdx rename to docs/mission-control/governance/org-permissions.mdx diff --git a/docs/hub/governance/pricing.mdx b/docs/mission-control/governance/pricing.mdx similarity index 84% rename from docs/hub/governance/pricing.mdx rename to docs/mission-control/governance/pricing.mdx index 3dace0e4b7e..e56ef351783 100644 --- a/docs/hub/governance/pricing.mdx +++ b/docs/mission-control/governance/pricing.mdx @@ -1,6 +1,6 @@ --- title: "Pricing" -description: "Continue Hub pricing plans for individuals, teams, and enterprises, including the Models Add-On that provides access to frontier AI models for a flat monthly fee" +description: "Continue Mission Control pricing plans for individuals, teams, and enterprises, including the Models Add-On that provides access to frontier AI models for a flat monthly fee" --- ## Solo diff --git a/docs/mission-control/index.mdx b/docs/mission-control/index.mdx new file mode 100644 index 00000000000..18da8b3e68b --- /dev/null +++ b/docs/mission-control/index.mdx @@ -0,0 +1,125 @@ +--- +title: "Continue Mission Control" +description: "Your command center for Continue. Create Tasks, set up Workflows, manage Agents, connect Integrations, and share with your team—all in one place." +sidebarTitle: "Overview" +--- + +## What You Can Do in Mission Control + +Mission Control is where developers and teams use Continue to power everyday coding workflows. From quick one-off Tasks to fully automated pipelines, everything starts here. + + + + Trigger your AI Agents and review or approve the results. + + + Create, configure, and monitor your custom Agents across repositories. + + + Schedule recurring Tasks, connect webhooks to trigger Agents automatically, or add + + + Link GitHub, Slack, and Sentry to power your Tasks and Workflows. + + + +## Monitoring & Insights + + +Track performance, share configurations across your organization, and monitor agent activity in real time. + + + + + + Measure success rates, PR activity, and intervention trends across Agents. + + + + Share Agents and Workflows with teammates using built-in access controls. + + + + View active runs, logs, and outcomes for every Agent session. + + + +--- + + +## Components Behind Mission Control + +Mission Control uses your configured components to power Agents, Tasks, and Workflows: +Agents are built from reusable components that you can create, share, and customize: + + + + + + Large Language Models from various providers (OpenAI, Anthropic, etc.) configured for specific roles like chat, autocomplete, or editing + + + + + + Model Context Protocol servers that provide tools and capabilities like database access, web search, or custom functions + + + + + + Guidelines that shape AI behavior - coding standards, constraints, or specific instructions for your domain + + + + + + Reusable instructions for common tasks, optimized for specific workflows or coding patterns + + + + + + + + Components are the building blocks for agents that you can create new or remix from an existing component. When you create a component in mission control, it becomes available according to the permissions you set: Personal, Public, or Organization. + + + + + + +Some components can receive values, including secrets, as inputs through templating. For values that the user needs to set, you can use template variables (e.g. `${{ inputs.API_KEY}}`). Then, the user can set `API_KEY: ${{ secrets.MY_API_KEY }}` in the `with` clause of their agent or config. + + +**Choosing between `secrets.` and `inputs.`** + +When creating components for your Agent: +- Use `${{ inputs.INPUT_NAME }}` in your definition when you want users to be able to customize which secret is used +- Users will then map their own secrets using `${{ secrets.SECRET_NAME }}` in the `with` clause + +For personal or single-use configurations, you can skip the inputs layer and reference `${{ secrets.SECRET_NAME }}` directly. + + + +--- +## Get Started + + + + + + + Start with a prompt and run an Agent on demand. + + + + Automate your Tasks using cron schedules or webhooks. + + + + Connect GitHub, Slack, and Sentry to extend your Agents. + + + + \ No newline at end of file diff --git a/docs/mission-control/integrations/github.mdx b/docs/mission-control/integrations/github.mdx new file mode 100644 index 00000000000..06f2a2cd266 --- /dev/null +++ b/docs/mission-control/integrations/github.mdx @@ -0,0 +1,207 @@ +--- +title: "GitHub Integration" +description: "Connect to GitHub to allow Continue Agents to read and create PRs on your repositories" +--- + +## Overview + +Connect your GitHub account to Continue Mission Control to enable agents to interact with your repositories. Once connected, agents can read code, create pull requests, manage issues, and automate your development workflow. + + + + - Automatically create pull requests from agent tasks + - Read and analyze repository code and issues + - Manage project workflows and milestones + - Automate code reviews and quality checks + - Generate release notes and documentation + + + + +## Setup + + + + + + Go to your [Integrations Settings](https://hub.continue.dev/integrations). + + + + + + Click "Connect" next to GitHub and authorize the Continue app in your GitHub account. + + + + + + Choose whether to grant access to all repositories or select specific ones. You can always modify this later in your GitHub settings. + + + + + + Review and approve the requested permissions. Continue needs these to perform automated tasks on your behalf. + + + + + +## Use Cases + +### Automated Issue Resolution + +Create agents that automatically fix bugs and open PRs: + + + + **Task Example**: "Review issues labeled 'bug' and create PRs to fix any that are straightforward" + + **What the Agent Does**: + - Scans your repository for issues with the "bug" label + - Analyzes the bug description and reproduces the issue + - Generates a fix and creates a pull request + - Adds a link back to the original issue + + **Run in Mission Control**: Create as a scheduled automation or trigger manually + + + +### Pull Request Management + +Automate code reviews and PR maintenance: + + + + **Task Example**: "Review open PRs for code quality, security issues, and best practices" + + **What the Agent Does**: + - Analyzes code changes in open pull requests + - Identifies potential bugs, security vulnerabilities, or style issues + - Adds review comments with suggestions + - Approves PRs that meet quality standards + + **Run in Mission Control**: Set up as an automation triggered on new PRs + + + +### Documentation Generation + +Keep your docs up-to-date automatically: + + + + **Task Example**: "Update README and API documentation based on recent code changes" + + **What the Agent Does**: + - Detects changes to public APIs or features + - Generates updated documentation + - Creates a PR with doc updates + - Links documentation to related code changes + + **Run in Mission Control**: Schedule to run after releases or major merges + + + +### Project Management + +Automate issue triage and project organization: + + + + **Task Example**: "Triage new issues by adding labels, assigning to appropriate team members, and linking related issues" + + **What the Agent Does**: + - Analyzes new issue descriptions + - Applies relevant labels (bug, feature, documentation, etc.) + - Suggests team members to assign based on expertise + - Identifies and links related issues or PRs + + **Run in Mission Control**: Create as an automation triggered on new issues + + + +### Release Management + +Automate your release process: + + + + **Task Example**: "Generate release notes from merged PRs since last release and create a draft release" + + **What the Agent Does**: + - Collects all merged PRs since the last tag + - Categorizes changes (features, fixes, breaking changes) + - Generates formatted release notes + - Creates a draft GitHub release for review + + **Run in Mission Control**: Trigger manually or on a schedule before releases + + + +### Code Quality Monitoring + +Maintain code standards across your codebase: + + + + **Task Example**: "Scan the codebase for deprecated API usage and create issues with migration guides" + + **What the Agent Does**: + - Identifies usage of deprecated functions or libraries + - Generates migration recommendations + - Creates individual issues for each deprecated usage + - Provides code examples for the upgrade path + + **Run in Mission Control**: Schedule monthly or after dependency updates + + + +## Running GitHub Agents in Mission Control + +You can run GitHub-connected agents in two ways: + +### 1. Manual Tasks + +Trigger agents on-demand for specific tasks: + +1. Go to [Mission Control Agents](https://hub.continue.dev/agents) +2. Select or create a GitHub-enabled agent +3. Click "Run Agent" and provide your task description +4. Monitor progress and review results in real-time + +### 2. Automated Workflows + +Set up agents to run automatically: + +- **Scheduled**: Run daily, weekly, or on a custom schedule +- **Triggered**: Execute when specific events occur (new issues, PR opened, etc.) +- **Webhook**: Integrate with external services to trigger agents + + + + Start with manual tasks to test your agent's behavior, then convert successful workflows to automations once you're confident in the results. + + + + +## Support & Resources + + + + + + Comprehensive guide to using GitHub with Continue agents + + + + + + Automate code reviews with Continue + + + + + + diff --git a/docs/mission-control/integrations/index.mdx b/docs/mission-control/integrations/index.mdx new file mode 100644 index 00000000000..9485edb1a50 --- /dev/null +++ b/docs/mission-control/integrations/index.mdx @@ -0,0 +1,33 @@ +--- +title: "Overview" +description: "Connect GitHub, Slack, and Sentry to power richer Agents, Tasks, and Workflows." +sidebarTitle: "Overview" +--- + + +Integrations let Continue connect to the tools you already use, so Agents can read code, open pull requests, send messages, react to real-world events, and more. + + +Mission Control currently supports three first-class integrations: + + + + + Required for PR creation, repo access, diffs, and workflow triggers. + + + + Mention @continue to kick off Agents directly from Slack. + + + + Trigger Agents automatically when new Sentry issues appear. + + + + + +## Next Steps + + + \ No newline at end of file diff --git a/docs/mission-control/integrations/sentry.mdx b/docs/mission-control/integrations/sentry.mdx new file mode 100644 index 00000000000..40ac05351d4 --- /dev/null +++ b/docs/mission-control/integrations/sentry.mdx @@ -0,0 +1,314 @@ +--- +title: "Sentry Integration" +description: "Automatically triage and resolve errors with Continue Agents connected to Sentry" +--- + +## Overview + +Connect Sentry to Continue Mission Control to enable agents to automatically detect, analyze, and resolve production errors. When Sentry is enabled, Continue can generate PRs to fix issues, analyze error patterns, and maintain application health. + + + + - Automatically generate PRs to resolve new errors + - Analyze error patterns and identify root causes + - Prioritize issues based on impact and frequency + - Create detailed bug reports with stack traces + - Monitor error trends across releases + + + +## Setup + + + + + + Go to your [Integrations Settings](https://hub.continue.dev/integrations). + + + + + Click "Connect" and select Sentry. You'll need the following credentials: + + - **Sentry Organization Slug**: Your organization name (e.g., "my-company") + - **Auth Token**: Internal integration token from Sentry + - **Client Secret**: For webhook signature verification + + + + + + In your Sentry account: + 1. Create a new [internal integration](https://docs.sentry.io/product/integrations/integration-platform/) + 2. Set the webhook URL to `https://api.continue.dev/webhooks/sentry` + 3. Select "Read and Write" access for "Issue and Event" + 4. Select "issue" in the webhooks section and click Save Changes + 5. Copy the Auth Token and Client Secret + + + + + + Paste all three values into the integration form and click "Create Connection" + + + + + + + + **How to get these credentials:** + 1. Create a new **internal integration** in Sentry + 2. Set the webhook URL to `https://api.continue.dev/webhooks/sentry` + 3. Select "Read and Write" access for "Issue and Event" + 4. Select "issue" in the webhooks section and click Save Changes + 5. Find your organization slug in the Sentry URL (your-slug.sentry.io) + 6. Copy the Auth Token and Client Secret from the integration + + + +## Use Cases + +### Automatic Error Resolution + +Create agents that fix errors as they occur: + + + + **Task Example**: "Monitor new Sentry errors and create PRs with fixes for straightforward issues" + + **What the Agent Does**: + - Receives notifications when new errors occur + - Analyzes the stack trace and error context + - Identifies the root cause in your codebase + - Generates a fix and creates a pull request + - Links the PR back to the Sentry issue + + **Run in Mission Control**: Set up as an automation triggered by Sentry webhooks + + + +### Error Pattern Analysis + +Identify and resolve systemic issues: + + + + **Task Example**: "Analyze error patterns from the last 7 days and identify common root causes" + + **What the Agent Does**: + - Groups similar errors together + - Identifies patterns in stack traces and user actions + - Determines if errors are related to specific releases or features + - Creates comprehensive reports with recommendations + - Opens issues for systemic problems requiring architectural changes + + **Run in Mission Control**: Schedule to run weekly or after major releases + + + +### Priority Triage + +Automatically prioritize critical errors: + + + + **Task Example**: "Triage new Sentry issues by impact, assign severity levels, and notify the appropriate team" + + **What the Agent Does**: + - Evaluates error frequency and user impact + - Assigns priority levels (critical, high, medium, low) + - Tags errors by component and team + - Creates GitHub issues for high-priority errors + - Notifies relevant team members + + **Run in Mission Control**: Create as an automation triggered on new Sentry issues + + + +### Release Quality Monitoring + +Track error rates across deployments: + + + + **Task Example**: "Compare error rates before and after the latest release and flag any regressions" + + **What the Agent Does**: + - Compares error metrics between releases + - Identifies new errors introduced in the latest release + - Calculates error rate changes by percentage + - Generates release quality reports + - Creates rollback recommendations if error rates spike + + **Run in Mission Control**: Trigger after each deployment or on a schedule + + + +### Performance Issue Detection + +Monitor and resolve performance degradation: + + + + **Task Example**: "Identify performance regressions from Sentry performance monitoring and suggest optimizations" + + **What the Agent Does**: + - Analyzes transaction duration trends + - Identifies slow database queries or API calls + - Detects N+1 query problems + - Suggests code optimizations + - Creates PRs with performance improvements + + **Run in Mission Control**: Schedule daily or trigger on performance alerts + + + +### User Impact Analysis + +Understand how errors affect your users: + + + + **Task Example**: "Generate a report on which users are most affected by current errors and prioritize fixes accordingly" + + **What the Agent Does**: + - Identifies users experiencing multiple errors + - Analyzes error distribution across user segments + - Correlates errors with user churn or frustration signals + - Creates prioritized fix lists based on user impact + - Generates customer communication templates + + **Run in Mission Control**: Run weekly or before customer check-ins + + + +## Running Sentry Agents in Mission Control + +You can run Sentry-connected agents in two ways: + +### 1. Manual Tasks + +Trigger agents on-demand for error analysis: + +1. Go to [Mission Control Agents](https://hub.continue.dev/agents) +2. Select or create a Sentry-enabled agent +3. Click "Run Agent" and provide your task description +4. Monitor progress and review results in real-time + +**Example Tasks:** +- "Analyze the top 10 errors from the last 24 hours" +- "Create a PR to fix the authentication timeout error" +- "Generate a report on errors affecting mobile users" + +### 2. Automated Workflows + +Set up agents to run automatically: + +- **Webhook-triggered**: Execute when new Sentry errors occur +- **Scheduled**: Run daily or weekly error analysis +- **Threshold-based**: Trigger when error rates exceed limits + + + + Start with manual tasks to refine your prompts, then convert successful workflows to automations for continuous error monitoring. + + + +## Integration with GitHub + +Combine Sentry with GitHub integration for a complete workflow: + + + + + + Enable both Sentry and GitHub integrations in Mission Control + + + + + + Build an agent that: + - Receives Sentry error notifications + - Analyzes the error and finds the problematic code + - Creates a PR with a fix + - Adds the PR link to the Sentry issue + + + + + + Configure the agent to run automatically on new Sentry issues + + + + + +## Monitoring Agent Activity + +Track your agent's error resolution performance: + +1. **View in Mission Control**: See all agent runs and their outcomes +2. **Check Sentry**: Verify that issues are being resolved +3. **Review PRs**: Ensure quality of generated fixes +4. **Monitor Metrics**: Track resolution time and success rate + + +## Troubleshooting + + + + **Problem**: Agent isn't running when new errors occur + + **Solutions**: + - Verify webhook URL is correct in Sentry + - Check that "issue" is selected in webhook events + - Ensure Client Secret matches in both Sentry and Mission Control + - Review webhook delivery logs in Sentry + + + + + + **Problem**: Agent returns errors when trying to fetch issue details + + **Solutions**: + - Verify Auth Token has "Read and Write" access for "Issue and Event" + - Check that organization slug is correct + - Ensure token hasn't expired + - Confirm project permissions in Sentry + + + + + + **Problem**: Generated PRs don't reference the Sentry issue + + **Solutions**: + - Ensure both Sentry and GitHub integrations are connected + - Verify agent has permission to access both services + - Check that the agent prompt includes instructions to link issues + - Review agent logs for errors + + + +## Support & Resources + + + + + + Comprehensive guide to using Sentry with Continue agents + + + + + + Combine Sentry with GitHub for complete automation + + + + + + diff --git a/docs/hub/agents/slack-agent.mdx b/docs/mission-control/integrations/slack-agent.mdx similarity index 86% rename from docs/hub/agents/slack-agent.mdx rename to docs/mission-control/integrations/slack-agent.mdx index f515c23b8a1..1dbe2954077 100644 --- a/docs/hub/agents/slack-agent.mdx +++ b/docs/mission-control/integrations/slack-agent.mdx @@ -29,9 +29,7 @@ Mention @Continue in any channel with a task description, and it will: ## Setup -Continue's Slack Bot can be installed to a Slack workspace via the Hub, from: - -- [Personal Integrations Settings](https://hub.continue.dev/settings/integrations) +Continue's Slack Bot can be installed to a Slack workspace via Mission Control, from:[Integrations Settings](https://hub.continue.dev/integrations) - Org Integrations Settings - `https://hub.continue.dev/organizations/{your-org}/settings/integrations` @@ -143,27 +141,15 @@ To remove the Slack integration: - + Learn about Continue agents - - - Use Continue from the command line - - - - - - Best practices for background agents - - - - + - Automate code reviews + Add the GitHub Integration to create issues and PRs diff --git a/docs/mission-control/metrics.mdx b/docs/mission-control/metrics.mdx new file mode 100644 index 00000000000..dc2d6bb1e4a --- /dev/null +++ b/docs/mission-control/metrics.mdx @@ -0,0 +1,48 @@ +--- +title: "Metrics" +description: "Track agent performance, workflow activity, and PR outcomes." +--- + + +Metrics give you visibility into how your Agents and Workflows perform across your repositories. +Use this page to understand activity patterns, identify bottlenecks, and measure success over time. + + +## What Metrics Show + + + + + A day-by-day graph of total Agent runs across your repositories. + - See which Agents are running most often + - Spot spikes, trends, or recurring failures + - Monitor automated Workflows in production + + + + Per-Agent breakdown of: + - **Total runs** + - **PR creation rate** + - **PR status** (open, merged, closed, failed) + - **Success vs. intervention rate** + + + + Track which Workflows create the most tasks or PRs, and how often they complete successfully. + + + + +## Why Metrics Matter + + + + + Identify which Agents need better rules, tools, or prompts. + + + + See how much work your automated Workflows are completing across your repos. + + + \ No newline at end of file diff --git a/docs/hub/secrets/secret-resolution.mdx b/docs/mission-control/secrets/secret-resolution.mdx similarity index 100% rename from docs/hub/secrets/secret-resolution.mdx rename to docs/mission-control/secrets/secret-resolution.mdx diff --git a/docs/hub/secrets/secret-types.mdx b/docs/mission-control/secrets/secret-types.mdx similarity index 82% rename from docs/hub/secrets/secret-types.mdx rename to docs/mission-control/secrets/secret-types.mdx index d2b690faabe..e9d0b07c626 100644 --- a/docs/hub/secrets/secret-types.mdx +++ b/docs/mission-control/secrets/secret-types.mdx @@ -1,13 +1,13 @@ --- title: "Secret Types" -description: "The Continue Hub comes with secrets management built-in. Secrets are values such as API keys or endpoints that can be shared across configurations and within organizations." +description: "The Continue Mission Control comes with secrets management built-in. Secrets are values such as API keys or endpoints that can be shared across configurations and within organizations." --- ## User secrets User secrets are defined by the user for themselves. This means that user secrets are available only to the user that created them. User secrets are assumed to be safe for the user to know, so they will be sent to the IDE extensions alongside `config.yaml`. -This allows API requests to be made directly from the IDE extensions. You can use user secrets with [Solo](/hub/governance/pricing#solo), [Teams](/hub/governance/pricing#teams), and [Enterprise](/hub/governance/pricing#enterprise). User secrets can be managed [here](https://hub.continue.dev/settings/secrets) in the hub. +This allows API requests to be made directly from the IDE extensions. You can use user secrets with [Solo](/hub/governance/pricing#solo), [Teams](/hub/governance/pricing#teams), and [Enterprise](/hub/governance/pricing#enterprise). User secrets can be managed [here](https://hub.continue.dev/settings/secrets) in Mission Control. ## Org secrets diff --git a/docs/mission-control/sharing.mdx b/docs/mission-control/sharing.mdx new file mode 100644 index 00000000000..a367eb8e9fd --- /dev/null +++ b/docs/mission-control/sharing.mdx @@ -0,0 +1,68 @@ +--- +title: "Sharing" +description: "Connect with the Continue community to discover, share, and collaborate on AI development tools." +--- + + +You can share any Agent or Component (Models, Rules, Prompts, MCP Servers) by publishing it as Public or Organization-visible. +Sharing makes it easy for teammates—or the entire community—to reuse your best workflows. + + +## Where to Find Your Shareable Items + +Your personal and organization components live in your Profile. + +To access your profile (or your organization’s profile): + + + + + + + + + + + + + + + +Profiles look the same for personal users and organizations. The only difference is visibility options: personal profiles can create *Public* or *Private* items. Organizations can also create *Organization-only* items. + + +## Sharing Options + +Each Agent or Component can be published with one of three visibility levels: + + + + + Only you can see and use the item. + Great for prototypes or experiments. + + + + Visible to everyone in your organization. + Ideal for internal workflows, standardized agents, and shared tooling. + + + + Available to everyone in Continue Mission Control. + Perfect for templates, community contributions, and reusable examples. + + + + +## Community + + + Join thousands of developers using Continue and share your experiences. + + + Let us know what you think of Mission Control. + + + + + diff --git a/docs/mission-control/tasks.mdx b/docs/mission-control/tasks.mdx new file mode 100644 index 00000000000..19d4a124b17 --- /dev/null +++ b/docs/mission-control/tasks.mdx @@ -0,0 +1,137 @@ +--- +title: "Tasks" +description: "A Task is a unit of work shared between you and an agent. You trigger the task, the agent executes it, then you review or approve the results. Tasks can run **on demand**, **on triggers**, or **on schedules**." +--- + + + + **What is a Task?** + + A Task is a unit of work that combines: + - Your instructions + - An agent's capabilities (model, rules, tools, prompt) + - Your codebase (repository and branch) + + Tasks can be triggered manually, by events, or on a schedule. + + + +## Creating and Running a Task + + + + + + Select the **Agent** you want to use for this task. + + + + Don't have an Agent yet? Create one in **[Mission Control → Agents](https://hub.continue.dev/new?type=agent)** before setting up your first task. + + + + + + + + Pick the **repository** and **branch** where the Agent will work. + + + + + + + Add your user input — clear instructions for what you want the agent to accomplish. + + **Example prompts:** + + ```text + Refactor unused React components and clean up imports + ``` + + ```text + Add error handling to all API endpoints in the /api directory + ``` + + ```text + Update README with installation instructions for the new CLI tool + ``` + + + + + + Click the Submit button. + + The Agent will: + - Analyze your repository and branch + - Execute the task based on your input + - Generate changes based on your task request + - Create a detailed session log + + + + Task execution time varies based on complexity. You can monitor progress in your inbox. + + + + + + + + Each Task run creates a Session with complete traceability. + + + + + A high-level explanation of: + - What the Agent did + - Why decisions were made + - Key changes implemented + + + + + + The exact code changes: + - Files modified + - Lines added/removed + - Side-by-side comparison + + + + + + Full execution trace: + - Tool calls made + - Agent reasoning + - Any errors or warnings + + + + + + + + + Review the diff carefully before accepting changes. You can: + - Accept all changes + - Request modifications + - Reject and retry with an updated input + + + + + + + +## Next Steps + + + + + Automate tasks with event-based triggers + + + + diff --git a/docs/mission-control/workflows.mdx b/docs/mission-control/workflows.mdx new file mode 100644 index 00000000000..0d4ac035df4 --- /dev/null +++ b/docs/mission-control/workflows.mdx @@ -0,0 +1,156 @@ +--- +title: "Workflows" +description: "Workflows trigger agents on a schedule or when events occur." +--- + + + + + What is a Workflow? + + A Workflow automatically runs an Agent on a repository when: + - A schedule is reached (cron) + - An event occurs (webhook, e.g. GitHub PR) + + Use Workflows for recurring or event-driven tasks like: + - Daily vulnerability scans + - Weekly changelog generation + - Reacting to new pull requests or Sentry alerts + + + +--- + +## Creating a Workflow + + + + + + In Mission Control → Workflows, create a [new workflow](https://hub.continue.dev/workflows/new). + + + + Create a workflow from scratch by clicking Create Workflow. + You'll choose the repository, agent, trigger type, and schedule or webhook. + + + + Select any of the “Try these Workflows” cards such as: + - _Update agents.md_ + - _Draft Changelog Updates_ + - _Solve Snyk Vulnerabilities_ + + Templates preload the recommended agent and schedule so you can customize and run them quickly. + + + + + + + + + Give your Workflow a clear, descriptive name. + + Examples: + - `Morning status check` + - `Weekly changelog draft` + - `Daily Snyk vulnerability scan` + + + + + + Choose: + + - Repository – the codebase the Agent will run against + - Agent – the configured Agent (model, rules, tools, prompt) that should perform the work + + + Need a new Agent? Create one in [Mission Control → Agents](https://hub.continue.dev/new?type=agent), then return to this screen. + + + + + + + Pick how this Workflow should run: + + - Cron – run on a schedule (daily, weekly, hourly, custom) + - Webhook – run when an external system sends a request (e.g. GitHub PR event) + + + + + + + + + + For scheduled Workflows: + + 1. Select Cron as the trigger type + 2. Choose a schedule: + - Common presets (e.g. weekdays at 9 AM UTC) + - Hourly, Daily, Weekly, Monthly + - Or define a Custom expression + 3. (Optional) Add additional instructions for this Workflow run in the text area. + + Example use cases: + - Run a morning status check on your repo every weekday + - Refactor React components once per week + - Generate a weekly changelog from recent commits + + + + + + For event-based Workflows: + + 1. Select Webhook as the trigger type + 2. (Optional) Set a Secret Header (e.g. `X-Webhook-Secret`) + 3. (Optional) Set a Secret Value (token your external system must send) + + You’ll receive a webhook URL to call from: + - GitHub Actions + - GitHub webhooks + - CI/CD pipelines + - Any external system that can send HTTP requests + + Example use cases: + - Run an Agent whenever a pull request is opened + - Kick off a workflow when Snyk or Sentry detects an issue + + + + + + + + + + Click Create Cron Workflow or Create Webhook Workflow, depending on your trigger type. + + Your Workflow will now appear in the Workflows list and begin running based on its configured schedule or events. + + + + + +## Monitoring Workflow Runs + +Workflow runs show up just like Tasks: + +- Each execution creates a Session +- Workflows appear in your Inbox +- You can open the detail view to see the summary, diff, and logs. + + + + + + + Connect GitHub, Slack, and Sentry for richer triggers and actions. + + + \ No newline at end of file diff --git a/docs/reference.mdx b/docs/reference.mdx index 2933ea3ace8..e467a5a3109 100644 --- a/docs/reference.mdx +++ b/docs/reference.mdx @@ -219,7 +219,7 @@ Confiugration example: ```yaml title="config.yaml" rules: - - uses: sanity/sanity-opinionated # rules file stored on Continue Hub + - uses: sanity/sanity-opinionated # rules file stored on Continue Mission Control - uses: file://user/Desktop/rules.md # rules file stored on local computer ``` @@ -245,7 +245,7 @@ Configuration example: ```yaml title="config.yaml" prompts: - - uses: supabase/create-functions # prompts file stored on Continue Hub + - uses: supabase/create-functions # prompts file stored on Continue Mission Control - uses: file://user/Desktop/prompts.md # prompts file stored on local computer ``` diff --git a/package-lock.json b/package-lock.json index 88c4caf915f..095609e8f5f 100644 --- a/package-lock.json +++ b/package-lock.json @@ -22,7 +22,6 @@ "integrity": "sha512-dyybb3AcajC7uha6CvhdVRJqaKyn7w2YKqKyAN37NKYgZT36w+iRb0Dymmc5qEJ549c/S31cMMSFd75bteCpCw==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "eslint-visitor-keys": "^3.4.3" }, @@ -42,7 +41,6 @@ "integrity": "sha512-CCZCDJuduB9OUkFkY2IgppNZMi2lBQgD2qzwXkEia16cge2pijY/aXi96CJMquDMn3nJdlPV1A5KrJEXwfLNzQ==", "dev": true, "license": "MIT", - "peer": true, "engines": { "node": "^12.0.0 || ^14.0.0 || >=16.0.0" } @@ -53,7 +51,6 @@ "integrity": "sha512-269Z39MS6wVJtsoUl10L60WdkhJVdPG24Q4eZTH3nnF6lpvSShEK3wQjDX9JRWAUPvPh7COouPpU9IrqaZFvtQ==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "ajv": "^6.12.4", "debug": "^4.3.2", @@ -78,7 +75,6 @@ "integrity": "sha512-9T9UjW3r0UW5c1Q7GTwllptXwhvYmEzFhzMfZ9H7FQWt+uZePjZPjBP/W1ZEyZ1twGWom5/56TF4lPcqjnDHcg==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "balanced-match": "^1.0.0", "concat-map": "0.0.1" @@ -90,7 +86,6 @@ "integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==", "dev": true, "license": "ISC", - "peer": true, "dependencies": { "brace-expansion": "^1.1.7" }, @@ -104,7 +99,6 @@ "integrity": "sha512-d9zaMRSTIKDLhctzH12MtXvJKSSUhaHcjV+2Z+GK+EEY7XKpP5yR4x+N3TAcHTcu963nIr+TMcCb4DBCYX1z6Q==", "dev": true, "license": "MIT", - "peer": true, "engines": { "node": "^12.22.0 || ^14.17.0 || >=16.0.0" } @@ -116,7 +110,6 @@ "deprecated": "Use @eslint/config-array instead", "dev": true, "license": "Apache-2.0", - "peer": true, "dependencies": { "@humanwhocodes/object-schema": "^2.0.3", "debug": "^4.3.1", @@ -132,7 +125,6 @@ "integrity": "sha512-9T9UjW3r0UW5c1Q7GTwllptXwhvYmEzFhzMfZ9H7FQWt+uZePjZPjBP/W1ZEyZ1twGWom5/56TF4lPcqjnDHcg==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "balanced-match": "^1.0.0", "concat-map": "0.0.1" @@ -144,7 +136,6 @@ "integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==", "dev": true, "license": "ISC", - "peer": true, "dependencies": { "brace-expansion": "^1.1.7" }, @@ -158,7 +149,6 @@ "integrity": "sha512-bxveV4V8v5Yb4ncFTT3rPSgZBOpCkjfK0y4oVVVJwIuDVBRMDXrPyXRL988i5ap9m9bnyEEjWfm5WkBmtffLfA==", "dev": true, "license": "Apache-2.0", - "peer": true, "engines": { "node": ">=12.22" }, @@ -173,8 +163,7 @@ "integrity": "sha512-93zYdMES/c1D69yZiKDBj0V24vqNzB/koF26KPaagAfd3P/4gUlh3Dys5ogAK+Exi9QyzlD8x/08Zt7wIKcDcA==", "deprecated": "Use @eslint/object-schema instead", "dev": true, - "license": "BSD-3-Clause", - "peer": true + "license": "BSD-3-Clause" }, "node_modules/@nodelib/fs.scandir": { "version": "2.1.5", @@ -381,8 +370,7 @@ "resolved": "https://registry.npmjs.org/@ungap/structured-clone/-/structured-clone-1.3.0.tgz", "integrity": "sha512-WmoN8qaIAo7WTYWbAZuG8PYEhn5fkz7dZrqTBZ7dtt//lL2Gwms1IcnQ5yHqjDfX8Ft5j4YzDM23f87zBfDe9g==", "dev": true, - "license": "ISC", - "peer": true + "license": "ISC" }, "node_modules/acorn": { "version": "8.15.0", @@ -404,7 +392,6 @@ "integrity": "sha512-rq9s+JNhf0IChjtDXxllJ7g41oZk5SlXtp0LHwyA5cejwn7vKmKp4pPri6YEePv2PU65sAsegbXtIinmDFDXgQ==", "dev": true, "license": "MIT", - "peer": true, "peerDependencies": { "acorn": "^6.0.0 || ^7.0.0 || ^8.0.0" } @@ -415,7 +402,6 @@ "integrity": "sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "fast-deep-equal": "^3.1.1", "fast-json-stable-stringify": "^2.0.0", @@ -474,8 +460,7 @@ "resolved": "https://registry.npmjs.org/argparse/-/argparse-2.0.1.tgz", "integrity": "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==", "dev": true, - "license": "Python-2.0", - "peer": true + "license": "Python-2.0" }, "node_modules/array-buffer-byte-length": { "version": "1.0.2", @@ -710,7 +695,6 @@ "integrity": "sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==", "dev": true, "license": "MIT", - "peer": true, "engines": { "node": ">=6" } @@ -1009,8 +993,7 @@ "resolved": "https://registry.npmjs.org/deep-is/-/deep-is-0.1.4.tgz", "integrity": "sha512-oIPzksmTg4/MriiaYGO+okXDT7ztn/w3Eptv/+gSIdMdKsJo0u4CfYNFJPy+4SKMuCqGw2wxnA+URMg3t8a/bQ==", "dev": true, - "license": "MIT", - "peer": true + "license": "MIT" }, "node_modules/define-data-property": { "version": "1.1.4", @@ -1054,7 +1037,6 @@ "integrity": "sha512-yS+Q5i3hBf7GBkd4KG8a7eBNNWNGLTaEwwYWUijIYM7zrlYDM0BFXHjjPWlWZ1Rg7UaddZeIDmi9jF3HmqiQ2w==", "dev": true, "license": "Apache-2.0", - "peer": true, "dependencies": { "esutils": "^2.0.2" }, @@ -1262,7 +1244,6 @@ "integrity": "sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA==", "dev": true, "license": "MIT", - "peer": true, "engines": { "node": ">=10" }, @@ -1475,7 +1456,6 @@ "integrity": "sha512-dOt21O7lTMhDM+X9mB4GX+DZrZtCUJPL/wlcTqxyrx5IvO0IYtILdtrQGQp+8n5S0gwSVmOf9NQrjMOgfQZlIg==", "dev": true, "license": "BSD-2-Clause", - "peer": true, "dependencies": { "esrecurse": "^4.3.0", "estraverse": "^5.2.0" @@ -1493,7 +1473,6 @@ "integrity": "sha512-wpc+LXeiyiisxPlEkUzU6svyS1frIO3Mgxj1fdy7Pm8Ygzguax2N3Fa/D/ag1WqbOprdI+uY6wMUl8/a2G+iag==", "dev": true, "license": "Apache-2.0", - "peer": true, "engines": { "node": "^12.22.0 || ^14.17.0 || >=16.0.0" }, @@ -1507,7 +1486,6 @@ "integrity": "sha512-9T9UjW3r0UW5c1Q7GTwllptXwhvYmEzFhzMfZ9H7FQWt+uZePjZPjBP/W1ZEyZ1twGWom5/56TF4lPcqjnDHcg==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "balanced-match": "^1.0.0", "concat-map": "0.0.1" @@ -1519,7 +1497,6 @@ "integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==", "dev": true, "license": "ISC", - "peer": true, "dependencies": { "brace-expansion": "^1.1.7" }, @@ -1533,7 +1510,6 @@ "integrity": "sha512-oruZaFkjorTpF32kDSI5/75ViwGeZginGGy2NoOSg3Q9bnwlnmDm4HLnkl0RE3n+njDXR037aY1+x58Z/zFdwQ==", "dev": true, "license": "BSD-2-Clause", - "peer": true, "dependencies": { "acorn": "^8.9.0", "acorn-jsx": "^5.3.2", @@ -1552,7 +1528,6 @@ "integrity": "sha512-ca9pw9fomFcKPvFLXhBKUK90ZvGibiGOvRJNbjljY7s7uq/5YO4BOzcYtJqExdx99rF6aAcnRxHmcUHcz6sQsg==", "dev": true, "license": "BSD-3-Clause", - "peer": true, "dependencies": { "estraverse": "^5.1.0" }, @@ -1566,7 +1541,6 @@ "integrity": "sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag==", "dev": true, "license": "BSD-2-Clause", - "peer": true, "dependencies": { "estraverse": "^5.2.0" }, @@ -1580,7 +1554,6 @@ "integrity": "sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==", "dev": true, "license": "BSD-2-Clause", - "peer": true, "engines": { "node": ">=4.0" } @@ -1631,8 +1604,7 @@ "resolved": "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz", "integrity": "sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==", "dev": true, - "license": "MIT", - "peer": true + "license": "MIT" }, "node_modules/fast-glob": { "version": "3.3.3", @@ -1667,16 +1639,14 @@ "resolved": "https://registry.npmjs.org/fast-json-stable-stringify/-/fast-json-stable-stringify-2.1.0.tgz", "integrity": "sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==", "dev": true, - "license": "MIT", - "peer": true + "license": "MIT" }, "node_modules/fast-levenshtein": { "version": "2.0.6", "resolved": "https://registry.npmjs.org/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz", "integrity": "sha512-DCXu6Ifhqcks7TZKY3Hxp3y6qphY5SJZmrWMDrKcERSOXWQdMhU9Ig/PYrzyw/ul9jOIyh0N4M0tbC5hodg8dw==", "dev": true, - "license": "MIT", - "peer": true + "license": "MIT" }, "node_modules/fastq": { "version": "1.19.1", @@ -1694,7 +1664,6 @@ "integrity": "sha512-7Gps/XWymbLk2QLYK4NzpMOrYjMhdIxXuIvy2QBsLE6ljuodKvdkWs/cpyJJ3CVIVpH0Oi1Hvg1ovbMzLdFBBg==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "flat-cache": "^3.0.4" }, @@ -1721,7 +1690,6 @@ "integrity": "sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "locate-path": "^6.0.0", "path-exists": "^4.0.0" @@ -1739,7 +1707,6 @@ "integrity": "sha512-CYcENa+FtcUKLmhhqyctpclsq7QF38pKjZHsGNiSQF5r4FtoKDWabFDl3hzaEQMvT1LHEysw5twgLvpYYb4vbw==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "flatted": "^3.2.9", "keyv": "^4.5.3", @@ -1754,8 +1721,7 @@ "resolved": "https://registry.npmjs.org/flatted/-/flatted-3.3.3.tgz", "integrity": "sha512-GX+ysw4PBCz0PzosHDepZGANEuFCMLrnRTiEy9McGjmkCQYwRq4A/X786G/fjM/+OjsWSU1ZrY5qyARZmO/uwg==", "dev": true, - "license": "ISC", - "peer": true + "license": "ISC" }, "node_modules/for-each": { "version": "0.3.5", @@ -1778,8 +1744,7 @@ "resolved": "https://registry.npmjs.org/fs.realpath/-/fs.realpath-1.0.0.tgz", "integrity": "sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw==", "dev": true, - "license": "ISC", - "peer": true + "license": "ISC" }, "node_modules/function-bind": { "version": "1.1.2", @@ -1922,7 +1887,6 @@ "deprecated": "Glob versions prior to v9 are no longer supported", "dev": true, "license": "ISC", - "peer": true, "dependencies": { "fs.realpath": "^1.0.0", "inflight": "^1.0.4", @@ -1944,7 +1908,6 @@ "integrity": "sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==", "dev": true, "license": "ISC", - "peer": true, "dependencies": { "is-glob": "^4.0.3" }, @@ -1958,7 +1921,6 @@ "integrity": "sha512-9T9UjW3r0UW5c1Q7GTwllptXwhvYmEzFhzMfZ9H7FQWt+uZePjZPjBP/W1ZEyZ1twGWom5/56TF4lPcqjnDHcg==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "balanced-match": "^1.0.0", "concat-map": "0.0.1" @@ -1970,7 +1932,6 @@ "integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==", "dev": true, "license": "ISC", - "peer": true, "dependencies": { "brace-expansion": "^1.1.7" }, @@ -1984,7 +1945,6 @@ "integrity": "sha512-AhO5QUcj8llrbG09iWhPU2B204J1xnPeL8kQmVorSsy+Sjj1sk8gIyh6cUocGmH4L0UuhAJy+hJMRA4mgA4mFQ==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "type-fest": "^0.20.2" }, @@ -2030,8 +1990,7 @@ "resolved": "https://registry.npmjs.org/graphemer/-/graphemer-1.4.0.tgz", "integrity": "sha512-EtKwoO6kxCL9WO5xipiHTZlSzBm7WLT627TqC/uVRd0HKmq8NXyebnNYxDoBi7wt8eTWrUrKXCOVaFq9x1kgag==", "dev": true, - "license": "MIT", - "peer": true + "license": "MIT" }, "node_modules/has-bigints": { "version": "1.1.0", @@ -2159,7 +2118,6 @@ "integrity": "sha512-hsBTNUqQTDwkWtcdYI2i06Y/nUBEsNEDJKjWdigLvegy8kDuJAS8uRlpkkcQpyEXL0Z/pjDy5HBmMjRCJ2gq+g==", "dev": true, "license": "MIT", - "peer": true, "engines": { "node": ">= 4" } @@ -2170,7 +2128,6 @@ "integrity": "sha512-TR3KfrTZTYLPB6jUjfx6MF9WcWrHL9su5TObK4ZkYgBdWKPOFoSoQIdEuTuR82pmtxH2spWG9h6etwfr1pLBqQ==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "parent-module": "^1.0.0", "resolve-from": "^4.0.0" @@ -2188,7 +2145,6 @@ "integrity": "sha512-JmXMZ6wuvDmLiHEml9ykzqO6lwFbof0GG4IkcGaENdCRDDmMVnny7s5HsIgHCbaq0w2MyPhDqkhTUgS2LU2PHA==", "dev": true, "license": "MIT", - "peer": true, "engines": { "node": ">=0.8.19" } @@ -2200,7 +2156,6 @@ "deprecated": "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.", "dev": true, "license": "ISC", - "peer": true, "dependencies": { "once": "^1.3.0", "wrappy": "1" @@ -2211,8 +2166,7 @@ "resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.4.tgz", "integrity": "sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==", "dev": true, - "license": "ISC", - "peer": true + "license": "ISC" }, "node_modules/internal-slot": { "version": "1.1.0", @@ -2491,7 +2445,6 @@ "integrity": "sha512-Fd4gABb+ycGAmKou8eMftCupSir5lRxqf4aD/vd0cD2qc4HL07OjCeuHMr8Ro4CoMaeCKDB0/ECBOVWjTwUvPQ==", "dev": true, "license": "MIT", - "peer": true, "engines": { "node": ">=8" } @@ -2674,7 +2627,6 @@ "integrity": "sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "argparse": "^2.0.1" }, @@ -2687,24 +2639,21 @@ "resolved": "https://registry.npmjs.org/json-buffer/-/json-buffer-3.0.1.tgz", "integrity": "sha512-4bV5BfR2mqfQTJm+V5tPPdf+ZpuhiIvTuAB5g8kcrXOZpTT/QwwVRWBywX1ozr6lEuPdbHxwaJlm9G6mI2sfSQ==", "dev": true, - "license": "MIT", - "peer": true + "license": "MIT" }, "node_modules/json-schema-traverse": { "version": "0.4.1", "resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz", "integrity": "sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==", "dev": true, - "license": "MIT", - "peer": true + "license": "MIT" }, "node_modules/json-stable-stringify-without-jsonify": { "version": "1.0.1", "resolved": "https://registry.npmjs.org/json-stable-stringify-without-jsonify/-/json-stable-stringify-without-jsonify-1.0.1.tgz", "integrity": "sha512-Bdboy+l7tA3OGW6FjyFHWkP5LuByj1Tk33Ljyq0axyzdk9//JSi2u3fP1QSmd1KNwq6VOKYGlAu87CisVir6Pw==", "dev": true, - "license": "MIT", - "peer": true + "license": "MIT" }, "node_modules/json5": { "version": "1.0.2", @@ -2725,7 +2674,6 @@ "integrity": "sha512-oxVHkHR/EJf2CNXnWxRLW6mg7JyCCUcG0DtEGmL2ctUo1PNTin1PUil+r/+4r5MpVgC/fn1kjsx7mjSujKqIpw==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "json-buffer": "3.0.1" } @@ -2736,7 +2684,6 @@ "integrity": "sha512-+bT2uH4E5LGE7h/n3evcS/sQlJXCpIp6ym8OWJ5eV6+67Dsql/LaaT7qJBAt2rzfoa/5QBGBhxDix1dMt2kQKQ==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "prelude-ls": "^1.2.1", "type-check": "~0.4.0" @@ -2908,7 +2855,6 @@ "integrity": "sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "p-locate": "^5.0.0" }, @@ -2931,8 +2877,7 @@ "resolved": "https://registry.npmjs.org/lodash.merge/-/lodash.merge-4.6.2.tgz", "integrity": "sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==", "dev": true, - "license": "MIT", - "peer": true + "license": "MIT" }, "node_modules/log-update": { "version": "6.1.0", @@ -3175,8 +3120,7 @@ "resolved": "https://registry.npmjs.org/natural-compare/-/natural-compare-1.4.0.tgz", "integrity": "sha512-OWND8ei3VtNC9h7V60qff3SVobHr996CTwgxubgyQYEpg290h9J0buyECNNJexkFm5sOajh5G116RYA1c8ZMSw==", "dev": true, - "license": "MIT", - "peer": true + "license": "MIT" }, "node_modules/npm-run-path": { "version": "5.3.0", @@ -3310,7 +3254,6 @@ "integrity": "sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==", "dev": true, "license": "ISC", - "peer": true, "dependencies": { "wrappy": "1" } @@ -3337,7 +3280,6 @@ "integrity": "sha512-6IpQ7mKUxRcZNLIObR0hz7lxsapSSIYNZJwXPGeF0mTVqGKFIXj1DQcMoT22S3ROcLyY/rz0PWaWZ9ayWmad9g==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "deep-is": "^0.1.3", "fast-levenshtein": "^2.0.6", @@ -3374,7 +3316,6 @@ "integrity": "sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "yocto-queue": "^0.1.0" }, @@ -3391,7 +3332,6 @@ "integrity": "sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "p-limit": "^3.0.2" }, @@ -3408,7 +3348,6 @@ "integrity": "sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "callsites": "^3.0.0" }, @@ -3422,7 +3361,6 @@ "integrity": "sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==", "dev": true, "license": "MIT", - "peer": true, "engines": { "node": ">=8" } @@ -3433,7 +3371,6 @@ "integrity": "sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg==", "dev": true, "license": "MIT", - "peer": true, "engines": { "node": ">=0.10.0" } @@ -3497,7 +3434,6 @@ "integrity": "sha512-vkcDPrRZo1QZLbn5RLGPpg/WmIQ65qoWWhcGKf/b5eplkkarX0m9z8ppCat4mlOqUsWpyNuYgO3VRyrYHSzX5g==", "dev": true, "license": "MIT", - "peer": true, "engines": { "node": ">= 0.8.0" } @@ -3508,6 +3444,7 @@ "integrity": "sha512-QQtaxnoDJeAkDvDKWCLiwIXkTgRhwYDEQCghU9Z6q03iyek/rxRh/2lC3HB7P8sWT2xC/y5JDctPLBIGzHKbhw==", "dev": true, "license": "MIT", + "peer": true, "bin": { "prettier": "bin/prettier.cjs" }, @@ -3603,7 +3540,6 @@ "integrity": "sha512-vYt7UD1U9Wg6138shLtLOvdAu+8DsC/ilFtEVHcH+wydcSpNE20AfSOduf6MkRFahL5FY7X1oU7nKVZFtfq8Fg==", "dev": true, "license": "MIT", - "peer": true, "engines": { "node": ">=6" } @@ -3710,7 +3646,6 @@ "integrity": "sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==", "dev": true, "license": "MIT", - "peer": true, "engines": { "node": ">=4" } @@ -3773,7 +3708,6 @@ "deprecated": "Rimraf versions prior to v4 are no longer supported", "dev": true, "license": "ISC", - "peer": true, "dependencies": { "glob": "^7.1.3" }, @@ -4242,7 +4176,6 @@ "integrity": "sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig==", "dev": true, "license": "MIT", - "peer": true, "engines": { "node": ">=8" }, @@ -4284,8 +4217,7 @@ "resolved": "https://registry.npmjs.org/text-table/-/text-table-0.2.0.tgz", "integrity": "sha512-N+8UisAXDGk8PFXP4HAzVR9nbfmVJ3zYLAWiTIoqC5v5isinhr+r5uaO8+7r3BMfuNIufIsA7RdpVgacC2cSpw==", "dev": true, - "license": "MIT", - "peer": true + "license": "MIT" }, "node_modules/to-regex-range": { "version": "5.0.1", @@ -4348,7 +4280,6 @@ "integrity": "sha512-XleUoc9uwGXqjWwXaUTZAmzMcFZ5858QA2vvx1Ur5xIcixXIP+8LnFDgRplU30us6teqdlskFfu+ae4K79Ooew==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "prelude-ls": "^1.2.1" }, @@ -4362,7 +4293,6 @@ "integrity": "sha512-Ne+eE4r0/iWnpAxD852z3A+N0Bt5RN//NjJwRd2VFHEmrywxf5vsZlh4R6lixl6B+wz/8d+maTSAkN1FIkI3LQ==", "dev": true, "license": "(MIT OR CC0-1.0)", - "peer": true, "engines": { "node": ">=10" }, @@ -4454,6 +4384,7 @@ "integrity": "sha512-p1diW6TqL9L07nNxvRMM7hMMw4c5XOo/1ibL4aAIGmSAt9slTE1Xgw5KWuof2uTOvCg9BY7ZRi+GaF+7sfgPeQ==", "dev": true, "license": "Apache-2.0", + "peer": true, "bin": { "tsc": "bin/tsc", "tsserver": "bin/tsserver" @@ -4487,7 +4418,6 @@ "integrity": "sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==", "dev": true, "license": "BSD-2-Clause", - "peer": true, "dependencies": { "punycode": "^2.1.0" } @@ -4603,7 +4533,6 @@ "integrity": "sha512-BN22B5eaMMI9UMtjrGd5g5eCYPpCPDUy0FJXbYsaT5zYxjFOckS53SQDE3pWkVoWpHXVb3BrYcEN4Twa55B5cA==", "dev": true, "license": "MIT", - "peer": true, "engines": { "node": ">=0.10.0" } @@ -4631,8 +4560,7 @@ "resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.2.tgz", "integrity": "sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ==", "dev": true, - "license": "ISC", - "peer": true + "license": "ISC" }, "node_modules/y18n": { "version": "5.0.8", @@ -4692,7 +4620,6 @@ "integrity": "sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==", "dev": true, "license": "MIT", - "peer": true, "engines": { "node": ">=10" },