diff --git a/changelog.txt b/changelog.txt new file mode 100644 index 0000000000..6bd1c28d60 --- /dev/null +++ b/changelog.txt @@ -0,0 +1 @@ +test: add comprehensive tests for hub error re-throwing diff --git a/docs/docs.json b/docs/docs.json index c320a20a20..1d76546e67 100644 --- a/docs/docs.json +++ b/docs/docs.json @@ -40,7 +40,8 @@ "mission-control/integrations/slack-agent", "mission-control/integrations/posthog", "mission-control/integrations/atlassian", - "mission-control/integrations/netlify" + "mission-control/integrations/netlify", + "mission-control/integrations/supabase" ] }, "mission-control/metrics", diff --git a/docs/mission-control/integrations/atlassian.mdx b/docs/mission-control/integrations/atlassian.mdx index 46f6d09406..41b1b6e232 100644 --- a/docs/mission-control/integrations/atlassian.mdx +++ b/docs/mission-control/integrations/atlassian.mdx @@ -2,301 +2,76 @@ title: "Atlassian Integration" description: "Connect Jira, Confluence, and Compass to automate project management with Continue Agents" --- - -## Overview - -Connect Jira, Confluence, and Compass to Continue Mission Control to enable agents to manage issues, search tickets, summarize pages, and bulk-process tasks using natural language. When Atlassian is enabled, Continue can automatically translate technical code changes into business-friendly updates, keeping stakeholders informed. - - - - - Automatically update Jira tickets with business-friendly summaries on PR merge + + - Update Jira tickets automatically on PR merge + - Translate code changes into business-friendly summaries - Search issues and create tickets using natural language - Summarize Confluence pages and documentation - - Bulk-process tasks across multiple tickets - - Triage incoming issues automatically - - Generate documentation from code changes - - Track development progress with stakeholder-friendly language - + - Reduce manual project-management overhead for developers -## Setup - - - - - - Go to your [Atlassian Integration Settings](https://hub.continue.dev/integrations/atlassian). - - - - - - Click "Connect" to Atlassian. - - - - - In the Atlassian authorization screen: - 1. Log into your Atlassian account - 2. Review the requested permissions - 3. Click "Authorize" to complete the connection - - - - - - ## Workflows - -### Update Jira Tickets - -**Trigger**: On PR merge -**Description**: Connect Jira, Confluence, and Compass to your agents. Search issues, create tickets, summarize pages, and bulk-process tasks with natural language. - -When a pull request is merged, this workflow automatically: - -1. **Extracts Jira Ticket ID** - Finds the ticket reference from: - - PR title (e.g., `[PROJ-123] Add feature`) - - Branch name (e.g., `feature/PROJ-123-description`) - - PR description or comments - -2. **Analyzes Code Changes** - Reviews the merged PR to identify: - - What changed (files, features, components) - - Why it matters (business value, problem solved) - - Impact (user-facing changes, performance improvements) - - Risk level (Low/Medium/High based on scope) - -3. **Creates Business Summary** - Translates technical changes into clear, non-technical language: - - Focuses on **outcomes over implementation** - - Highlights **business value** and user benefits - - Uses **plain language** avoiding technical jargon - - Explains who benefits and how - -4. **Updates Jira Ticket** - Posts a formatted comment with: - - Business-friendly summary of what was accomplished - - Key changes in business terms - - Impact on users or stakeholders - - Technical metadata (files changed, merge details, PR link) - -5. **Comments on PR** - Adds a link back to the updated Jira ticket - - - - Technical code changes are often difficult for stakeholders to understand. This workflow bridges the gap between development and business by: - - Keeping product managers informed without technical details - - Providing business stakeholders with clear progress updates - - Reducing manual ticket updates for developers - - Creating a clear audit trail of work completed - - - - - - **Smart Translation**: The agent automatically converts technical terms into business language. For example, "Refactored authentication module" becomes "Users can now stay logged in longer without interruptions." - - - -## Use Cases - -You can also create your own Atlassian-connected agents in Mission Control. Here are some examples for these use cases: - - - - - **Task Example**: "Create Jira tickets for all TODO comments in the codebase with priority based on code location" - - **What the Agent Does**: - - Scans codebase for TODO and FIXME comments - - Creates Jira issues with relevant context - - Links issues to code files and line numbers - - Assigns priority based on file criticality - - **Run in Mission Control**: Schedule weekly or after major releases - - - - -Streamline sprint planning with intelligent automation: - - - - **Task Example**: "Analyze backlog items and create a proposed sprint plan based on team velocity and priorities" - - **What the Agent Does**: - - Reviews open Jira issues and their estimates - - Considers team capacity and historical velocity - - Groups related tickets together - - Creates a proposed sprint with balanced workload - - **Run in Mission Control**: Run before sprint planning meetings - - - - - - **Task Example**: "Update Confluence API documentation to match current OpenAPI spec" - - **What the Agent Does**: - - Parses API specifications from codebase - - Compares with existing Confluence documentation - - Updates or creates Confluence pages with changes - - Notifies team of significant API changes - - **Run in Mission Control**: Trigger on API spec changes or schedule weekly - - +--- - +## Official Workflow Templates - **Task Example**: "Generate release notes from closed Jira tickets since last release and publish to Confluence" - - **What the Agent Does**: - - Queries Jira for tickets closed since last release - - Categorizes changes (features, fixes, improvements) - - Generates formatted release notes - - Creates or updates Confluence release page - - **Run in Mission Control**: Trigger manually before releases - - - - - - **Task Example**: "Analyze current sprint progress and identify blocked or at-risk items" - - **What the Agent Does**: - - Reviews sprint board status - - Identifies tickets without recent updates - - Flags dependencies and blockers - - Generates summary report in Confluence - - **Run in Mission Control**: Schedule daily during active sprints - - - - -## Running Atlassian Agents in Mission Control -You can run Supabase-connected agents in two ways as [one-off tasks](../tasks) or automated [workflows](../workflows): +The following **official workflow template** is maintained by the Continue team and is available directly in the Mission Control Hub. This workflow is designed to work out of the box and represents the recommended way to automate Atlassian-based updates. + + + Automatically translate merged pull requests into clear, business-friendly Jira updates that explain what changed, why it matters, and who benefits. + + - - Start with manual tasks to refine your content queries, then automate repetitive content management and validation tasks. - +Official workflow templates may expand over time as new patterns are validated. You can view, enable, and configure this workflow in **[Mission Control → Integrations → Atlassian](https://hub.continue.dev/integrations/atlassian)**. -## Optional Workflow Enhancements - - - - -Automatically add Jira labels based on code changes: - -- `frontend-update` - UI/UX changes detected -- `backend-update` - API or database changes -- `bugfix` - Resolves bugs or issues -- `feature` - New functionality added -- `security` - Security improvements -- `performance` - Performance optimizations - - - -Tag relevant people in Jira based on components modified: - -- Payment processing changes → `@finance-team` -- User interface changes → `@product-manager` -- Security updates → `@security-lead` -- API modifications → `@api-architect` - - - -Accumulate business-friendly summaries for release documentation: - -- Store formatted summaries in `.release-notes/{version}/` -- Automatically compile summaries into Confluence release pages -- Generate customer-facing changelog from Jira updates -- Include impact metrics and user benefits - - - -Log metadata for reporting and analytics: - -- Time from ticket creation to PR merge -- Number of files changed per ticket -- Business impact category (high/medium/low) -- Stakeholder engagement (comments, mentions) -- Risk level distribution across releases - - - -## Troubleshooting - - - - **Problem**: Agent can't connect to Atlassian services - - **Solutions**: - - Verify API token hasn't expired - - Check that email matches the token's account - - Ensure domain includes `.atlassian.net` - - Regenerate token if necessary - - - - - - **Problem**: Agent can't create or update items - - **Solutions**: - - Verify your Atlassian account has appropriate permissions - - Check project-level permissions in Jira - - Ensure space permissions are correct in Confluence - - Contact your Atlassian admin if needed - - - - +## Advanced Use Cases - **Problem**: Agent reports Jira issues don't exist - - **Solutions**: - - Verify issue keys are correct (e.g., PROJECT-123) - - Check that you have access to the project - - Ensure issues aren't in a restricted project - - Verify your API token has read access + +These examples are not officially maintained by the Continue team, but illustrate what’s possible with custom workflows. +- Generate stakeholder-ready release notes from Jira activity +- Summarize sprint progress and risks in Confluence +- Automatically triage incoming Jira issues +- Create tickets from TODOs or code comments +- Maintain audit trails linking code changes to business outcomes - - - **Problem**: Documentation changes aren't reflected in Confluence - - **Solutions**: - - Check that you have edit permissions for the space - - Verify page IDs are correct - - Ensure Confluence Cloud API is accessible - - Review agent logs for specific error messages - - - - - - **Problem**: Agent hits Atlassian API rate limits - - **Solutions**: - - Reduce frequency of automated workflows - - Batch operations where possible - - Implement exponential backoff in agent logic - - Consider upgrading Atlassian plan for higher limits - - +--- +## Access & Permissions -## Resources +When connecting Atlassian, you’ll authorize Continue to access Jira, Confluence, and Compass data based on your account permissions. +- **Project and space access** + Agents can only access Jira projects and Confluence spaces you are permitted to view or edit. - +- **Permissions** + Approved permissions allow Continue to read and update Jira tickets, summarize Confluence pages, and create links back to related pull requests. + +--- - Comprehensive guide to project management automation with Atlassian and Continue +## Support & Resources + + + Practical examples for automating Jira and Confluence with Continue agents. + + Combine Atlassian and GitHub to keep code and tickets in sync. + + diff --git a/docs/mission-control/integrations/github.mdx b/docs/mission-control/integrations/github.mdx index 168b098d60..feb1d5cb06 100644 --- a/docs/mission-control/integrations/github.mdx +++ b/docs/mission-control/integrations/github.mdx @@ -1,13 +1,11 @@ --- title: "GitHub Integration" -description: "Connect to GitHub to allow Continue Agents to read and create PRs on your repositories" +description: "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." --- -## 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 @@ -18,173 +16,56 @@ Connect your GitHub account to Continue Mission Control to enable agents to inte -## 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 - - +## Official Workflow Templates -### Code Quality Monitoring +The following **official workflow templates** are maintained by the Continue team and are available directly in the Mission Control Hub. These workflows are designed to work out of the box and represent the recommended ways to automate GitHub-based tasks. -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 + + + Keeps your AGENTS.md file in sync with the agents and capabilities used in your repository. + -Trigger agents on-demand for specific tasks: + + Creates draft changelog entries based on recent merged pull requests. + -1. Go to [Mission Control Agents](https://hub.continue.dev/hub?type=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 + + Generates a high-level explanation of your repository’s structure and architecture. + -### 2. Automated Workflows + + Periodically identifies and refactors large or complex React components. + -Set up agents to run automatically: + + Makes incremental improvements to test coverage on a recurring schedule. + + -- **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 +Official workflow templates may expand over time as new patterns are validated. You can view, enable, and configure these workflows in **Mission Control → Integrations → GitHub**. + +## Advanced Use Cases + +You can create custom workflows using Continue agents to automate a variety of GitHub-related tasks. Here are some ideas to get you started: + - Automatically triage new issues with labels and suggested assignees + - Review pull requests for security or performance concerns + - Draft documentation updates based on code changes + - Detect deprecated APIs and open migration issues + - Summarize repository activity for weekly team updates + +--- +## Access & Permissions - +When connecting GitHub, you’ll be asked to configure repository access and approve permissions. - Start with manual tasks to test your agent's behavior, then convert successful workflows to automations once you're confident in the results. +- **Repository access** + Choose whether to grant access to all repositories or select specific ones. You can change this at any time in your GitHub settings. - +- **Permissions** + Review and approve the requested permissions. These allow Continue to read repository data and perform automated actions like opening pull requests on your behalf. +You can revisit or revoke access at any time from GitHub or the Mission Control Hub. +--- ## Support & Resources diff --git a/docs/mission-control/integrations/netlify.mdx b/docs/mission-control/integrations/netlify.mdx index 28effdf801..4a1c72af97 100644 --- a/docs/mission-control/integrations/netlify.mdx +++ b/docs/mission-control/integrations/netlify.mdx @@ -1,395 +1,113 @@ --- title: "Netlify Integration" -description: "Give your agents access to Netlify's API and CLI to manage deployments and optimize website performance" +description: "Connect **Netlify** to Mission Control so agents can automatically catch performance regressions by comparing preview and production deploys when code ships." --- -## Overview - -Connect Netlify to Continue Mission Control to give your agents access to Netlify's API and CLI. Create projects, deploy applications, configure domains, and manage infrastructure with natural language. When Netlify is enabled, Continue can analyze bundle sizes, audit performance, and prevent performance regressions. - - - - - Run Lighthouse audits on PR previews and production - - Compare bundle sizes and analyze performance regressions - - Automatically detect configuration issues (minification, caching, tree-shaking) - - Block PRs that introduce critical performance problems - - Generate detailed performance reports with actionable fixes - - Create projects and manage domains with natural language - - Configure build settings and environment variables - + + - Run Lighthouse audits on preview and production deploys + - Compare bundle sizes and detect performance regressions + - Surface configuration issues like disabled minification or caching + - Post clear performance summaries directly to pull requests -## Setup - - - - - - Go to your [Integrations Settings](https://hub.continue.dev/integrations). - - - - - - Click "Connect" next to Netlify. You'll need: - - - **Personal Access Token**: Generate from Netlify account settings - - - - - - To create a personal access token: - 1. Log into your [Netlify account](https://app.netlify.com) - 2. Go to **User Settings** → **Applications** → **Personal access tokens** - 3. Click "New access token" - 4. Give it a descriptive name (e.g., "Continue Mission Control") - 5. Copy the token immediately - - - - - - Paste your access token into the integration form and click "Create Connection" - - +## Official Workflow Templates - +The following **official workflow template** is maintained by the Continue team and is available directly in the Mission Control Hub. This workflow is designed to work out of the box and represents the recommended way to automate Netlify performance checks. - - - **Token Scope**: Personal access tokens have full access to your Netlify account. Create a token specifically for Continue to maintain security and easy revocation if needed. - - - -## Workflows - -### Optimize Website Performance - -**Trigger**: On PR merge -**Description**: Run Lighthouse audits on PR preview and production to compare performance - -When a pull request is merged, this performance-focused workflow automatically: - -1. **Retrieves Deployment Information** - Uses Netlify MCP to get: - - Production deploy URL and metadata - - Deploy preview URL for the PR branch - - Build artifacts and configuration - -2. **Analyzes Bundle Sizes** - Compares JavaScript and CSS bundles: - - Downloads and measures all asset files - - Calculates total bundle size for both deploys - - Identifies largest individual files - - Detects unminified or bloated assets - -3. **Reviews Build Configuration** - Examines: - - `vite.config.ts` or `webpack.config.js` for minification settings - - `netlify.toml` for cache headers and build commands - - `package.json` for redundant or oversized dependencies - -4. **Identifies Performance Issues** - Classifies problems by severity: - - 🔴 **Critical**: Minification disabled, bundle size >50% increase, no caching - - ⚠️ **Warning**: No code splitting, large chunks >500KB, 20-50% bundle increase - - ℹ️ **Info**: Suboptimal configurations, bundle size less than 20% increase - -5. **Generates Actionable Report** - Posts to PR with: - - Bundle size comparison table - - Root cause analysis with file references and line numbers - - Code fixes that can be copy-pasted - - Merge recommendation (Approved/Review Needed/Blocked) - - Expected improvements from each fix - - - - Performance regressions often slip through code review because: - - Bundle size increases aren't visible in diffs - - Configuration errors (disabled minification) go unnoticed - - Redundant dependencies accumulate over time - - This workflow catches these issues automatically before they reach production. - - - - - - **Smart Analysis**: The agent doesn't just report bundle sizes—it analyzes build configurations, identifies root causes, and provides specific code fixes with line numbers. - - + + + When a pull request is merged, runs Lighthouse audits comparing preview and production deploys to catch performance regressions before they reach users. + + ### Performance Issue Classification -The agent categorizes issues by severity: - - +The Netlify performance workflow classifies issues so you can quickly understand impact and urgency. + + +Issues that indicate severe regressions or broken production configuration. - **Issues that must be fixed before merging:** - - Minification disabled (`minify: false`) - - Tree-shaking disabled (`treeshake: false`) - - No caching headers (`Cache-Control: no-cache`) - - Production source maps enabled - - Bundle size increase >50% - - Redundant dependencies (lodash + underscore, moment + date-fns + dayjs) - - **Action**: Agent recommends blocking the merge +- Minification disabled +- Tree-shaking disabled +- Missing or unsafe cache headers +- Production source maps enabled +- Bundle size increase greater than 50% - - - **Issues that need attention:** - - No code splitting (single large bundle) - - Suboptimal cache headers (max-age too low) - - Large individual chunks (>500KB) - - Unoptimized images - - Bundle size increase 20-50% + +Issues that may negatively impact performance and should be reviewed before release. - **Action**: Agent recommends careful review before merging +- No code splitting (single large bundle) +- Large individual chunks (>500KB) +- Bundle size increase between 20–50% +- Suboptimal cache headers - + +Non-blocking improvements and suggestions. - **Non-blocking improvements:** - - Could use better code splitting - - Modern browser features could replace polyfills - - CSS not extracted/split - - Bundle size increase less than 20% - - **Action**: Agent approves merge but suggests optimizations +- Better code splitting opportunities +- Redundant dependencies +- Unoptimized images +- Bundle size increase under 20% - -## Use Cases - -### Infrastructure as Code - -Manage Netlify infrastructure with natural language: - - - - **Task Example**: "Create a new Netlify site for the marketing-site repo with custom domain marketing.company.com" - - **What the Agent Does**: - - Creates new Netlify project via API - - Connects to specified Git repository - - Configures build settings and commands - - Sets up custom domain and SSL - - Configures environment variables - - **Run in Mission Control**: Run manually when creating new projects - - - -### Build Configuration Optimization - -Automatically optimize build settings: - - - - **Task Example**: "Audit all Netlify sites for missing cache headers and suboptimal build configs" - - **What the Agent Does**: - - Reviews `netlify.toml` and build settings - - Checks cache header configurations - - Identifies missing optimizations - - Generates recommended configuration changes - - Can apply fixes automatically - - **Run in Mission Control**: Run monthly or after adding new sites - - - -### Performance Auditing - -Prevent performance regressions before deployment: - - - - **Task Example**: "Analyze bundle sizes and configurations, block PRs with critical performance issues" - - **What the Agent Does**: - - Compares preview and production bundle sizes - - Detects disabled minification or tree-shaking - - Identifies redundant dependencies (lodash + underscore, multiple date libraries) - - Checks cache configuration - - Posts detailed report with fixes to PR - - Recommends approval, review, or blocking merge - - **Run in Mission Control**: Triggered automatically on PR merge - - - -### Dependency Analysis - -Identify and fix problematic dependencies: - - - - **Task Example**: "Find redundant or oversized dependencies across all projects" - - **What the Agent Does**: - - Scans `package.json` files in all Netlify sites - - Identifies duplicate functionality (multiple date/utility libraries) - - Finds oversized packages (>100KB) - - Suggests lightweight alternatives - - Calculates potential bundle size savings - - **Run in Mission Control**: Run quarterly for dependency cleanup - - - -### Continuous Performance Monitoring - -Track performance trends over time: - - - - **Task Example**: "Generate a performance trend report for the last 30 deploys" - - **What the Agent Does**: - - Queries deploy history via Netlify MCP - - Tracks bundle size over time - - Identifies gradual performance degradation - - Highlights deploysthat introduced regressions - - Generates visualization of trends - - **Run in Mission Control**: Schedule weekly for ongoing monitoring - - - -### Domain and SSL Management - -Manage domains using natural language: - - - - **Task Example**: "Add www.example.com to my site and configure SSL" - - **What the Agent Does**: - - Configures custom domains via Netlify API - - Sets up SSL certificates automatically - - Configures DNS records and redirects - - Verifies domain setup and SSL status - - **Run in Mission Control**: Run manually when adding domains - - - -## Running Netlify Agents in Mission Control - -You can run Netlify-connected agents in two ways as [one-off tasks](../tasks) or automated [workflows](../workflows): - - - - - Start with manual tasks to refine your content queries, then automate repetitive content management and validation tasks. - - - - -### 2. Automated Workflows - -Set up agents to run automatically: - -- **PR-triggered**: Audit performance when pull requests are merged -- **Scheduled**: Run weekly bundle size audits across all sites -- **Manual**: Analyze specific deploys or troubleshoot performance issues + - - Start with manual performance audits on specific PRs to refine your thresholds, then enable automated workflows to catch all performance regressions. - +Official workflow templates may expand over time as new patterns are validated. You can view, enable, and configure this workflow in **[Mission Control → Integrations → Netlify](https://hub.continue.dev/integrations/netlify)**. +## Advanced Use Cases -## Troubleshooting - - - - **Problem**: Agent can't connect to Netlify API - - **Solutions**: - - Verify personal access token is correct - - Check that token hasn't been revoked - - Ensure token has necessary permissions - - Try regenerating the token - - - - - - **Problem**: Deploy preview is still building when agent tries to analyze - - **Solutions**: - - Verify you have deploy permissions for the site - - Check that the site exists and is accessible - - Ensure build hooks are configured if using webhooks - - Review Netlify API rate limits - - - - - - **Problem**: Agent can't find deploy preview for the branch - - **Solutions**: - - Verify branch name is correct - - Check that PR has triggered a Netlify build - - Ensure deploy previews are enabled in Netlify settings - - Confirm the repository is connected to Netlify + +These examples are not officially maintained by the Continue team, but illustrate what’s possible with custom workflows. +- Generate weekly performance trend reports across deploys +- Audit build configuration consistency across multiple sites +- Track bundle size growth over time +- Identify redundant or oversized dependencies +- Run performance checks on demand for specific deploys - - - **Problem**: Agent can't download or analyze bundles - - **Solutions**: - - Verify deploy URLs are accessible - - Check for authentication requirements on preview - - Ensure assets are being generated correctly - - Review build logs for errors - - - - - - **Problem**: Agent can't locate deploy previews +--- - **Solutions**: - - Verify branch name is correct - - Check that deploy previews are enabled for the site - - Ensure the commit has triggered a build - - Wait for build to complete before querying +## Access & Permissions - +When connecting Netlify, you’ll provide a **personal access token** so Continue can query deploys and site configuration. - +- **Access token** + Generate a personal access token from your Netlify user settings. Tokens grant account-level access, so we recommend creating one specifically for Continue. - **Problem**: Can't retrieve site performance metrics +- **Permissions** + Approved access allows Continue to read deploy metadata, fetch build artifacts, and run performance analyses tied to workflows. - **Solutions**: - - Verify Netlify Analytics is enabled for the site - - Check that your plan includes analytics access - - Ensure time range for queries is valid - - Review API documentation for metrics endpoints +You can revoke or rotate the token at any time from your Netlify account settings. - +--- ## Support & Resources - - - - Complete guide to continuous deployment automation with Netlify and Continue - + + Combine Netlify and GitHub to run performance checks on PR merges. - - - Combine Netlify with GitHub for end-to-end CI/CD automation - + + Advanced examples for working with Netlify deployments using Continue agents. - diff --git a/docs/mission-control/integrations/posthog.mdx b/docs/mission-control/integrations/posthog.mdx index 52f1037922..1ff6e9ff2b 100644 --- a/docs/mission-control/integrations/posthog.mdx +++ b/docs/mission-control/integrations/posthog.mdx @@ -1,238 +1,84 @@ --- title: "PostHog Integration" -description: "Leverage product analytics and feature flags with Continue Agents connected to PostHog" +description: "Connect PostHog to Mission Control so agents can keep analytics and tracking in sync with code changes, ensuring dashboards reflect what actually shipped." --- -## Overview - -Connect PostHog to Continue Mission Control to enable agents to analyze user behavior, manage feature flags, and optimize product experiences. When PostHog is enabled, Continue can analyze product metrics, automate feature rollouts, and create data-driven development tasks. - - - - - Analyze user behavior patterns and create optimization tasks - - Manage feature flags and gradual rollouts - - Generate insights from product analytics - - Automate A/B test analysis and reporting - - Monitor conversion funnels and user journeys - - Create PRs based on analytics insights - + + - Update analytics dashboards automatically after PRs merge + - Keep tracking and feature usage aligned with shipped code + - Analyze user behavior and product adoption trends + - Reduce manual analytics maintenance for engineering teams -## Setup - - - - - - Go to your [Integrations Settings](https://hub.continue.dev/integrations). - - - - - - Click "Connect" next to PostHog. You'll need the following credentials: - - - **Project API Key**: Your PostHog project API key - - **Host URL**: Your PostHog instance URL (e.g., `https://app.posthog.com` or your self-hosted URL) - - - - - - In your PostHog account: - 1. Navigate to Project Settings - 2. Find your Project API Key - 3. Copy your PostHog instance URL - 4. Paste both values into Mission Control - - - - - - Click "Create Connection" and verify that Continue can access your PostHog data - - - - - - - - **How to get these credentials:** - 1. Log into your PostHog account - 2. Go to **Settings** → **Project API Key** - 3. Copy your API key - 4. Note your instance URL (shown in the browser address bar) - - - -## Use Cases - -### Analytics-Driven Development - -Create agents that analyze user behavior and generate development tasks: - - - - **Task Example**: "Analyze the checkout flow conversion rate and identify areas for improvement" - - **What the Agent Does**: - - Retrieves funnel data from PostHog - - Identifies drop-off points in the user journey - - Analyzes user session recordings at problem areas - - Creates issues or PRs with optimization recommendations - - **Run in Mission Control**: Schedule weekly or trigger after significant traffic changes - - - -### Feature Flag Management - -Automate feature rollout based on metrics: - - - - **Task Example**: "Monitor new checkout feature performance and increase rollout percentage if metrics are positive" - - **What the Agent Does**: - - Tracks key metrics for the feature flag - - Compares performance against baseline - - Automatically adjusts rollout percentage - - Alerts team if anomalies are detected - - **Run in Mission Control**: Set up as continuous monitoring workflow - - - -### Performance Monitoring - -Track and respond to performance issues: - - - - **Task Example**: "Analyze page load times and create issues for pages slower than 3 seconds" - - **What the Agent Does**: - - Queries PostHog for performance metrics - - Identifies slow-loading pages - - Analyzes common characteristics of slow pages - - Creates prioritized issues with performance data - - **Run in Mission Control**: Schedule daily performance audits - - - -### A/B Test Analysis - -Automate experiment analysis and reporting: - - - - **Task Example**: "Analyze the results of the new homepage A/B test and determine statistical significance" - - **What the Agent Does**: - - Retrieves experiment data from PostHog - - Performs statistical analysis - - Generates comprehensive report with visualizations - - Creates recommendations for next steps - - **Run in Mission Control**: Trigger when experiment reaches sample size - - - -### User Feedback Loop - -Connect analytics insights to code improvements: - - - - **Task Example**: "Identify the top 5 most frustrating user experiences based on rage clicks and session replays" - - **What the Agent Does**: - - Analyzes user session data for frustration signals - - Reviews session replays of problematic interactions - - Identifies common UX issues - - Creates detailed bug reports with user context - - **Run in Mission Control**: Run weekly to catch emerging patterns - - +--- -## Running PostHog Agents in Mission Control +## Official Workflow Templates -You can run PostHog-connected agents in two ways as [one-off tasks](../tasks) or automated [workflows](../workflows): +The following **official workflow template** is maintained by the Continue team and is available directly in the Mission Control Hub. This workflow is designed to work out of the box and represents the recommended way to automate PostHog updates. + + + When a pull request is merged, this workflow updates PostHog dashboards and tracking to reflect newly shipped features or changes. + + - - Start with manual tasks to refine your content queries, then automate repetitive content management and validation tasks. - +Official workflow templates may expand over time as new analytics patterns are validated. You can view, enable, and configure this workflow in **[Mission Control → Integrations → PostHog](https://hub.continue.dev/integrations/posthog)**. +## Advanced Use Cases -## Troubleshooting - - - - **Problem**: Agent returns errors when trying to fetch analytics - - **Solutions**: - - Verify API key is correct and hasn't expired - - Check that the project API key has read permissions - - Ensure host URL includes protocol (https://) - - Confirm your PostHog plan includes API access - - - - - - **Problem**: Data retrieved doesn't match PostHog dashboard - - **Solutions**: - - Check that you're querying the correct time range - - Verify PostHog data is fully processed (may have slight delay) - - Ensure filters and breakdowns match your dashboard - - Review agent logs for query parameters + +These examples are not officially maintained by the Continue team, but illustrate what’s possible with custom workflows. +- Generate product insights from usage data and open follow-up issues +- Detect tracking gaps when new features ship +- Summarize weekly product metrics for stakeholders +- Correlate feature flags with user adoption and retention +- Trigger investigations when key metrics regress - +--- - **Problem**: Agent can't modify feature flags +## Access & Permissions - **Solutions**: - - Verify API key has write permissions - - Check that you're using a Personal API Key (not Project API Key) for modifications - - Ensure feature flag exists before attempting updates - - Review PostHog API documentation for flag management +When connecting PostHog, you’ll provide an API key that allows Continue to query analytics data and update dashboards. - +- **API key access** + You’ll need a PostHog API key with permission to read analytics data and modify dashboards. - +- **Project access** + Agents can only access the PostHog project associated with the API key you provide. - **Problem**: Can't connect to self-hosted PostHog instance +You can rotate or revoke the API key at any time from your PostHog settings. - **Solutions**: - - Verify host URL is accessible from Mission Control - - Check firewall rules allow Continue's IP addresses - - Ensure SSL certificate is valid if using HTTPS - - Test API access with curl or Postman first + + PostHog supports both cloud-hosted and self-hosted instances. + You’ll need your project’s API key and PostHog host URL available when connecting. + - +--- ## Support & Resources - - - - Complete guide to building product-led development workflows with PostHog and Continue - + + Build product-led development workflows using PostHog and Continue. - - - Combine PostHog with GitHub for data-driven development automation - + + Combine PostHog and GitHub to keep analytics aligned with code. - diff --git a/docs/mission-control/integrations/sanity.mdx b/docs/mission-control/integrations/sanity.mdx index 0a8a2ce83a..75433f22e3 100644 --- a/docs/mission-control/integrations/sanity.mdx +++ b/docs/mission-control/integrations/sanity.mdx @@ -1,349 +1,80 @@ --- title: "Sanity Integration" -description: "Automate content management and schema validation with Continue Agents connected to Sanity" +description: "Connect **Sanity** to Mission Control so agents can keep your content documentation in sync with schema and code changes — automatically generating updates when pull requests are opened." --- -## Overview - -Connect Sanity to Continue Mission Control to enable agents to manage content, validate schemas, execute GROQ queries, and automate your content workflows. When Sanity is enabled, Continue can explore document types, update content, handle migrations, and maintain content quality across your projects. - - - - - Automatically validate content and schemas on every PR - - Execute GROQ queries to analyze and update content - - Generate documentation from your content model - - Manage content migrations between environments - - Monitor content quality and consistency - - Automate content creation and updates - - - -## Setup - - - - - - Go to [the Sanity Integrations](https://hub.continue.dev/integrations/sanity). - - - - - - "Connect" to Sanity. The integration uses OAuth authentication through the Sanity MCP. - - - - - - Select the Sanity organization and project to connect - - - - - - After connecting, set up your first workflow. The integration supports: - - **On PR open**: Validate schemas and content when PRs are created - - **Manual tasks**: Run content operations on-demand - - **Scheduled jobs**: Periodic content audits and maintenance - - - - - - -## Workflows - -### Update Sanity schema docs - -**Trigger**: On PR open -**Description**: Skip the GROQ lookup. Agents manage your content through conversation. - -When a pull request modifies schema files (`schemas/**/*.{ts,js,tsx,jsx}`, `schemaTypes/**/*`, or `sanity.config.{ts,js}`), this workflow automatically: - -1. **Connects to Sanity** - Fetches the complete current schema using Sanity MCP -2. **Analyzes Changes** - Identifies new, modified, or removed document types -3. **Updates Documentation** - Generates comprehensive documentation including: - - Complete field descriptions and validation rules - - Relationship diagrams between document types - - GROQ query examples for each type - - Usage guidance for developers and content teams -4. **Commits to PR Branch** - Adds documentation directly to the existing PR branch -5. **Posts PR Comment** - Provides a detailed summary of documented changes - - - - For each document type, the agent generates: - - **Field Reference**: Every field with type, validation, and description - - **Relationships**: Visual diagram showing references between types - - **Query Examples**: Practical GROQ queries for common operations - - **Studio Behavior**: How fields appear and function in Sanity Studio - - **Validation Rules**: All constraints and requirements - - **Usage Notes**: Important gotchas and best practices - - - - - - **Documentation Location**: By default, docs are created at `docs/content-model.md`. The agent searches for existing documentation in several standard locations and preserves your structure. - - - -#### Example PR Comment - -After updating the documentation, the agent posts a comprehensive comment like this: - -```markdown -## 📝 Schema Documentation Updated - -I've automatically updated the content model documentation based on the schema changes in this PR. - -### 📋 Changes Documented - -**New Document Types** (2) -- ✨ `product` - E-commerce product listings -- ✨ `review` - Customer product reviews - -**Modified Document Types** (1) -- 📝 `article` - Added `featured` boolean field, updated `title` validation - -### 📄 Documentation Location - -📖 [View Updated Documentation](./docs/content-model.md) - -### 📊 Schema Overview - -- **Total Document Types**: 12 -- **Total Fields**: 87 -- **Types Modified in this PR**: 3 -- **New Fields Added**: 5 - -### 🔗 Key Relationships Changed - -- `product` now references `review` (one-to-many) -- `article.featured` added for homepage curation -``` - -## Use Cases - -### Content Validation - -Automatically validate content structure and quality: - - - - **Task Example**: "Check all blog posts for required fields and broken references" - - **What the Agent Does**: - - Scans documents for missing required fields - - Validates references between documents - - Checks for orphaned content - - Reports inconsistencies and suggests fixes - - **Run in Mission Control**: Schedule daily or trigger on content updates - - - -### Schema Management - -Manage and evolve your content schemas: - - - - **Task Example**: "Analyze the product schema and suggest optimizations for better performance" - - **What the Agent Does**: - - Reviews document type definitions - - Identifies unused or redundant fields - - Suggests schema improvements - - Validates relationships and data integrity - - **Run in Mission Control**: Run before major schema changes + + - Generate and update Sanity schema documentation from PR changes + - Explore schemas and content models with natural-language queries + - Run GROQ queries to validate content and discover issues + - Create and update documents with consistent structure -### Content Migration - -Automate content structure changes: - - - - **Task Example**: "Migrate all blog posts from the old schema to the new format" - - **What the Agent Does**: - - Reads content from old schema structure - - Transforms data to match new schema - - Validates migrated content - - Creates migration report with any issues - - **Run in Mission Control**: Run manually for controlled migrations - - - -### GROQ Query Execution - -Run complex queries to analyze content: - - - - **Task Example**: "Find all articles published in Q4 2023 with over 10,000 views" - - **What the Agent Does**: - - Executes GROQ queries against your dataset - - Analyzes results and identifies patterns - - Generates reports and visualizations - - Exports data for further analysis - - **Run in Mission Control**: Run on-demand for content insights - - - -### Schema Documentation - -Automatically maintain comprehensive schema documentation: - - - - **Task Example**: "Generate comprehensive documentation for all document types and their relationships" - - **What the Agent Does**: - - Fetches complete schema from Sanity - - Documents every field with types, validation, and descriptions - - Creates Mermaid diagrams showing document relationships - - Includes practical GROQ query examples - - Preserves manual documentation sections - - Updates statistics (total types, field counts) - - **Run in Mission Control**: Triggered automatically on PR open when schema files change - - **Documentation Structure**: - - Table of contents with all document types - - Detailed field tables for each type - - Relationship diagrams - - Query examples for common operations - - Validation rules and Studio configurations - - - -### Content Localization - -Manage multi-language content: - - - - **Task Example**: "Verify all product pages have complete Spanish and French translations" - - **What the Agent Does**: - - Identifies missing translations - - Validates localized field structure - - Reports incomplete content - - Suggests content for translation - - **Run in Mission Control**: Schedule weekly translation audits - - +--- -## Running Sanity Agents in Mission Control +## Official Workflow Templates -You can run Sanity-connected agents in two ways as [one-off tasks](../tasks) or automated [workflows](../workflows): +The following **official workflow template** is maintained by the Continue team and is available directly in the Mission Control Hub. This workflow is designed to work out of the box and represents the recommended way to automate Sanity documentation updates. + + + When a pull request is opened, automatically update your Sanity content documentation to stay in sync with schema and code changes. + + - - Start with manual tasks to refine your content queries, then automate repetitive content management and validation tasks. - +Official workflow templates may expand over time as new patterns are validated. You can view, enable, and configure this workflow in **[Mission Control → Integrations → Sanity](https://hub.continue.dev/integrations/sanity)**. +--- -## Troubleshooting - - - - **Problem**: Agent shows authentication errors - - **Solutions**: - - Re-authenticate through the integrations page (OAuth expires after 7 days) - - For CI/CD workflows, use environment variables instead - - Check that project permissions haven't changed - - Verify the Sanity project still exists - - - - - - **Problem**: Agent can't locate schema definitions - - **Solutions**: - - Verify schema files are in the correct location - - Check that the project ID is correct - - Ensure you're connected to the right dataset - - Confirm schema files are properly exported - - - - - - **Problem**: Queries fail or return unexpected results +## Advanced Use Cases - **Solutions**: - - Validate GROQ syntax in Sanity Vision - - Check that referenced fields exist - - Verify document types are spelled correctly - - Review query complexity and optimize if needed + +These examples are not officially maintained by the Continue team, but illustrate what’s possible with custom workflows. +- Validate schema changes against content standards before merging +- Generate migration suggestions when schema changes are detected +- Audit content for missing fields, broken references, or invalid values +- Generate content-model summaries for designers and stakeholders +- Create tickets or PR comments when content risks are detected - - - **Problem**: Agent reports content doesn't match schema - - **Solutions**: - - Check for recent schema changes - - Verify required fields are present - - Review field type mismatches - - Run migration to update content structure +--- - +## Access & Permissions - +When connecting Sanity, you’ll authorize Continue to access your workspace and interact with content based on your project permissions. - **Problem**: Content migration fails or produces errors +- **Workspace access** + Agents can only access Sanity projects and datasets you are permitted to view. - **Solutions**: - - Test migration on a small subset first - - Validate both old and new schemas - - Check for data type conflicts - - Review migration logs for specific errors - - Use transactions for atomic updates +- **Permissions** + Approved permissions allow Continue to read schemas, run GROQ queries, and create or update documents when workflows require it. - +--- ## Support & Resources - - - - Complete guide to content management automation with Sanity and Continue - - - - - - Combine Sanity with GitHub for automated content workflows - - - - - - Official Sanity documentation and guides - + + Practical examples for working with Sanity schemas and content using Continue agents. - - - Learn GROQ query language for content queries - + + Combine Sanity and GitHub to keep schema docs aligned with code changes. - - \ No newline at end of file + diff --git a/docs/mission-control/integrations/sentry.mdx b/docs/mission-control/integrations/sentry.mdx index 72532310a9..46b7cb4ca3 100644 --- a/docs/mission-control/integrations/sentry.mdx +++ b/docs/mission-control/integrations/sentry.mdx @@ -1,138 +1,87 @@ --- title: "Sentry Integration" -description: "Automatically triage and resolve errors with Continue Agents connected to Sentry" +description: "Connect Sentry to Mission Control so agents can automatically respond to production errors, analyzing issues as they occur and proposing fixes before they escalate." --- -## 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 + + - Analyze production errors as they occur + - Investigate stack traces and recent code changes + - Generate pull requests to resolve issues + - Create contextual GitHub issues - Monitor error trends across releases - -## Setup - - - - - - Go to [Sentry Integration](https://hub.continue.dev/integrations/sentry). - - - - - Click "Connect". 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 - - **API Key**: For MCP support - - - - - - 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 - +## Official Workflow Templates - +The following **official workflow template** is maintained by the Continue team and is available directly in the Mission Control Hub. This workflow is designed to work out of the box and represents the recommended way to automate Sentry-based remediation. - 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 - - - -## Running Sentry Agents in Mission Control - -You can run Sentry-connected agents in two ways as [one-off tasks](../tasks) or automated [workflows](../workflows). + + + Automatically analyze and fix production errors when Sentry detects new issues. + + - - Start with manual tasks to refine your content queries, then automate repetitive content management and validation tasks. - +Official workflow templates may expand over time as new patterns are validated. You can view, enable, and configure this workflow in **Mission Control → Integrations → Sentry**. +### Advanced Use Cases -## 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 + +These examples are not officially maintained by the Continue team, but illustrate what’s possible with custom workflows. +- Trigger investigations only for high-impact or high-frequency errors +- Route specific error types to specialized agents +- Correlate Sentry issues with recent deploys or feature flags +- Generate weekly error trend summaries for engineering teams +- Combine Sentry signals with GitHub or analytics data +--- +## Access & Permissions - - - **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 +When connecting Sentry, you’ll authorize Continue to receive error events and access issue data. - +- **Project and issue access** + Agents can access Sentry projects and issues you have permission to view within your organization. - +- **Permissions** + Approved permissions allow Continue to analyze error events, read issue details, and create pull requests or GitHub issues on your behalf. - **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 +You can update or revoke access at any time from Sentry or the Mission Control Hub. - + + Connecting Sentry requires creating an **[internal integration](https://sentry.io/settings/developer-settings/new-internal/)** in your Sentry organization. + + You’ll be asked for your organization slug and credentials that allow Continue to receive issue and event data via webhooks and API access. + + Full credential setup is handled in the Mission Control Hub. + +--- ## Support & Resources - - - - Comprehensive guide to using Sentry with Continue agents - + + Practical examples for working with Sentry data using Continue agents. - - - Combine Sentry with GitHub for complete automation - + + Combine Sentry and GitHub to automate error remediation. - - - diff --git a/docs/mission-control/integrations/slack-agent.mdx b/docs/mission-control/integrations/slack-agent.mdx index b386164e6b..98770184bf 100644 --- a/docs/mission-control/integrations/slack-agent.mdx +++ b/docs/mission-control/integrations/slack-agent.mdx @@ -9,16 +9,7 @@ description: "Kick off background Agents from Slack by mentioning @Continue" -## Overview - -Mention @Continue in any channel with a task description, and it will: - -- Create a new development agent -- Clone and work on your Repository -- Generate code changes and create pull requests -- Keep you updated on progress - - + - Quick bug fixes and feature implementations - Code reviews and refactoring @@ -27,36 +18,6 @@ Mention @Continue in any channel with a task description, and it will: -## Setup - - - - Continue's Slack app is in Beta development. During installation, you will see a warning that it is not yet approved/official. - - - - - - - - Click "Connect" next to GitHub in the Integrations settings, and grant access to the repositories you want Continue to work with. - - - - - - Click the "Connect" button next in [the Slack Integration ](https://hub.continue.dev/integrations/slack)and authorize the app in your workspace. - - - - - - Use the repository selector within the Slack tile to select a default repository for Continue Agents to work in. - - - - - ## Usage To kick off an agent, mention `@Continue` with a short task description. @@ -112,7 +73,7 @@ Continue will forward your message to the existing agent session instead of crea ## Monitoring Agent Progress -Click the agent link in Slack to view the agent's progress in [Mission Control](https://hub.continue.dev/hub?type=agents). +Click the agent link in Slack to view the agent's progress in [Mission Control](https://hub.continue.dev). You can also click the Slack icon in the agents page to return to the Slack message. @@ -140,11 +101,11 @@ To remove the Slack integration: - Learn about Continue agents + Learn about Continue agents. - + Add the GitHub Integration to create issues and PRs diff --git a/docs/mission-control/integrations/snyk.mdx b/docs/mission-control/integrations/snyk.mdx index 2cd981d536..023016d0d4 100644 --- a/docs/mission-control/integrations/snyk.mdx +++ b/docs/mission-control/integrations/snyk.mdx @@ -1,130 +1,75 @@ --- title: "Snyk Integration" -description: "Automatically detect and fix vulnerabilities with Continue Agents connected to Snyk" +description: "Connect Snyk to Continue Mission Control to automatically detect and fix vulnerabilities with Continue Agents" --- -## Overview - -Connect Snyk to Continue Mission Control to enable agents to automatically detect, analyze, and resolve security vulnerabilities. When Snyk is enabled, Continue can generate PRs to fix vulnerabilities, analyze security patterns, and maintain application security posture. - - - - - Automatically generate PRs to fix security vulnerabilities - - Analyze dependency risks and suggest updates + + - Detect and analyze security vulnerabilities + - Generate pull requests to remediate issues + - Analyze dependency and supply chain risks - Monitor security posture across projects - - Create detailed vulnerability reports with remediation steps - - Track vulnerability trends and compliance status - + - Create reports and summaries for security trends -## Setup - - - - - - Go to the [Snyk Integration](https://hub.continue.dev/integrations/snyk). - - - - - - Click "Connect" next to Snyk integration. - - - - - - Click the "Connect with Snyk" button to authorize Continue Mission Control: - - - You'll be redirected to Snyk's OAuth authorization page - - Review and approve the requested permissions - - You'll be automatically redirected back to the [Snyk inbox view](https://hub.continue.dev/inbox?view=snyk) - - - - - - Once redirected back, you'll see: - - A confirmation that Snyk is connected - - Your Snyk projects available for monitoring - - Any active vulnerability alerts - - - - - - - - **OAuth Authorization**: No manual token configuration needed! Simply click the authorization button and Continue will securely handle the authentication flow with Snyk. - - - +## Official Workflow Templates -## Troubleshooting +The following **official workflow template** is maintained by the Continue team and is available directly in the Mission Control Hub. This workflow is designed to work out of the box and represents the recommended way to automate Snyk-based remediation. - - - **Problem**: Can't complete the Snyk authorization flow - - **Solutions**: - - Ensure you have appropriate permissions in your Snyk organization - - Check if your organization allows OAuth integrations - - Try logging out and back into Snyk before authorizing - - Clear browser cookies and try again - - - - - - **Problem**: Snyk projects aren't visible after connection - - **Solutions**: - - Verify you have access to projects in Snyk - - Check that projects are properly imported in Snyk - - Refresh the integration connection - - Ensure the OAuth scope includes project access - - + + + Automatically remediate high and critical security vulnerabilities detected by Snyk. + + - + +Official workflow templates may expand over time as new security patterns are validated. You can view, enable, and configure these workflows in **[Mission Control → Integrations → Snyk](https://hub.continue.dev/integrations/snyk)**. + - **Problem**: Agent returns errors when trying to fetch Snyk data +### Advanced Use Cases - **Solutions**: - - Verify the OAuth connection is still valid - - Re-authorize if the token has expired - - Check that the agent has the necessary Snyk context provider - - Review agent logs for specific error messages + +These examples are not officially maintained by the Continue team, but illustrate what’s possible with custom workflows. +- Prioritize vulnerabilities based on exploitability or business impact +- Correlate Snyk findings with recent code changes +- Generate security summaries for compliance or audit reviews +- Trigger remediation only for production-critical projects +- Combine Snyk findings with GitHub or CI signals +--- +## Access & Permissions - +When connecting Snyk, you’ll authorize Continue to access vulnerability and project data via OAuth. - **Problem**: Agent isn't running when new vulnerabilities are found +- **Project access** + Agents can only access Snyk projects you are permitted to view within your organization. - **Solutions**: - - Verify webhook configuration in Snyk integration settings - - Check that webhook URL points to Continue Mission Control - - Ensure webhook events include vulnerability detection - - Review webhook delivery logs in Snyk +- **Permissions** + Approved permissions allow Continue to read vulnerability findings and create remediation pull requests on your behalf. - +You can revoke or reauthorize access at any time from Snyk or the Mission Control Hub. +--- ## Support & Resources - - - - Complete guide with security scanning recipes, CI/CD integration, and automated remediation workflows - + + Security automation recipes using Snyk and Continue agents. - - - Combine Snyk with GitHub for complete security automation - + + Combine Snyk and GitHub to automate vulnerability remediation. - diff --git a/docs/mission-control/integrations/supabase.mdx b/docs/mission-control/integrations/supabase.mdx index c29d35b6f6..d6313c70c8 100644 --- a/docs/mission-control/integrations/supabase.mdx +++ b/docs/mission-control/integrations/supabase.mdx @@ -1,526 +1,136 @@ --- title: "Supabase Integration" -description: "Monitor database security, generate migrations, and optimize queries with Continue Agents connected to Supabase" +description: "Connect **Supabase** to Mission Control so agents can automatically review **Row Level Security (RLS)** when pull requests touch database-related code." --- -## Overview - -Connect Supabase to Continue Mission Control to enable AI-powered database workflows. When Supabase is enabled, Continue can audit Row Level Security (RLS) policies, generate secure migrations, optimize queries, and maintain database security automatically. - - - - - Automatically audit RLS policies on every PR - - Generate secure migrations for missing security policies - - Identify and fix critical security gaps - - Optimize database queries and schemas - - Monitor database performance and security - - Validate schema changes before deployment - - - -## Setup - - - - - - Go to the [Supabase Integration](https://hub.continue.dev/integrations/supabase). - - - - - - Click "Connect" to Supabase. - - - - - - You'll be redirected to Supabase to authorize Continue: - 1. Select the Supabase organization and project to connect - 2. Review the requested permissions - 3. Click "Authorize" to complete the connection - - - - - - After connecting, set up your first workflow. The integration supports: - - **On PR open**: Audit RLS policies when PRs are created - - **Manual tasks**: Run database operations on-demand - - **Scheduled jobs**: Periodic security audits and performance checks - - - - - -## Workflows - -### Supabase security review - -**Trigger**: On PR open -**Description**: Connect your Supabase workspace to agents that can explore schemas, run queries, create and update documents, and handle migrations using natural language - -When a pull request is opened, this security-focused workflow automatically: - -1. **Analyzes PR Changes** - Identifies affected tables from: - - Migration files (`supabase/migrations/*.sql`) - - SDK/library usage (`.from('table_name')` calls) - - Schema references in type definitions - -2. **Audits RLS Policies** - Uses Supabase MCP to inspect: - - Whether RLS is enabled on affected tables - - Existing policy configurations - - Potential security gaps - -3. **Classifies Security Risks** - Prioritizes findings by severity: - - 🔴 **Critical**: No RLS on tables with sensitive data - - 🟠 **High**: Overly permissive policies (e.g., `USING (true)`) - - 🟡 **Medium**: Missing standard access patterns - - 🟢 **Low**: Policy optimization opportunities - -4. **Generates SQL Migrations** - Creates fixes for Critical/High/Medium issues: - - Enables RLS on unprotected tables - - Adds missing user-scoped policies - - Implements proper access controls - - Includes rollback commands - -5. **Commits Fixes to PR Branch** - Automatically pushes security fixes -6. **Posts Comprehensive Comment** - Explains all findings and changes - - - - Row Level Security (RLS) is Supabase's primary security mechanism. Without proper RLS policies: - - Users can access other users' private data - - Unauthorized modifications can occur - - Sensitive information may be exposed - - This workflow automatically catches these issues before they reach production. - - - - - - **Smart Scoping**: The agent only audits tables directly referenced in your PR changes, not your entire database. This keeps audits focused and efficient. - - - -#### Example PR Comment - -After auditing RLS policies, the agent posts a comprehensive comment like this: - -```markdown -## 🔒 Supabase RLS Policy Audit - -### Scope -This audit covers **3 tables** referenced in this PR: -- user_profiles (detected in: migration file) -- comments (detected in: SDK usage in src/api/comments.ts) -- posts (detected in: migration file) - -### Summary -- ✅ 1 table with proper RLS -- ⚠️ 2 tables requiring attention -- 🔴 1 critical security gap found - -### Findings - -| Table | Risk Level | Issue | Status | -|-------|------------|-------|--------| -| `user_profiles` | 🔴 Critical | No RLS enabled | ✅ Fixed in commit abc123 | -| `comments` | 🟡 Medium | Missing delete policy | ✅ Fixed in commit abc123 | -| `posts` | 🟢 Low | Policy optimization possible | 💡 Recommendation | - -### Changes Made - -- Enabled RLS on `user_profiles` -- Added policies: `user_profiles_select_own`, `user_profiles_update_own`, `comments_delete_own` -- See full migration: `supabase/migrations/20241118120000_rls_security_fixes.sql` - -### Recommendations (Low Priority) - -- **posts table**: Consider renaming policy `posts_policy_1` to `posts_select_owner` for clarity - -### Policy Patterns Used - -**User-scoped access** (users access only their own data): -\```sql -USING (auth.uid() = user_id) -WITH CHECK (auth.uid() = user_id) -\``` - -### Next Steps - -- ✅ Review the migration file and committed changes -- ✅ Test the policies in your development environment -- ✅ Merge this PR once you've verified the security improvements -``` - -### Security Risk Levels Explained - - - - **What it means**: Tables with no RLS that contain sensitive data - - **Examples**: - - User profiles, emails, or authentication data - - Financial information or payment details - - Private messages or personal content - - New tables created without RLS - - **What the agent does**: Automatically enables RLS and adds basic policies - - - - - - **What it means**: Overly permissive policies that could allow unauthorized access - - **Examples**: - - Policies using `USING (true)` without justification - - Write access without proper validation - - Admin policies that don't verify admin status - - Missing `WITH CHECK` clauses - - **What the agent does**: Generates restrictive policies with proper checks - - - - - - **What it means**: Partial RLS coverage or missing standard patterns - - **Examples**: - - SELECT policy exists but no UPDATE/DELETE - - No user-scoped policies for personal data - - Missing public read policies where appropriate - - Incomplete CRUD policy coverage - - **What the agent does**: Adds missing policies following standard patterns - - - - - - **What it means**: Policies work but could be improved - - **Examples**: - - Poor policy naming conventions - - Inefficient policy logic - - Missing documentation - - Duplicate or redundant policies - - **What the agent does**: Suggests improvements in PR comment (no auto-fix) - - - -## Use Cases - -### Automated Security Audits - -Catch security issues before they reach production: - - - - **Task Example**: Automatically audit RLS on every PR that touches database schema or queries - - **What the Agent Does**: - - Scans PR for database-related changes - - Identifies all affected tables - - Checks RLS status and policies - - Generates fixes for security gaps - - Commits migrations to the PR branch - - **Run in Mission Control**: Triggered automatically on PR open - + + - Audit RLS policies for tables referenced in PR changes + - Generate SQL migrations to remediate missing or unsafe policies + - Commit fixes for **Critical / High / Medium** issues to the PR branch + - Post (or update) a single PR comment with scope, findings, and changes -### Database Migration Generation - -Create secure migrations automatically: - - - **Task Example**: "Generate a migration to add RLS policies for the new messages table" +## Official Workflow Templates - **What the Agent Does**: - - Analyzes table structure and purpose - - Determines appropriate access patterns - - Generates SQL with RLS policies - - Includes proper naming and comments - - Adds rollback commands +The following **official workflow template** is maintained by the Continue team and is available directly in the Mission Control Hub. This workflow is designed to work out of the box and represents the recommended way to automate Supabase security reviews. - **Run in Mission Control**: Run manually or on schema changes - - - -### Query Optimization - -Improve database performance: - - - - **Task Example**: "Analyze slow queries and suggest optimizations" - - **What the Agent Does**: - - Identifies queries in your codebase - - Checks for missing indexes - - Suggests query rewrites - - Recommends schema changes - - Estimates performance impact - - **Run in Mission Control**: Schedule weekly performance reviews - - - -### Schema Validation - -Ensure schema changes follow best practices: - - - - **Task Example**: "Validate that all new tables follow our schema standards" - - **What the Agent Does**: - - Checks naming conventions - - Validates data types and constraints - - Ensures proper indexes exist - - Verifies RLS is enabled - - Reviews foreign key relationships - - **Run in Mission Control**: Triggered on migration file changes - - - -### Access Pattern Analysis - -Understand how your database is used: - - - - **Task Example**: "Analyze SDK usage patterns and suggest RLS policies" + + + When a pull request is opened, automatically audits RLS for tables referenced in that PR, commits fixes for Critical/High/Medium issues, and posts (or updates) a single PR comment with results. + + - **What the Agent Does**: - - Scans codebase for Supabase client calls - - Identifies data access patterns - - Detects security anti-patterns - - Recommends appropriate RLS policies - - Generates migration files +### Risk Levels Explained + + + Tables with sensitive data that have **no RLS enabled**. - **Run in Mission Control**: Run before major releases + **Examples** + - User profiles or authentication-related tables + - Financial or billing data + - Private messages or personal content - + **What happens** + - RLS is enabled automatically + - Baseline access policies are generated + - Fixes are committed directly to the PR branch + -### Development Environment Sync + + Policies exist but are **overly permissive** or unsafe. -Keep dev and production schemas aligned: + **Examples** + - Policies using `USING (true)` + - Write access without proper ownership checks + - Admin policies without role validation - + **What happens** + - Restrictive policies are generated + - Unsafe rules are replaced + - Fixes are committed to the PR branch + - **Task Example**: "Compare dev and production schemas and generate sync migrations" + + Partial or incomplete RLS coverage. - **What the Agent Does**: - - Connects to multiple Supabase projects - - Compares schema definitions - - Identifies differences - - Generates sync migrations - - Validates compatibility + **Examples** + - SELECT policy exists but UPDATE or DELETE is missing + - Missing user-scoped access patterns + - Incomplete CRUD coverage - **Run in Mission Control**: Schedule or run manually + **What happens** + - Missing policies are added + - Fixes are committed to the PR branch + - + + Policies work, but could be improved. -## Running Supabase Agents in Mission Control + **Examples** + - Poor policy naming + - Redundant or inefficient rules + - Missing documentation -You can run Supabase-connected agents in two ways as [one-off tasks](../tasks) or automated [workflows](../workflows): + **What happens** + - No automatic fixes + - Suggestions are included in the PR comment only + + - - Start with manual tasks to refine your content queries, then automate repetitive content management and validation tasks. - +Official workflow templates may expand over time as new patterns are validated. You can view, enable, and configure this workflow in **[Mission Control → Integrations → Supabase](https://hub.continue.dev/integrations/supabase)**. -## Common RLS Policy Patterns - -The agent recognizes and implements these standard security patterns: - -### User-Scoped Access - -Users can only access their own data: - -```sql --- SELECT: Users can read their own records -CREATE POLICY "users_select_own" ON user_profiles -FOR SELECT USING (auth.uid() = user_id); - --- UPDATE: Users can update their own records -CREATE POLICY "users_update_own" ON user_profiles -FOR UPDATE USING (auth.uid() = user_id) -WITH CHECK (auth.uid() = user_id); - --- DELETE: Users can delete their own records -CREATE POLICY "users_delete_own" ON user_profiles -FOR DELETE USING (auth.uid() = user_id); -``` - -### Admin Override - -Admins can access all data while users access only their own: - -```sql -CREATE POLICY "posts_select_owner_or_admin" ON posts -FOR SELECT USING ( - auth.uid() = user_id OR - auth.jwt() ->> 'role' = 'admin' -); -``` - -### Public Read, Authenticated Write - -Anyone can read, only authenticated users can write: - -```sql --- Public read access -CREATE POLICY "public_posts_select" ON public_posts -FOR SELECT USING (true); - --- Authenticated insert only -CREATE POLICY "public_posts_insert_auth" ON public_posts -FOR INSERT WITH CHECK (auth.role() = 'authenticated'); -``` - -### Soft Delete Handling +### Advanced Use Cases -Exclude soft-deleted records from queries: - -```sql -CREATE POLICY "posts_select_not_deleted" ON posts -FOR SELECT USING ( - deleted_at IS NULL AND - (auth.uid() = user_id OR is_published = true) -); -``` - -## Troubleshooting - - - - **Problem**: Agent can't connect to Supabase - - **Solutions**: - - Re-authenticate through the integrations page - - Verify OAuth token hasn't expired (expires after 7 days) - - Check project permissions - - Ensure Supabase project is accessible - - For CI/CD, verify environment variables are set - - - - - - **Problem**: Agent reports no tables found to audit - - **Solutions**: - - Verify PR contains database-related changes - - Check that migration files use standard naming - - Ensure SDK calls use `.from('table_name')` pattern - - Review PR for schema/type definition changes - - - - - - **Problem**: Agent identifies issues but doesn't create fixes - - **Solutions**: - - Check if issues are Low priority (agent suggests only) - - Verify agent has write access to repository - - Review error messages in agent logs - - Ensure Supabase MCP connection is working - - Check if migration directory exists - - - - - - **Problem**: Auto-generated RLS policies block legitimate access - - **Solutions**: - - Review and adjust policies in the generated migration - - Add custom logic for your specific access patterns - - Mark tables for manual policy creation if needed - - Provide feedback to improve future policy generation - - - - - - **Problem**: Generated migration conflicts with existing changes - - **Solutions**: - - Review both migrations and merge manually - - Ensure migration timestamps are unique - - Check for duplicate policy names - - Adjust generated migration as needed + +These examples are not officially maintained by the Continue team, but illustrate what’s possible with custom workflows. +- Run scheduled audits across high-risk tables (beyond PR scope) +- Generate migration suggestions for schema changes even when no issues are Critical/High/Medium +- Review SQL performance risks (missing indexes, expensive queries) before merge +- Enforce schema conventions (naming, constraints, standard columns) +- Generate “security notes” summaries for release PRs or weekly reports -## Security Best Practices +--- - +## Access & Permissions - **Development vs. Production**: - - Always test RLS policies in development first - - Use separate Supabase projects for dev/staging/prod - - Never disable RLS on production tables - - Review all generated policies before deploying - - Test policies with different user roles +When connecting Supabase, you’ll authorize Continue to access your Supabase project(s) through the integration. - +- **Project selection** + Choose the Supabase organization and project you want Mission Control to connect to. - +- **Permissions** + Approved permissions allow Continue to inspect RLS and policies, generate recommended migrations, and support workflows that comment on PRs and commit fixes. - Before deploying RLS changes, verify: - - [ ] RLS is enabled on all sensitive tables - - [ ] Policies cover all CRUD operations (SELECT, INSERT, UPDATE, DELETE) - - [ ] User-scoped data includes `auth.uid()` checks - - [ ] Admin overrides verify admin role properly - - [ ] Public access is intentional and documented - - [ ] Policies include `WITH CHECK` clauses for writes - - [ ] Soft deletes filter out `deleted_at IS NOT NULL` - - [ ] Policy names follow naming conventions - - [ ] Rollback commands are included - - [ ] Policies are tested with different user scenarios +You can update or revoke access at any time from Supabase or the Mission Control Hub. - +--- ## Support & Resources - - - - Complete guide to database security automation with Supabase and Continue - + + Combine Supabase with GitHub for PR-triggered security workflows. - - - Combine Supabase with GitHub for automated security workflows - - - - - - Official Supabase Row Level Security documentation - + + Learn more about Row Level Security and recommended policy patterns. - - - - Learn about the Supabase MCP Server. - - -