diff --git a/docs/docs.json b/docs/docs.json
index 9e61f5d6cb5..adf43cf31e1 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -37,7 +37,10 @@
"mission-control/integrations/github",
"mission-control/integrations/sentry",
"mission-control/integrations/snyk",
- "mission-control/integrations/slack-agent"
+ "mission-control/integrations/slack-agent",
+ "mission-control/integrations/posthog",
+ "mission-control/integrations/atlassian",
+ "mission-control/integrations/netlify"
]
},
"mission-control/metrics",
diff --git a/docs/guides/atlassian-mcp-continue-cookbook.mdx b/docs/guides/atlassian-mcp-continue-cookbook.mdx
index dcfd64a996f..5c00bc9de3d 100644
--- a/docs/guides/atlassian-mcp-continue-cookbook.mdx
+++ b/docs/guides/atlassian-mcp-continue-cookbook.mdx
@@ -13,6 +13,12 @@ sidebarTitle: "Atlassian Workflows with Continue"
- Automate Atlassian workflows with headless CLI runs
+
+ The new [Atlassian Mission Control Integration](/mission-control/integrations/atlassian) enables **[Continuous AI](/guides/continuous-ai)** for project management and documentation - where AI agents autonomously manage Jira issues, sync Confluence documentation, and streamline development workflows. This cookbook focuses on CLI-based workflows, but you can also deploy autonomous agents through Mission Control.
+
+ **Get Started:** Use this cookbook to understand Atlassian MCP fundamentals, then [enable Mission Control](/mission-control/integrations/atlassian) to deploy autonomous project management agents across your organization.
+
+
## Prerequisites
Before starting, ensure you have:
diff --git a/docs/guides/netlify-mcp-continuous-deployment.mdx b/docs/guides/netlify-mcp-continuous-deployment.mdx
index 830fcc730a8..11318a8dac0 100644
--- a/docs/guides/netlify-mcp-continuous-deployment.mdx
+++ b/docs/guides/netlify-mcp-continuous-deployment.mdx
@@ -10,6 +10,12 @@ sidebarTitle: "Using Netlify MCP for Performance Optimization"
from Netlify Analytics
+
+ The new [Netlify Mission Control Integration](/mission-control/integrations/netlify) enables **[Continuous AI](/guides/continuous-ai)** for deployment automation - where AI agents autonomously manage deployments, monitor site performance, and respond to deployment events. This cookbook focuses on CLI-based performance optimization workflows, but you can also deploy autonomous deployment agents through Mission Control.
+
+ **Get Started:** Use this cookbook to understand Netlify MCP fundamentals, then [enable Mission Control](/mission-control/integrations/netlify) to deploy autonomous deployment management agents across your organization.
+
+
**Did You Know?** Netlify is more than just static hosting! It offers:
- [Split Testing](https://docs.netlify.com/site-deploys/split-testing/) for A/B testing branches
diff --git a/docs/guides/posthog-github-continuous-ai.mdx b/docs/guides/posthog-github-continuous-ai.mdx
index 157b3c823e0..6cd701820bc 100644
--- a/docs/guides/posthog-github-continuous-ai.mdx
+++ b/docs/guides/posthog-github-continuous-ai.mdx
@@ -9,6 +9,12 @@ sidebarTitle: "PostHog Analytics with Continue CLI"
issues with the GitHub CLI.
+
+ The new [PostHog Mission Control Integration](/mission-control/integrations/posthog) enables **[Continuous AI](/guides/continuous-ai)** for product analytics - where AI agents autonomously analyze user behavior, identify optimization opportunities, and create data-driven development tasks. This cookbook focuses on CLI-based workflows, but you can also deploy autonomous agents through Mission Control.
+
+ **Get Started:** Use this cookbook to understand PostHog analytics fundamentals, then [enable Mission Control](/mission-control/integrations/posthog) to deploy autonomous analytics-driven agents across your organization.
+
+
## What You'll Learn
This cookbook teaches you to:
diff --git a/docs/mission-control/integrations/atlassian.mdx b/docs/mission-control/integrations/atlassian.mdx
new file mode 100644
index 00000000000..67230b2349d
--- /dev/null
+++ b/docs/mission-control/integrations/atlassian.mdx
@@ -0,0 +1,324 @@
+---
+title: "Atlassian Integration"
+description: "Connect Jira and Confluence to automate project management and documentation with Continue Agents"
+---
+
+## Overview
+
+Connect Atlassian products (Jira and Confluence) to Continue Mission Control to enable agents to manage issues, track projects, and maintain documentation. When Atlassian is enabled, Continue can automate ticket creation, sync documentation, and streamline development workflows.
+
+
+
+ - Automatically create and update Jira issues from code changes
+ - Sync documentation between Confluence and your codebase
+ - Generate release notes and project updates
+ - Track development progress across projects
+ - Automate sprint planning and backlog grooming
+ - Create PRs linked to Jira tickets
+
+
+
+## Setup
+
+
+
+
+
+ Go to your [Integrations Settings](https://hub.continue.dev/integrations).
+
+
+
+
+
+ Click "Connect" next to Atlassian. You'll need the following credentials:
+
+ - **Atlassian Domain**: Your Atlassian domain (e.g., `your-company.atlassian.net`)
+ - **Email**: Your Atlassian account email
+ - **API Token**: Generate from Atlassian account settings
+
+
+
+
+
+ To create an API token:
+ 1. Go to [Atlassian API Tokens](https://id.atlassian.com/manage-profile/security/api-tokens)
+ 2. Click "Create API token"
+ 3. Give it a descriptive name (e.g., "Continue Mission Control")
+ 4. Copy the token immediately (it won't be shown again)
+
+
+
+
+
+ Paste your domain, email, and API token into the integration form and click "Create Connection"
+
+
+
+
+
+
+
+ **Security Best Practice**: Create a dedicated API token for Continue rather than reusing existing tokens. This makes it easier to revoke access if needed.
+
+
+
+## Use Cases
+
+### Automated Issue Management
+
+Create agents that manage your Jira backlog:
+
+
+
+ **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
+
+
+
+### Sprint Planning Automation
+
+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
+
+
+
+### Documentation Sync
+
+Keep Confluence and code documentation in sync:
+
+
+
+ **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
+
+
+
+### Release Management
+
+Automate release notes and changelog generation:
+
+
+
+ **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
+
+
+
+### Project Tracking
+
+Monitor development progress and blockers:
+
+
+
+ **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
+
+
+
+### Code-to-Ticket Linking
+
+Maintain traceability between code and requirements:
+
+
+
+ **Task Example**: "Review recent PRs and ensure they're linked to appropriate Jira tickets"
+
+ **What the Agent Does**:
+ - Scans merged PRs without Jira ticket references
+ - Analyzes PR content to find related tickets
+ - Adds Jira ticket links to PRs and vice versa
+ - Reports PRs that may need ticket creation
+
+ **Run in Mission Control**: Run daily or after PR merges
+
+
+
+## Running Atlassian Agents in Mission Control
+
+You can run Atlassian-connected agents in two ways:
+
+### 1. Manual Tasks
+
+Trigger agents on-demand for project management:
+
+1. Go to [Mission Control Agents](https://hub.continue.dev/agents)
+2. Select or create an Atlassian-enabled agent
+3. Click "Run Agent" and provide your task description
+4. Monitor progress and review results in real-time
+
+**Example Tasks:**
+- "Summarize all critical bugs from the last sprint"
+- "Create architecture decision records in Confluence for recent technical decisions"
+- "Update the project roadmap based on current velocity"
+
+### 2. Automated Workflows
+
+Set up agents to run automatically:
+
+- **Scheduled**: Run daily standup summaries, weekly backlog reviews
+- **Triggered**: Execute on Jira events (new critical bug, sprint completion)
+- **Webhook**: Integrate with CI/CD to update tickets on deployments
+
+
+
+ Start with manual tasks to refine your Jira queries and Confluence formatting, then convert successful patterns to automated workflows.
+
+
+
+## Integration with GitHub
+
+Combine Atlassian with GitHub for complete development workflow automation:
+
+
+
+
+
+ Enable both Atlassian and GitHub integrations in Mission Control
+
+
+
+
+
+ Build an agent that:
+ - Creates PRs for Jira tickets
+ - Updates ticket status based on PR state
+ - Links code changes to requirements
+ - Updates Confluence with technical decisions
+
+
+
+
+
+ Configure the agent to run throughout the development lifecycle
+
+
+
+
+
+## Monitoring Agent Activity
+
+Track your agent's project management automation:
+
+1. **View in Mission Control**: See all agent runs and their outputs
+2. **Check Jira**: Verify tickets are created and updated correctly
+3. **Review Confluence**: Ensure documentation is accurate and well-formatted
+4. **Monitor Metrics**: Track automation impact on team velocity
+
+## 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
+
+
+
+
+
+ **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
+
+
+
+
+
+ **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
+
+
+
+## Support & Resources
+
+
+
+
+
+ Comprehensive guide to project management automation with Atlassian and Continue
+
+
+
+
+
+ Combine Atlassian with GitHub for complete DevOps automation
+
+
+
+
diff --git a/docs/mission-control/integrations/index.mdx b/docs/mission-control/integrations/index.mdx
index 9bb796866fe..357401220d1 100644
--- a/docs/mission-control/integrations/index.mdx
+++ b/docs/mission-control/integrations/index.mdx
@@ -1,6 +1,6 @@
---
title: "Overview"
-description: "Connect GitHub, Slack, Sentry, and Snyk to power richer Agents, Tasks, and Workflows."
+description: "Connect GitHub, Slack, Sentry, Snyk, PostHog, Atlassian, and Netlify to power richer Agents, Tasks, and Workflows."
sidebarTitle: "Overview"
---
@@ -8,7 +8,7 @@ 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 four first-class integrations:
+Mission Control currently supports seven first-class integrations:
@@ -28,6 +28,18 @@ Mission Control currently supports four first-class integrations:
Detect and fix security vulnerabilities automatically.
+
+ Leverage product analytics and feature flags for data-driven development.
+
+
+
+ Connect Jira and Confluence to automate project management and docs.
+
+
+
+ Automate deployments and manage site configuration.
+
+
diff --git a/docs/mission-control/integrations/netlify.mdx b/docs/mission-control/integrations/netlify.mdx
new file mode 100644
index 00000000000..1020c08d82f
--- /dev/null
+++ b/docs/mission-control/integrations/netlify.mdx
@@ -0,0 +1,324 @@
+---
+title: "Netlify Integration"
+description: "Automate deployments and site management with Continue Agents connected to Netlify"
+---
+
+## Overview
+
+Connect Netlify to Continue Mission Control to enable agents to manage deployments, monitor site performance, and automate your continuous deployment pipeline. When Netlify is enabled, Continue can trigger builds, manage environments, and respond to deployment events.
+
+
+
+ - Automatically trigger and monitor deployments
+ - Manage environment variables and build settings
+ - Create and test deploy previews
+ - Monitor site performance and uptime
+ - Automate rollback on errors or failed tests
+ - Generate deployment reports and notifications
+
+
+
+## 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"
+
+
+
+
+
+
+
+ **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.
+
+
+
+## Use Cases
+
+### Automated Deployment Management
+
+Create agents that manage your deployment pipeline:
+
+
+
+ **Task Example**: "Deploy the staging branch to preview environment and run smoke tests"
+
+ **What the Agent Does**:
+ - Triggers Netlify build for specified branch
+ - Monitors build progress and logs
+ - Runs automated tests on deploy preview
+ - Reports results and preview URL
+
+ **Run in Mission Control**: Trigger on PR creation or manual request
+
+
+
+### Environment Configuration
+
+Automate environment variable management:
+
+
+
+ **Task Example**: "Sync environment variables from .env.example to all Netlify sites"
+
+ **What the Agent Does**:
+ - Reads environment variable definitions
+ - Updates Netlify site settings
+ - Verifies variables are set correctly
+ - Triggers rebuild if necessary
+
+ **Run in Mission Control**: Run after config updates or schedule periodic audits
+
+
+
+### Performance Monitoring
+
+Track and respond to site performance issues:
+
+
+
+ **Task Example**: "Monitor production deployment and rollback if Core Web Vitals degrade"
+
+ **What the Agent Does**:
+ - Tracks deployment performance metrics
+ - Compares against baseline thresholds
+ - Automatically rolls back if issues detected
+ - Creates incident report with details
+
+ **Run in Mission Control**: Set up as continuous monitoring for production
+
+
+
+### Deploy Preview Testing
+
+Automate testing of deploy previews:
+
+
+
+ **Task Example**: "Run visual regression tests on deploy preview and comment results on PR"
+
+ **What the Agent Does**:
+ - Waits for deploy preview to be ready
+ - Executes test suite against preview URL
+ - Captures screenshots and differences
+ - Posts results as PR comment
+
+ **Run in Mission Control**: Trigger on deploy preview creation
+
+
+
+### Site Health Monitoring
+
+Proactively monitor site availability and health:
+
+
+
+ **Task Example**: "Check all production sites every hour and create alerts for downtime or errors"
+
+ **What the Agent Does**:
+ - Pings production sites to verify availability
+ - Checks for broken links or 500 errors
+ - Monitors SSL certificate expiration
+ - Creates incidents for issues found
+
+ **Run in Mission Control**: Schedule hourly health checks
+
+
+
+### Automated Rollback
+
+Implement intelligent rollback strategies:
+
+
+
+ **Task Example**: "Monitor error rates after deployment and rollback if errors exceed 1%"
+
+ **What the Agent Does**:
+ - Tracks error metrics post-deployment
+ - Analyzes error patterns and severity
+ - Triggers rollback to previous version if threshold exceeded
+ - Notifies team with incident details
+
+ **Run in Mission Control**: Set up as post-deployment monitoring
+
+
+
+## Running Netlify Agents in Mission Control
+
+You can run Netlify-connected agents in two ways:
+
+### 1. Manual Tasks
+
+Trigger agents on-demand for deployment operations:
+
+1. Go to [Mission Control Agents](https://hub.continue.dev/agents)
+2. Select or create a Netlify-enabled agent
+3. Click "Run Agent" and provide your task description
+4. Monitor progress and review results in real-time
+
+**Example Tasks:**
+- "Create a new deploy preview for the feature/redesign branch"
+- "List all sites and their current deployment status"
+- "Update production environment variables for API endpoints"
+
+### 2. Automated Workflows
+
+Set up agents to run automatically:
+
+- **Event-triggered**: Execute on Git push, PR creation, or deployment completion
+- **Scheduled**: Run daily site audits or weekly performance reviews
+- **Threshold-based**: Trigger on metric anomalies or build failures
+
+
+
+ Start with manual deployment tasks to validate your workflow, then automate repetitive deployment patterns and monitoring tasks.
+
+
+
+## Integration with GitHub
+
+Combine Netlify with GitHub for complete CI/CD automation:
+
+
+
+
+
+ Enable both Netlify and GitHub integrations in Mission Control
+
+
+
+
+
+ Build an agent that:
+ - Monitors GitHub for new PRs
+ - Triggers Netlify deploy previews
+ - Runs automated tests on preview
+ - Updates PR status and adds preview URL
+ - Manages production deployments on merge
+
+
+
+
+
+ Configure the agent to handle the entire deployment workflow automatically
+
+
+
+
+
+## Monitoring Agent Activity
+
+Track your agent's deployment automation:
+
+1. **View in Mission Control**: See all agent runs and deployment actions
+2. **Check Netlify Dashboard**: Verify builds and deployments
+3. **Review Deploy Logs**: Ensure builds complete successfully
+4. **Monitor Metrics**: Track deployment frequency and success rate
+
+## 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**: Agent can't trigger Netlify builds
+
+ **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**: Can't update site environment variables
+
+ **Solutions**:
+ - Confirm you have admin access to the site
+ - Check variable name format (no spaces or special chars)
+ - Ensure values are properly escaped
+ - Verify API token has write permissions
+
+
+
+
+
+ **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
+
+
+
+
+
+ **Problem**: Can't retrieve site performance metrics
+
+ **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
+
+
+
+## Support & Resources
+
+
+
+
+
+ Complete guide to continuous deployment automation with Netlify and Continue
+
+
+
+
+
+ Combine Netlify with GitHub for end-to-end CI/CD automation
+
+
+
+
diff --git a/docs/mission-control/integrations/posthog.mdx b/docs/mission-control/integrations/posthog.mdx
new file mode 100644
index 00000000000..d0a1d953faa
--- /dev/null
+++ b/docs/mission-control/integrations/posthog.mdx
@@ -0,0 +1,297 @@
+---
+title: "PostHog Integration"
+description: "Leverage product analytics and feature flags with Continue Agents connected to PostHog"
+---
+
+## 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
+
+
+
+## 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 **Project 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
+
+You can run PostHog-connected agents in two ways:
+
+### 1. Manual Tasks
+
+Trigger agents on-demand for analytics insights:
+
+1. Go to [Mission Control Agents](https://hub.continue.dev/agents)
+2. Select or create a PostHog-enabled agent
+3. Click "Run Agent" and provide your task description
+4. Monitor progress and review results in real-time
+
+**Example Tasks:**
+- "What are the most common user paths leading to checkout abandonment?"
+- "Compare mobile vs desktop conversion rates for the last month"
+- "Identify features with low adoption that we should sunset"
+
+### 2. Automated Workflows
+
+Set up agents to run automatically:
+
+- **Scheduled**: Run daily, weekly, or monthly analytics reviews
+- **Metric-triggered**: Execute when KPIs cross thresholds
+- **Event-based**: Trigger on feature flag changes or experiment completion
+
+
+
+ Start with manual exploratory tasks to understand your data, then automate recurring analysis patterns with scheduled workflows.
+
+
+
+## Integration with GitHub
+
+Combine PostHog with GitHub integration for data-driven development:
+
+
+
+
+
+ Enable both PostHog and GitHub integrations in Mission Control
+
+
+
+
+
+ Build an agent that:
+ - Monitors PostHog metrics and user behavior
+ - Identifies optimization opportunities
+ - Creates issues or PRs with data-backed improvements
+ - Links PostHog dashboards in PR descriptions
+
+
+
+
+
+ Configure the agent to run on a schedule or when metrics indicate action is needed
+
+
+
+
+
+## Monitoring Agent Activity
+
+Track your agent's analytics-driven development:
+
+1. **View in Mission Control**: See all agent runs and their insights
+2. **Check PostHog**: Verify data accuracy and explore referenced metrics
+3. **Review Issues/PRs**: Ensure recommendations are actionable
+4. **Monitor Impact**: Track whether changes improve metrics
+
+## 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
+
+
+
+
+
+ **Problem**: Agent can't modify feature flags
+
+ **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
+
+
+
+
+
+ **Problem**: Can't connect to self-hosted PostHog instance
+
+ **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
+
+
+
+## Support & Resources
+
+
+
+
+
+ Complete guide to building product-led development workflows with PostHog and Continue
+
+
+
+
+
+ Combine PostHog with GitHub for data-driven development automation
+
+
+
+