diff --git a/docs/docs.json b/docs/docs.json index 56c6e23037d..69bfb1e1635 100644 --- a/docs/docs.json +++ b/docs/docs.json @@ -239,7 +239,6 @@ "guides/codebase-documentation-awareness", "guides/cli", "guides/continuous-ai", - "guides/snyk-mcp-continue-cookbook", "guides/continuous-ai-readiness-assessment", "guides/plan-mode-guide", "guides/ollama-guide", @@ -254,6 +253,7 @@ "icon": "book-open-cover", "pages": [ "guides/posthog-github-continuous-ai", + "guides/snyk-mcp-continue-cookbook", "guides/netlify-mcp-continuous-deployment" ] } diff --git a/docs/guides/netlify-mcp-continuous-deployment.mdx b/docs/guides/netlify-mcp-continuous-deployment.mdx index b16c8d5f3e6..c852de1de2e 100644 --- a/docs/guides/netlify-mcp-continuous-deployment.mdx +++ b/docs/guides/netlify-mcp-continuous-deployment.mdx @@ -44,18 +44,82 @@ This cookbook teaches you to: ## Quick Setup + + The Netlify Development Rules bundle includes guardrails for: + - Proper `.gitignore` configuration + - Function structure and placement + - Edge function constraints + - Local development best practices + + +For all options, first: - + ```bash npm i -g @continuedev/cli ``` + + + 1. Install Netlify CLI: `npm i -g netlify-cli` + 2. Authenticate with Netlify: + `netlify login` + + + +## Netlify Continuous AI Workflow Options + + + Skip the manual setup and use our pre-built Netlify Continuous AI agent that includes + optimized prompts, rules, and the Netlify MCP for more consistent results. + + +After completing **Quick Setup** above, you have two paths to get started: + + + + + + + Visit the [Netlify Continuous AI Agent](https://hub.continue.dev/continuedev/netlify-continuous-ai) on Continue Hub and click **"Install Agent"** + + This agent includes: + - **Optimized prompts** for Netlify deployment and performance analysis + - **Built-in rules** for consistent formatting and error handling + - **Netlify MCP** for more reliable API interactions + + + + The agent uses the Netlify MCP automatically and includes best practice rules for deployment and performance optimization. + + + + Navigate to your project directory and run: + ```bash + cn "Analyze my Netlify site's performance and optimize it for better Core Web Vitals." + ``` + + That's it! The agent handles everything automatically. + + + + + **Why Use the Agent?** Results are more consistent and debugging is easier thanks to the Netlify MCP integration and pre-tested prompts. You can remix the agent later to customize it to your needs. + + + + + + + - 1. Install Netlify CLI: `npm i -g netlify-cli` 2. Authenticate with Netlify: - `netlify login` 3. Visit [Netlify MCP on Continue - Hub](https://hub.continue.dev/netlify/netlify-mcp) 4. Follow the configuration - instructions for your editor + 1. Authenticate with Netlify: + `netlify login` + 2. Visit [Netlify MCP on Continue + Hub](https://hub.continue.dev/netlify/netlify-mcp) + 3. Follow the configuration instructions for your editor + @@ -77,13 +141,26 @@ This cookbook teaches you to: ``` + + + + You're all set! Now you can use cn CLI to interact with Netlify using natural language prompts. Check out the examples below to get started. + + + + + + To use the pre-built agent, you need either: + - **Continue CLI Pro Plan** with + the models add-on, OR + - **Your own API keys** added to Continue Hub secrets + The agent will automatically detect and use your + configuration along with the Netlify MCP for deployment operations. + + - - The Netlify Development Rules bundle includes guardrails for: - Proper - `.gitignore` configuration - Function structure and placement - Edge function - constraints - Local development best practices - +--- ## Performance Optimization Steps @@ -375,6 +452,14 @@ Unlike Google Analytics, Netlify Analytics: ## Automated Performance Checks +### Add GitHub Secrets + +Navigate to **Repository Settings → Secrets and variables → Actions** and add: + +- `CONTINUE_API_KEY`: Your Continue API key from [hub.continue.dev/settings/api-keys](https://hub.continue.dev/settings/api-keys) +- `NETLIFY_AUTH_TOKEN`: Your Netlify personal access token +- `NETLIFY_SITE_ID`: Your Netlify site ID + ### GitHub Actions Performance Guard Block PRs that degrade performance: @@ -394,17 +479,28 @@ jobs: with: node-version: "22" + - name: Install Continue CLI + run: | + npm install -g @continuedev/cli + echo "✅ Continue CLI installed" + + - name: Authenticate Continue CLI + env: + CONTINUE_API_KEY: ${{ secrets.CONTINUE_API_KEY }} + run: | + cn auth login --api-key "$CONTINUE_API_KEY" + echo "✅ Continue CLI authenticated" + - name: Deploy and Test Performance id: perf env: NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }} NETLIFY_SITE_ID: ${{ secrets.NETLIFY_SITE_ID }} run: | - npx @continuedev/cli@latest << 'EOF' - Deploy PR preview and run Lighthouse. - Compare scores with main branch. - Output JSON with score deltas. - EOF > performance.json + echo "🚀 Deploying PR preview and analyzing performance..." + cn -p "Deploy PR preview and run Lighthouse. + Compare scores with main branch. + Output JSON with score deltas." > performance.json - name: Comment Performance Results uses: actions/github-script@v7 @@ -442,9 +538,11 @@ jobs: ``` - This workflow will: - **Block merge** if performance score drops >10 points - - **Warn** on any performance regression - **Celebrate** improvements with green - indicators + This workflow will: + - **Block merge** if performance score drops >10 points + - **Warn** on any performance regression + - **Celebrate** improvements with green indicators + ## Performance Testing Locally @@ -528,9 +626,12 @@ Features many developers don't know Netlify offers: **[On-Demand - Builders](https://docs.netlify.com/configure-builds/on-demand-builders/)** - - Generate pages only when requested - Cache dynamically generated content - - Perfect for large sites (10k+ pages) - Reduce build times dramatically + Builders](https://docs.netlify.com/configure-builds/on-demand-builders/)** + - Generate pages only when requested + - Cache dynamically generated content + - Perfect for large sites (10k+ pages) + - Reduce build times dramatically + diff --git a/docs/guides/posthog-github-continuous-ai.mdx b/docs/guides/posthog-github-continuous-ai.mdx index 1742d601114..a84b64e1e60 100644 --- a/docs/guides/posthog-github-continuous-ai.mdx +++ b/docs/guides/posthog-github-continuous-ai.mdx @@ -1,23 +1,32 @@ --- title: "Building a Continuous AI Workflow with PostHog and GitHub" -description: "Build an automated system that continuously monitors PostHog session recordings, analyzes UX issues using Continue CLI, and creates GitHub issues automatically." -sidebarTitle: "PostHog Session Analysis with Continue CLI" +description: "Build an automated system that continuously monitors PostHog analytics, analyzes user behavior with AI, and creates GitHub issues automatically using PostHog MCP." +sidebarTitle: "PostHog Analytics with Continue CLI" --- - A fully automated workflow that uses Continue CLI to fetch PostHog session - data, analyze user experience issues with AI, and automatically create GitHub - issues with specific technical recommendations + A fully automated workflow that uses Continue CLI with the PostHog MCP to fetch analytics data, analyze user experience issues with AI, and automatically create GitHub + issues with the GitHub CLI. +## What You'll Learn + +This cookbook teaches you to: + +- Use [PostHog MCP](https://posthog.com/docs/model-context-protocol) to query [analytics](https://posthog.com/docs/web-analytics), [errors](https://posthog.com/docs/error-tracking), and [feature flags](https://posthog.com/docs/feature-flags) +- Analyze user behavior patterns with AI +- Automatically create GitHub issues using GitHub CLI +- Set up continuous monitoring with GitHub Actions + ## Prerequisites Before starting, ensure you have: - GitHub repository where you want to create issues -- PostHog account with **[session recordings enabled and collecting data](https://posthog.com/docs/session-replay/installation)** +- [PostHog account](https://posthog.com) with [session recordings enabled](https://posthog.com/docs/session-replay/installation) and data collecting - Node.js 18+ installed locally -- Continue CLI account with **active credits** (required for API usage) +- [Continue CLI](https://docs.continue.dev/guides/cli) with **active credits** (required for API usage) +- [GitHub CLI](https://cli.github.com/) installed (`gh` command) @@ -66,39 +75,38 @@ First, you'll need to gather your PostHog and GitHub API credentials and add the 7. Note your PostHog host URL (e.g., `https://us.posthog.com` or your custom domain) 8. You'll also need your POSTHOG_AUTH_HEADER value, which is simply `Bearer YOUR_API_KEY` - - **Find Your Project Details**: Your Project ID is in your PostHog URL: - `https://app.posthog.com/project/YOUR_PROJECT_ID` - + + **Continue Secrets**: The `POSTHOG_AUTH_HEADER` secret should be stored in + Continue's secure secrets storage. This keeps your API key safe and the MCP + automatically connects to your default PostHog project. + - - You'll need a **Personal Access Token** to create issues in your GitHub repository: + + GitHub CLI handles authentication automatically - no manual PAT needed: - 1. Go to [GitHub Personal Access Tokens](https://github.com/settings/personal-access-tokens/new) - 2. Click **"Generate new token (classic)"** - 3. Name it "Continue CLI PostHog Analysis" - 4. Select these scopes: - - `repo` (or just `public_repo` if your repository is public) - - `issues:write` - **Required** for creating issues - 5. Copy the token immediately + 1. Install GitHub CLI if not already installed + 2. Run `gh auth login` and follow the prompts + 3. Choose authentication method (browser or token) + 4. Grant necessary permissions when prompted (`issues:write` is **required** for creating issues) - - -### Add Secrets to Continue CLI + + + +See https://docs.continue.dev/hub/secrets/secret-types#secret-types for adding secrets + -To add environment variables to your Continue Hub account: +You only need to configure the PostHog MCP credential - it automatically handles project selection. To add environment variables to your Continue Hub account: 1. Go to the [Continue Hub](https://hub.continue.dev) 2. Sign in to your account 3. Navigate to your user settings 4. Look for the "Secrets" section -5. Add your variables there (like POSTHOG_API_KEY, POSTHOG_PROJECT_ID, - POSTHOG_HOST,GITHUB_PAT, etc.) +5. Add your Personal API Key from PostHog (phx_...) as POSTHOG_AUTH_HEADER secret with format: Bearer YOUR_API_KEY -These environment variables will then be securely stored and available for use in -your Continue workflows. + + ## PostHog GitHub Continuous AI Workflow Options @@ -107,7 +115,17 @@ your Continue workflows. optimized prompts, rules, and the PostHog MCP for more consistent results. -After completing **Step 1** below, you have two paths to get started: + + **How PostHog MCP Works**: + - Your API key is tied to your PostHog account and + organization + - It automatically uses your default project (no project ID + needed) + - If you have multiple projects, use `mcp__posthog__switch-project` to + change + - The MCP connects via `https://mcp.posthog.com/sse` using your account context. + + @@ -115,20 +133,16 @@ After completing **Step 1** below, you have two paths to get started: - Visit the [PostHog GitHub Continuous AI Agent](https://hub.continue.dev/continuedev/awesome-models-posthog-gh) on Continue Hub and click **"Install Agent"** + Visit the [PostHog GitHub Continuous AI Agent](https://hub.continue.dev/continuedev/awesome-models-posthog-gh) on Continue Hub and click **"Install Agent"** or run: + + ```bash + cn --config continuedev/awesome-models-posthog-gh + ``` This agent includes: - - **Optimized prompts** for PostHog analysis and GitHub issue creation - - **Built-in rules** for consistent formatting and error handling - - **PostHog MCP** for more reliable API interactions - - - - The agent uses these Hub resources automatically: - - **Environment Variables**: [bekahhw/env-vars](https://hub.continue.dev/bekahhw/env-vars) - - **Analysis Rules**: [bekah-hawrot-weigel/posthog-github-continuous-ai-rules](https://hub.continue.dev/bekah-hawrot-weigel/posthog-github-continuous-ai-rules) - - **Analysis Prompt**: [continuedev/posthog-analysis](https://hub.continue.dev/continuedev/posthog-analysis) - - **Issue Creation Prompt**: [continuedev/github-issues](https://hub.continue.dev/continuedev/github-issues) + - **Optimized prompts** for [PostHog analysis](https://hub.continue.dev/continuedev/posthog-analysis) and [GitHub issue creation](https://hub.continue.dev/continuedev/posthog-github-issues) + - **[Built-in rules](https://hub.continue.dev/bekah-hawrot-weigel/posthog-github-continuous-ai-rules)** for consistent formatting and error handling + - **[PostHog MCP](https://hub.continue.dev/posthog/posthog-mcp)** for more reliable API interactions @@ -148,72 +162,41 @@ After completing **Step 1** below, you have two paths to get started: - **Perfect for:** Learning the process and customizing prompts. - - Now you'll use Continue CLI to fetch PostHog session data and analyze it for UX issues. Continue CLI handles all the API calls and analysis automatically. - -### Run the PostHog Analysis - -Use this prompt with Continue CLI to fetch and analyze your PostHog sessions: - -```bash -cn -p "I need you to help me analyze PostHog session recordings to identify UX issues. Please: - -1. First, fetch session recordings from PostHog using these details: - - Use the POSTHOG_API_KEY, POSTHOG_PROJECT_ID, and POSTHOG_HOST from my secrets - - API endpoint: {POSTHOG_HOST}/api/projects/{POSTHOG_PROJECT_ID}/session_recordings/?limit=20 - - Include Authorization header: 'Bearer {POSTHOG_API_KEY}' - -2. Filter the sessions to find problematic ones with either: - - console_error_count > 0 (JavaScript errors) - - recording_duration > 300 (sessions longer than 5 minutes) - -3. Analyze the filtered sessions and create exactly 3 GitHub issues for the most critical UX problems. - -4. Format each issue like this: -### 1. **Issue Title Here** -**Problem**: One sentence describing the user problem -**Technical Causes**: Brief technical explanation -**Affected Pages**: List the URLs -**Recommended Fix**: -- Specific action item 1 -- Specific action item 2 -**Priority**: **HIGH** or **MEDIUM** or **LOW** -**Impact**: Quantify the impact (e.g., 'Affects 80% of sessions') - -Please make the API call, analyze the data, and provide the 3 formatted issues. Base all recommendations on actual patterns in the session data." -``` - -### Create GitHub Issues from PostHog Analysis - -Now use Continue CLI to create GitHub issues from your analysis results: - -```bash -cn -p "I have analyzed PostHog session data and identified UX issues. Now I need you to create GitHub issues using the GitHub API. - -Use these details from my secrets: -- GITHUB_PAT: My GitHub Personal Access Token -- Repository: Extract from git remote or ask me to specify - -For each issue in my analysis: -1. Parse the issue title, body content, and priority level -2. Create a GitHub issue via API POST to: https://api.github.com/repos/{owner}/{repo}/issues -3. Use these headers: - - Authorization: token {GITHUB_PAT} - - Accept: application/vnd.github.v3+json - - Content-Type: application/json -4. Set labels based on priority: - - HIGH: [\"bug\", \"high-priority\", \"user-experience\", \"automated\"] - - MEDIUM: [\"enhancement\", \"medium-priority\", \"user-experience\", \"automated\"] - - LOW: [\"low-priority\", \"user-experience\", \"automated\"] -5. Format the issue title as: \"🔍 UX Issue: {original title}\" - -Please create the GitHub issues and confirm they were successfully created with issue numbers and URLs. -" -``` + + + First, install the [PostHog MCP](https://hub.continue.dev/posthog/posthog-mcp) or run: + ```bash + npx -y mcp-remote@latest https://mcp.posthog.com/sse --header Authorization:${{ secrets.continuedev/awesome-models-posthog-gh/posthog/posthog-mcp/POSTHOG_AUTH_HEADER }} + ``` + + + In the Continue Hub, add the [PostHog GitHub Continuous AI Rules](https://hub.continue.dev/bekah-hawrot-weigel/posthog-github-continuous-ai-rules) to your account for better formatting and error handling. + + + Use this prompt with Continue CLI to analyze PostHog data and create GitHub issues: + + ```bash + + # In cn TUI mode: + "Create GitHub issues from the PostHog analysis using gh CLI: + - For each issue, run: gh issue create --title '🔍 UX Issue: [title]' --body '[details]' + - Add labels: --label 'bug,user-experience,automated' + - Set priority labels (high/medium/low) + - Include session data and technical details in the body + Execute the commands and confirm each issue was created with URL." + ``` + + + + + **Why GitHub CLI over GitHub MCP**: While GitHub MCP is available, it can be + token-expensive to run. The `gh` CLI is more efficient, requires no API tokens + (authenticated via `gh auth login`), and provides a cleaner command-line + experience. GitHub MCP remains an option if you prefer full MCP integration. + To use the pre-built agent, you need either: @@ -492,16 +475,17 @@ Consider enhancing your workflow with these advanced Continue CLI prompts: - "Analyze PostHog performance metrics alongside session recordings to - identify slow page loads affecting user experience" + "Analyze [PostHog performance + metrics](https://posthog.com/docs/web-analytics) alongside session + recordings to identify slow page loads affecting user experience" "Cross-reference JavaScript console errors with user actions to identify the root cause of UX issues" - "Analyze how PostHog feature flags impact user behavior in session - recordings" + "Analyze how [PostHog feature flags](https://posthog.com/docs/feature-flags) + impact user behavior in session recordings" "Create Slack alerts when critical UX issues are detected in PostHog @@ -511,7 +495,19 @@ Consider enhancing your workflow with these advanced Continue CLI prompts: ## Next Steps -1. **Monitor your first issues** - Review the GitHub issues created and implement fixes -2. **Measure impact** - Track how resolved issues improve PostHog metrics -3. **Refine prompts** - Adjust the Continue CLI prompts based on issue quality -4. **Scale the system** - Add more data sources or create specialized analysis workflows +- Consider [GitHub MCP](https://hub.continue.dev/github/github-mcp) as an alternative (note: can be token-expensive) +- Configure [Slack MCP](https://hub.continue.dev/slack/slack-mcp) for alerts +- Set up [PostHog performance monitoring](https://posthog.com/docs/web-analytics) +- Join the [Continue Discord](https://discord.gg/continue) for support + +## Resources + +- [PostHog API Documentation](https://posthog.com/docs/api) +- [PostHog MCP Documentation](https://posthog.com/docs/model-context-protocol) +- [PostHog Session Replay](https://posthog.com/docs/session-replay) +- [PostHog Feature Flags](https://posthog.com/docs/feature-flags) +- [PostHog Error Tracking](https://posthog.com/docs/error-tracking) +- [GitHub CLI Documentation](https://cli.github.com/) +- [GitHub MCP on Continue Hub](https://hub.continue.dev/github/github-mcp) (alternative option) +- [Continue CLI Guide](https://docs.continue.dev/guides/cli) +- [Continuous AI Best Practices](https://blog.continue.dev/what-is-continuous-ai-a-developers-guide/) diff --git a/docs/guides/snyk-mcp-continue-cookbook.mdx b/docs/guides/snyk-mcp-continue-cookbook.mdx index 6705fd15c38..709cfd60493 100644 --- a/docs/guides/snyk-mcp-continue-cookbook.mdx +++ b/docs/guides/snyk-mcp-continue-cookbook.mdx @@ -20,9 +20,74 @@ Before starting, ensure you have: - [Snyk account](https://snyk.io/) (free tier works) - A local project to scan for vulnerabilities +For all options, first: + + ```bash + npm i -g @continuedev/cli + ``` + + + + + 1. Sign up for a Snyk account at [snyk.io](https://snyk.io/) + 2. Create a new project in Snyk by importing your code repository (Git + provider or manual upload) + + + + To use agents in headless mode, you need a [Continue API key](https://hub.continue.dev/settings/api-keys). + + +## Snyk Continuous AI Workflow Options + + + Skip the manual setup and use our pre-built Snyk Continuous AI agent that includes + the Snyk MCP and optimized security scanning workflows for more consistent results. + + + +After ensuring you meet the **Prerequisites** above, you have two paths to get started: + + + + + + Navigate to your project directory and run: + ```bash + cn --config continuedev/snyk-continuous-ai + ``` + + This agent includes: + - **Snyk MCP** pre-configured and ready to use + - **Security-focused rules** for best practices + + + + Start with a comprehensive security scan: + ```bash + # TUI mode + cn -p "Run a complete security scan on this project including code vulnerabilities, dependencies, and any IaC files. Summarize findings by severity." + ``` + + That's it! The agent handles everything automatically. + + + + + **Why Use the Agent?** The pre-built agent provides consistent security scanning workflows and handles MCP configuration automatically, making it easier to get started with AI-powered security scanning. + + + + + + + + Go to the [Continue Hub](https://hub.continue.dev) and [create a new agent](https://hub.continue.dev/new?type=agent). + + - Visit the [Snyk MCP on Continue Hub](https://hub.continue.dev/snyk/snyk-mcp) and click **Install** to add it to your Continue account. + Visit the [Snyk MCP on Continue Hub](https://hub.continue.dev/snyk/snyk-mcp) and click **Install** to add it to the agent you created in the step above. This will add Snyk MCP to your agent's available tools. The Hub listing automatically configures the MCP command: ```bash @@ -31,7 +96,7 @@ Before starting, ensure you have: **Alternative installation methods:** - 1. **Quick CLI install**: `cn -p --mcp snyk/snyk-mcp` + 1. **Quick CLI install**: `cn --mcp snyk/snyk-mcp` 2. **Manual configuration**: Add the MCP to your `~/.continue/config.json` under the `mcpServers` section Once installed, Snyk MCP tools become available to your Continue agent for all prompts. @@ -59,35 +124,42 @@ Before starting, ensure you have: - - Use this prompt with your Continue agent to set up authentication: - - ``` - Check Snyk auth status. If not authenticated, authenticate me and confirm my org context. - ``` - - Or use the Continue CLI: + + Start with a comprehensive security scan: ```bash - cn -p "Check Snyk auth status. If not authenticated, authenticate me and confirm my org context." + # TUI mode + cn "Run a complete security scan on this project including code vulnerabilities, dependencies, and any IaC files. Summarize findings by severity." ``` - - - A browser window will open for Snyk login. After authenticating, approve - the request to trust your project folder when prompted. - - + + + + + To use the pre-built agent, you need either: + - **Continue CLI Pro Plan** with the models add-on, OR + - **Your own API keys** added to Continue Hub secrets (same as manual setup) + + The agent will automatically detect and use your configuration along with the pre-configured Snyk MCP for security scanning operations. + + + +--- + ## Security Scanning Recipes Now you can use natural language prompts to run comprehensive security scans. The Continue agent automatically calls the appropriate Snyk MCP tools. + +You can add prompts to your agent's configuration for easy access in future sessions. Go to your agent in the [Continue Hub](https://hub.continue.dev), click **Edit**, and add prompts under the **Prompts** section. + + **Where to run these workflows:** - **IDE Extensions**: Use Continue in VS Code, JetBrains, or other supported IDEs - **Terminal (TUI mode)**: Run `cn` to enter interactive mode, then type your prompts - - **CLI (headless mode)**: Use `cn -p "your prompt"` for one-off commands + - **CLI (headless mode)**: Use `cn -p "your prompt"` for headless commands **Test in Plan Mode First**: Before running security scans that might make changes, test your prompts in plan mode (see the [Plan Mode @@ -101,14 +173,14 @@ Now you can use natural language prompts to run comprehensive security scans. Th Scan your source code for security vulnerabilities and code quality issues. -**Example prompt:** +**TUI Mode Prompt:** ``` Run a Snyk Code scan on this repo with severity threshold medium. Summarize issues with file:line. Propose minimal diffs for the top 3 and rerun to verify. ``` -**Using Continue CLI:** +**Headless Mode Prompt:** ```bash cn -p "Run a Snyk Code scan on this repo with severity threshold medium. Summarize issues with file:line. Propose minimal diffs for the top 3 and rerun to verify." ``` @@ -120,14 +192,14 @@ cn -p "Run a Snyk Code scan on this repo with severity threshold medium. Summari Check open source dependencies for known vulnerabilities. -**Example prompt:** +**TUI Mode Prompt:** ``` Run Snyk Open Source on this repo (include dev deps). Summarize vulnerable paths and propose a minimal-risk upgrade plan. Re-test after the plan (dry run). ``` -**Using Continue CLI:** +**Headless Mode Prompt:** ```bash cn -p "Run Snyk Open Source on this repo (include dev deps). Summarize vulnerable paths and propose a minimal-risk upgrade plan. Re-test after the plan (dry run)." ``` @@ -139,13 +211,13 @@ cn -p "Run Snyk Open Source on this repo (include dev deps). Summarize vulnerabl Scan Terraform, CloudFormation, and Kubernetes configs for misconfigurations. -**Example prompt:** +**TUI Mode Prompt:** ``` Scan ./infra with Snyk IaC. Report high/critical misconfigs with exact files/lines. Provide code changes and re-scan to confirm. ``` -**Using Continue CLI:** +**Headless Mode Prompt:** ```bash cn -p "Scan ./infra with Snyk IaC. Report high/critical misconfigs with exact files/lines. Provide code changes and re-scan to confirm." ``` @@ -157,14 +229,14 @@ cn -p "Scan ./infra with Snyk IaC. Report high/critical misconfigs with exact fi Analyze Docker images for vulnerabilities in base images and packages. -**Example prompt:** +**TUI Mode Prompt:** ``` Scan image my-api:latest. Exclude base image vulns. Print dependency tree. Recommend a safer base image or upgrades. Re-test after the change (dry run). ``` -**Using Continue CLI:** +**Headless Mode Prompt:** ```bash cn -p "Scan image my-api:latest. Exclude base image vulns. Print dependency tree. Recommend a safer base image or upgrades. Re-test after the change (dry run)." ``` @@ -176,13 +248,13 @@ cn -p "Scan image my-api:latest. Exclude base image vulns. Print dependency tree Focus scanning on modified files to catch issues before merging. -**Example prompt:** +**TUI Mode Prompt:** ``` Scan only files changed since origin/main with Snyk Code. Block if new high issues would be introduced. Show deltas. ``` -**Using Continue CLI:** +**Headless Mode Prompt:** ```bash cn -p "Scan only files changed since origin/main with Snyk Code. Block if new high issues would be introduced. Show deltas." ``` @@ -194,12 +266,12 @@ cn -p "Scan only files changed since origin/main with Snyk Code. Block if new hi Access security education resources based on identified vulnerabilities ([CWE](https://cwe.mitre.org/)). -**Example prompt:** +**TUI Mode Prompt:** ``` Open Snyk Learn lessons related to the top CWE(s) from this scan. ``` -**Using Continue CLI:** +**Headless Mode Prompt:** ```bash cn -p "Open Snyk Learn lessons related to the top CWE(s) from this scan." ``` @@ -208,7 +280,7 @@ cn -p "Open Snyk Learn lessons related to the top CWE(s) from this scan." ## Continuous Security with GitHub Actions -This example demonstrates a **Continuous AI workflow** where security scanning runs automatically in your CI/CD pipeline using Continue CLI in headless mode (`cn -p`) with Snyk MCP. +This example demonstrates a **Continuous AI workflow** where security scanning runs automatically in your CI/CD pipeline Headless Mode Prompt in headless mode (`cn -p`) with Snyk MCP. ### Add GitHub Secrets @@ -249,8 +321,10 @@ jobs: echo "✅ Continue CLI installed" - name: Authenticate Continue CLI + env: + CONTINUE_API_KEY: ${{ secrets.CONTINUE_API_KEY }} run: | - cn auth login --api-key "${{ secrets.CONTINUE_API_KEY }}" + cn auth login --api-key "$CONTINUE_API_KEY" echo "✅ Continue CLI authenticated" - name: Run Security Scans diff --git a/docs/hub/agents/create-an-agent.mdx b/docs/hub/agents/create-an-agent.mdx index f518c48f55f..27de8084650 100644 --- a/docs/hub/agents/create-an-agent.mdx +++ b/docs/hub/agents/create-an-agent.mdx @@ -8,7 +8,8 @@ sidebarTitle: "Create an AI Agent" To create an agent from scratch, select “New agent” in the top bar. -![New agent button](/images/hub/assistants/images/assistant-new-button-16070e2cff9ce25ec9ebfeecb0e2f2b5.png) +![New agent button](/images/hub/new-agent-button.png) + Choose a name, slug, description, and icon for your agent. @@ -24,7 +25,7 @@ You can also create an agent by remixing an existing one. This is useful if you By clicking the “remix” button, you’ll be taken to the “Create a remix” page. -![Remix Agent Button](/images/hub/assistants/images/assistant-remix-button-728ececa73983140eeab42e33cc3903b.png) +![Remix Agent Button](/images/hub/agent-remix-button.png) Once here, you’ll be able to diff --git a/docs/images/hub/agent-remix-button.png b/docs/images/hub/agent-remix-button.png new file mode 100644 index 00000000000..8410177f672 Binary files /dev/null and b/docs/images/hub/agent-remix-button.png differ diff --git a/docs/images/hub/assistant-new-button.png b/docs/images/hub/assistant-new-button.png deleted file mode 100644 index d6088a06102..00000000000 Binary files a/docs/images/hub/assistant-new-button.png and /dev/null differ diff --git a/docs/images/hub/assistants/images/assistant-new-button-16070e2cff9ce25ec9ebfeecb0e2f2b5.png b/docs/images/hub/assistants/images/assistant-new-button-16070e2cff9ce25ec9ebfeecb0e2f2b5.png deleted file mode 100644 index d6088a06102..00000000000 Binary files a/docs/images/hub/assistants/images/assistant-new-button-16070e2cff9ce25ec9ebfeecb0e2f2b5.png and /dev/null differ diff --git a/docs/images/hub/assistants/images/assistant-new-button.png b/docs/images/hub/assistants/images/assistant-new-button.png deleted file mode 100644 index d6088a06102..00000000000 Binary files a/docs/images/hub/assistants/images/assistant-new-button.png and /dev/null differ diff --git a/docs/images/hub/assistants/images/assistant-remix-button.png b/docs/images/hub/assistants/images/assistant-remix-button.png deleted file mode 100644 index 02c9d34ef8b..00000000000 Binary files a/docs/images/hub/assistants/images/assistant-remix-button.png and /dev/null differ diff --git a/docs/images/hub/new-agent-button.png b/docs/images/hub/new-agent-button.png new file mode 100644 index 00000000000..b4c6525acef Binary files /dev/null and b/docs/images/hub/new-agent-button.png differ