From c6e6a7a4539207e32ee9a93342c7fc4f077f8f54 Mon Sep 17 00:00:00 2001 From: "continue[bot]" Date: Sat, 1 Nov 2025 01:31:27 +0000 Subject: [PATCH 01/11] Add comprehensive Slack integration documentation for agents - Created detailed guide at docs/hub/agents/slack-integration.mdx - Covers setup, usage, configuration, and troubleshooting - Includes examples for inline repos, default repos, and interactive selection - Documents follow-up messages, agent restarts, and thread context - Added organization-level integration section - Includes best practices and security information - Updated docs.json navigation to include the new page Co-authored-by: dallin Generated with [Continue](https://continue.dev) Co-Authored-By: Continue --- docs/docs.json | 2 +- docs/hub/agents/slack-integration.mdx | 340 ++++++++++++++++++++++++++ 2 files changed, 341 insertions(+), 1 deletion(-) create mode 100644 docs/hub/agents/slack-integration.mdx diff --git a/docs/docs.json b/docs/docs.json index 88cea7782f4..2868c5f1256 100644 --- a/docs/docs.json +++ b/docs/docs.json @@ -57,7 +57,7 @@ { "group": "Agents", "icon": "cloud", - "pages": ["hub/agents/intro"] + "pages": ["hub/agents/intro", "hub/agents/slack-integration"] }, "hub/sharing", "hub/source-control" diff --git a/docs/hub/agents/slack-integration.mdx b/docs/hub/agents/slack-integration.mdx new file mode 100644 index 00000000000..32087c267a6 --- /dev/null +++ b/docs/hub/agents/slack-integration.mdx @@ -0,0 +1,340 @@ +--- +title: "Slack Integration" +description: "Trigger agents from Slack by mentioning @Continue" +--- + + + The Slack integration allows you to start and manage Continue agents directly from your Slack workspace. This is currently in beta. + + +## Overview + +The Continue Slack integration enables you to: + +- **Start agents** by mentioning `@Continue` in any Slack channel +- **Send follow-up messages** to existing agents by mentioning `@Continue` in the agent's thread +- **Select repositories** interactively when starting an agent +- **Configure default repositories** to streamline agent creation +- **Use agent files** to customize behavior with specific prompts, tools, and rules + +## Setup + +### 1. Install the Slack App + + + + Go to [hub.continue.dev/settings/integrations](https://hub.continue.dev/settings/integrations) + + + + Click the "Connect" button next to Slack and authorize the app in your workspace + + + + After authorization, you'll be redirected back to Continue Hub with a success message + + + +### 2. Connect GitHub + +Before using the Slack integration, ensure you have the Continue GitHub App installed: + +1. Go to [hub.continue.dev/settings/integrations](https://hub.continue.dev/settings/integrations) +2. Click "Connect" next to GitHub +3. Grant access to the repositories you want Continue to work with + +## Usage + +### Starting an Agent + +There are three ways to start an agent from Slack: + +#### 1. With a Prompt and Inline Repository + +Mention `@Continue` with your prompt and specify a repository: + +``` +@Continue repo=my-app Fix the login validation bug +``` + +The repository name should match one of your GitHub repositories that the Continue GitHub App has access to. + +#### 2. With a Prompt (Uses Default Repo) + +If you've configured a default repository, simply mention `@Continue` with your prompt: + +``` +@Continue Add unit tests for the authentication service +``` + +Continue will use your default repository automatically. + +#### 3. Without a Prompt (Interactive Selection) + +Mention `@Continue` without any prompt to get an interactive repository picker: + +``` +@Continue +``` + +Continue will show a dropdown menu of your accessible repositories. Select one to create an agent. + +### Sending Follow-up Messages + +Once an agent is created, you can send additional messages by mentioning `@Continue` in the agent's thread: + +``` +@Continue Also add error handling for edge cases +``` + +Continue will add your message to the existing agent session instead of creating a new one. + +### Restarting Shut Down Agents + +If an agent's devbox has been shut down (due to inactivity or other reasons), Continue will automatically create a replacement agent when you try to send a message: + +``` +@Continue Continue working on this +``` + +You'll see a message like "The agent is back online! 🤖" with a link to the new agent session. + +## Configuration + +### Setting a Default Repository + +Configure a default repository to streamline agent creation: + + + + Navigate to [hub.continue.dev/settings/integrations](https://hub.continue.dev/settings/integrations) + + + + Locate your connected Slack workspace in the integrations list + + + + Click "Edit" and enter the full GitHub URL of your default repository (e.g., `https://github.com/myorg/myapp`) + + + +### Using Custom Agent Files + +You can configure a default agent file that will be used for all Slack-triggered agents: + + + + Go to [hub.continue.dev/new?type=agentFile](https://hub.continue.dev/new?type=agentFile) and create your custom agent configuration + + + + In your Slack integration settings, select your agent file from the dropdown + + + +Your agent file can include: +- Custom prompts and instructions +- Specific tools and MCP servers +- Rules for code quality and style +- Model selection + +## Organization-Level Integrations + +Organization admins can set up Slack integrations at the organization level: + +1. Navigate to your organization settings: `hub.continue.dev/organizations/{org-slug}/settings/integrations` +2. Connect Slack for the organization +3. Configure default settings that apply to all organization members + +Organization-level integrations: +- Share the same default repository across the team +- Use organization-scoped agent files +- Access organization GitHub repositories +- Provide consistent agent behavior across the team + +## Help Command + +Get help and see available commands by mentioning: + +``` +@Continue /help +``` + +This will show you usage examples and available options. + +## Thread Context + +Continue automatically captures the context of your Slack thread when creating an agent. This includes: + +- Previous messages in the thread +- Any code snippets shared +- Links and attachments +- The full conversation history + +This context is passed to the agent, allowing it to understand the full scope of your request. + +## Best Practices + +### 1. Be Specific in Your Prompts + +Provide clear, detailed prompts to help Continue understand your requirements: + +✅ **Good**: `@Continue repo=api-server Fix the authentication timeout issue in /api/v1/auth/login. Users are getting logged out after 5 minutes instead of 30.` + +❌ **Poor**: `@Continue fix auth` + +### 2. Use Thread Context + +Start a conversation in a thread to provide context before requesting work: + +``` +User: I'm seeing errors in the login flow when users have special characters in their passwords +User: @Continue Investigate and fix this issue +``` + +### 3. Configure Default Repositories + +For projects you work on frequently, set a default repository to avoid specifying `repo=` every time. + +### 4. Use Agent Files for Consistency + +Create agent files with custom rules and prompts for recurring types of work. For example: +- A "code review" agent file with specific review guidelines +- A "documentation" agent file that follows your doc style guide +- A "bug fix" agent file with debugging tools and error handling patterns + +### 5. Monitor Agent Progress + +Click the agent link in Slack to view the agent's progress in Mission Control: + +``` +🤖 Agent created (view agent) +``` + +You can see: +- Current status (Planning, Working, Done) +- Files being modified +- Pull request details +- Any errors or blockers + +## Troubleshooting + +### "No accessible repositories found" + +**Problem**: You see this error when trying to start an agent. + +**Solution**: Install the Continue GitHub App and grant it access to your repositories: +1. Go to [hub.continue.dev/settings/integrations](https://hub.continue.dev/settings/integrations) +2. Connect GitHub and authorize repository access + +### "User not found" + +**Problem**: Continue can't match your Slack user to a Continue Hub account. + +**Solution**: Ensure your Slack email matches your Continue Hub account email. If you're using a different email: +1. Go to [hub.continue.dev/settings/profile](https://hub.continue.dev/settings/profile) +2. Update your email to match your Slack email +3. Or update your Slack email to match your Continue email + +### Repository Not Found + +**Problem**: When using `repo=my-repo`, Continue says the repository wasn't found. + +**Solution**: +- Verify the repository name exactly matches your GitHub repository name (case-sensitive) +- Ensure the Continue GitHub App has access to that specific repository +- Try using the interactive repository picker instead: just mention `@Continue` without specifying a repo + +### Agent Link Returns "Not Found" + +**Problem**: Clicking the agent link shows "Agent Not Available". + +**Solution**: +- The agent's devbox may have been shut down. Try mentioning `@Continue` in the same thread to create a replacement agent +- Check Mission Control at [hub.continue.dev/agents](https://hub.continue.dev/agents) to see all your agent sessions + +### Messages Not Being Delivered + +**Problem**: Continue isn't responding to your mentions. + +**Solution**: +1. Verify you're mentioning `@Continue` (not just typing "Continue") +2. Check that the Slack integration is still connected in your settings +3. Ensure you're in a channel where the Continue app has been invited +4. Try disconnecting and reconnecting the Slack integration + +## Security & Privacy + +### OAuth Scopes + +The Continue Slack app requests the following permissions: + +- `app_mentions:read` - To detect when you mention @Continue +- `chat:write` - To send messages and responses +- `users:read` - To look up user information +- `users:read.email` - To match Slack users to Continue accounts +- `channels:read` - To access channel information +- `channels:history` - To read thread context + +### Data Handling + +- **Thread content**: Captured and stored as part of agent metadata to provide context +- **Messages**: Processed in real-time; not permanently stored by the Slack integration +- **Tokens**: Encrypted and stored securely in the Continue database +- **Repository access**: Controlled by GitHub App permissions, separate from Slack + +### Disconnecting + +To remove the Slack integration: + +1. Go to [hub.continue.dev/settings/integrations](https://hub.continue.dev/settings/integrations) +2. Find your Slack integration +3. Click "Disconnect" + +This will: +- Revoke the OAuth token +- Stop Continue from accessing your Slack workspace +- Remove stored integration data + +## Advanced Features + +### Source Tracking + +Agents started from Slack are tracked with a special source identifier format: + +``` +slack:{org|user}:{slug}:{channelId}:{threadTs}:{teamId} +``` + +This allows Continue to: +- Link agents back to their originating Slack thread +- Group agents by Slack team or channel +- Provide analytics on Slack-triggered agents + +### Webhook Processing + +The Slack integration uses Slack's Events API with the following optimizations: + +- **Retry handling**: Duplicate events from Slack retries are ignored +- **Processing timeouts**: Webhook responses are sent within 3 seconds to comply with Slack's requirements +- **Background processing**: Agent creation happens asynchronously after acknowledging the webhook + +### Thread Permalinks + +Continue generates structured prompts that include a permanent link to the Slack thread, allowing the agent to reference the full conversation context if needed. + +## Feedback & Support + +The Slack integration is in active development. We'd love to hear your feedback: + +- Report issues: [GitHub Issues](https://github.com/continuedev/continue/issues) +- Feature requests: [GitHub Discussions](https://github.com/continuedev/continue/discussions) +- Questions: Join our [Discord community](https://discord.gg/continue) + +## Related Resources + +- [Agents Introduction](./intro) - Learn about Continue agents +- [CLI Guide](../../guides/cli) - Use Continue from the command line +- [Continuous AI](../../guides/continuous-ai) - Best practices for background agents +- [GitHub PR Review Bot](../../guides/github-pr-review-bot) - Automate code reviews From 6aae22ae6114dba4c6e2e4451e5fb3438388c3c5 Mon Sep 17 00:00:00 2001 From: Dallin Romney Date: Sat, 1 Nov 2025 22:45:33 -0700 Subject: [PATCH 02/11] fix: slack integration docs touch up --- docs/hub/agents/slack-integration.mdx | 314 ++++---------------------- 1 file changed, 38 insertions(+), 276 deletions(-) diff --git a/docs/hub/agents/slack-integration.mdx b/docs/hub/agents/slack-integration.mdx index 32087c267a6..b35d759cb76 100644 --- a/docs/hub/agents/slack-integration.mdx +++ b/docs/hub/agents/slack-integration.mdx @@ -9,282 +9,76 @@ description: "Trigger agents from Slack by mentioning @Continue" ## Overview -The Continue Slack integration enables you to: - -- **Start agents** by mentioning `@Continue` in any Slack channel -- **Send follow-up messages** to existing agents by mentioning `@Continue` in the agent's thread -- **Select repositories** interactively when starting an agent -- **Configure default repositories** to streamline agent creation -- **Use agent files** to customize behavior with specific prompts, tools, and rules +Continue brings AI-powered development agents to your Slack workspace. 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 + +The Slack bot is great for: +- Quick bug fixes and feature implementations +- Code reviews and refactoring +- Documentation updates +- Automated development tasks ## Setup -### 1. Install the Slack App - - - - Go to [hub.continue.dev/settings/integrations](https://hub.continue.dev/settings/integrations) - - - - Click the "Connect" button next to Slack and authorize the app in your workspace - - - - After authorization, you'll be redirected back to Continue Hub with a success message - - +Continue's Slack Bot can be installed to a Slack workspace via the Hub, from: +- [Personal Integrations Settings](https://hub.continue.dev/settings/integrations) or +- Org Integrations Settings - `https://hub.continue.dev/organizations/{your-org-slug}/settings/integrations` -### 2. Connect GitHub - -Before using the Slack integration, ensure you have the Continue GitHub App installed: - -1. Go to [hub.continue.dev/settings/integrations](https://hub.continue.dev/settings/integrations) -2. Click "Connect" next to GitHub -3. Grant access to the repositories you want Continue to work with +1. First, connect Github by clicking "Connect" next to GitHub in the Integrations settings, and granting access to the repositories you want Continue to work with +2. Click the "Connect" button next to Slack and authorize the app in your workspace +3. Optionally, use the repository selector within the Slack tile to select a default repo for Continue Agents to work in ## Usage ### Starting an Agent -There are three ways to start an agent from Slack: +To kick off an agent, mention `@Continue` with a description of what needs to be done. -#### 1. With a Prompt and Inline Repository +Provide clear, detailed prompts to help Continue understand your requirements: -Mention `@Continue` with your prompt and specify a repository: +✅ **Good**: `@Continue Fix the authentication timeout issue in /api/v1/auth/login. Users are getting logged out after 5 minutes instead of 30.` -``` -@Continue repo=my-app Fix the login validation bug -``` - -The repository name should match one of your GitHub repositories that the Continue GitHub App has access to. +❌ **Poor**: `@Continue fix auth` -#### 2. With a Prompt (Uses Default Repo) +#### Agent context -If you've configured a default repository, simply mention `@Continue` with your prompt: +Continue captures the context of your Slack thread when creating an agent. If mentioned directly in a channel, it will respond in the thread and not have context other than the first message. -``` -@Continue Add unit tests for the authentication service -``` +The agent can also use a Slack MCP to dynamically send updates and retrieve more context if needed. -Continue will use your default repository automatically. +#### Repo selection -#### 3. Without a Prompt (Interactive Selection) - -Mention `@Continue` without any prompt to get an interactive repository picker: +Continue determines which repo to work in with the following precedence: +1. You can specify a repository to work in by adding `repo=repo-name` to your message. The repository name should match one of your GitHub repositories that the Continue GitHub App has access to. ``` -@Continue +@Continue repo=my-app Fix the login validation bug ``` -Continue will show a dropdown menu of your accessible repositories. Select one to create an agent. +2. A default repo, if set in the integration settings + +3. Otherwise, it will follow up with a dropdown to select a repository to work in. ### Sending Follow-up Messages -Once an agent is created, you can send additional messages by mentioning `@Continue` in the agent's thread: +Once an agent is created, you can send additional messages by mentioning `@Continue` in the same thread: ``` @Continue Also add error handling for edge cases ``` -Continue will add your message to the existing agent session instead of creating a new one. - -### Restarting Shut Down Agents - -If an agent's devbox has been shut down (due to inactivity or other reasons), Continue will automatically create a replacement agent when you try to send a message: - -``` -@Continue Continue working on this -``` - -You'll see a message like "The agent is back online! 🤖" with a link to the new agent session. - -## Configuration - -### Setting a Default Repository - -Configure a default repository to streamline agent creation: - - - - Navigate to [hub.continue.dev/settings/integrations](https://hub.continue.dev/settings/integrations) - - - - Locate your connected Slack workspace in the integrations list - - - - Click "Edit" and enter the full GitHub URL of your default repository (e.g., `https://github.com/myorg/myapp`) - - - -### Using Custom Agent Files - -You can configure a default agent file that will be used for all Slack-triggered agents: - - - - Go to [hub.continue.dev/new?type=agentFile](https://hub.continue.dev/new?type=agentFile) and create your custom agent configuration - - - - In your Slack integration settings, select your agent file from the dropdown - - - -Your agent file can include: -- Custom prompts and instructions -- Specific tools and MCP servers -- Rules for code quality and style -- Model selection - -## Organization-Level Integrations - -Organization admins can set up Slack integrations at the organization level: - -1. Navigate to your organization settings: `hub.continue.dev/organizations/{org-slug}/settings/integrations` -2. Connect Slack for the organization -3. Configure default settings that apply to all organization members - -Organization-level integrations: -- Share the same default repository across the team -- Use organization-scoped agent files -- Access organization GitHub repositories -- Provide consistent agent behavior across the team - -## Help Command - -Get help and see available commands by mentioning: - -``` -@Continue /help -``` - -This will show you usage examples and available options. - -## Thread Context - -Continue automatically captures the context of your Slack thread when creating an agent. This includes: - -- Previous messages in the thread -- Any code snippets shared -- Links and attachments -- The full conversation history - -This context is passed to the agent, allowing it to understand the full scope of your request. +Continue will forward your message to the existing agent session instead of creating a new one. For older threads, with no running agent, a new agent will be created. -## Best Practices +## Monitoring Agent Progress -### 1. Be Specific in Your Prompts +Click the agent link in Slack to view the agent's progress in [Mission Control](https://hub.continue.dev/agents). -Provide clear, detailed prompts to help Continue understand your requirements: - -✅ **Good**: `@Continue repo=api-server Fix the authentication timeout issue in /api/v1/auth/login. Users are getting logged out after 5 minutes instead of 30.` - -❌ **Poor**: `@Continue fix auth` - -### 2. Use Thread Context +You can also click the Slack icon in the agents page to return to the Slack message. -Start a conversation in a thread to provide context before requesting work: - -``` -User: I'm seeing errors in the login flow when users have special characters in their passwords -User: @Continue Investigate and fix this issue -``` - -### 3. Configure Default Repositories - -For projects you work on frequently, set a default repository to avoid specifying `repo=` every time. - -### 4. Use Agent Files for Consistency - -Create agent files with custom rules and prompts for recurring types of work. For example: -- A "code review" agent file with specific review guidelines -- A "documentation" agent file that follows your doc style guide -- A "bug fix" agent file with debugging tools and error handling patterns - -### 5. Monitor Agent Progress - -Click the agent link in Slack to view the agent's progress in Mission Control: - -``` -🤖 Agent created (view agent) -``` - -You can see: -- Current status (Planning, Working, Done) -- Files being modified -- Pull request details -- Any errors or blockers - -## Troubleshooting - -### "No accessible repositories found" - -**Problem**: You see this error when trying to start an agent. - -**Solution**: Install the Continue GitHub App and grant it access to your repositories: -1. Go to [hub.continue.dev/settings/integrations](https://hub.continue.dev/settings/integrations) -2. Connect GitHub and authorize repository access - -### "User not found" - -**Problem**: Continue can't match your Slack user to a Continue Hub account. - -**Solution**: Ensure your Slack email matches your Continue Hub account email. If you're using a different email: -1. Go to [hub.continue.dev/settings/profile](https://hub.continue.dev/settings/profile) -2. Update your email to match your Slack email -3. Or update your Slack email to match your Continue email - -### Repository Not Found - -**Problem**: When using `repo=my-repo`, Continue says the repository wasn't found. - -**Solution**: -- Verify the repository name exactly matches your GitHub repository name (case-sensitive) -- Ensure the Continue GitHub App has access to that specific repository -- Try using the interactive repository picker instead: just mention `@Continue` without specifying a repo - -### Agent Link Returns "Not Found" - -**Problem**: Clicking the agent link shows "Agent Not Available". - -**Solution**: -- The agent's devbox may have been shut down. Try mentioning `@Continue` in the same thread to create a replacement agent -- Check Mission Control at [hub.continue.dev/agents](https://hub.continue.dev/agents) to see all your agent sessions - -### Messages Not Being Delivered - -**Problem**: Continue isn't responding to your mentions. - -**Solution**: -1. Verify you're mentioning `@Continue` (not just typing "Continue") -2. Check that the Slack integration is still connected in your settings -3. Ensure you're in a channel where the Continue app has been invited -4. Try disconnecting and reconnecting the Slack integration - -## Security & Privacy - -### OAuth Scopes - -The Continue Slack app requests the following permissions: - -- `app_mentions:read` - To detect when you mention @Continue -- `chat:write` - To send messages and responses -- `users:read` - To look up user information -- `users:read.email` - To match Slack users to Continue accounts -- `channels:read` - To access channel information -- `channels:history` - To read thread context - -### Data Handling - -- **Thread content**: Captured and stored as part of agent metadata to provide context -- **Messages**: Processed in real-time; not permanently stored by the Slack integration -- **Tokens**: Encrypted and stored securely in the Continue database -- **Repository access**: Controlled by GitHub App permissions, separate from Slack - -### Disconnecting +## Disconnecting To remove the Slack integration: @@ -292,39 +86,7 @@ To remove the Slack integration: 2. Find your Slack integration 3. Click "Disconnect" -This will: -- Revoke the OAuth token -- Stop Continue from accessing your Slack workspace -- Remove stored integration data - -## Advanced Features - -### Source Tracking - -Agents started from Slack are tracked with a special source identifier format: - -``` -slack:{org|user}:{slug}:{channelId}:{threadTs}:{teamId} -``` - -This allows Continue to: -- Link agents back to their originating Slack thread -- Group agents by Slack team or channel -- Provide analytics on Slack-triggered agents - -### Webhook Processing - -The Slack integration uses Slack's Events API with the following optimizations: - -- **Retry handling**: Duplicate events from Slack retries are ignored -- **Processing timeouts**: Webhook responses are sent within 3 seconds to comply with Slack's requirements -- **Background processing**: Agent creation happens asynchronously after acknowledging the webhook - -### Thread Permalinks - -Continue generates structured prompts that include a permanent link to the Slack thread, allowing the agent to reference the full conversation context if needed. - -## Feedback & Support +## Support The Slack integration is in active development. We'd love to hear your feedback: From 4753fa7c9f7237af224846d35d1e106f28dc917c Mon Sep 17 00:00:00 2001 From: BekahHW Date: Mon, 3 Nov 2025 13:43:32 -0500 Subject: [PATCH 03/11] Remove discord link --- docs/hub/agents/slack-integration.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/hub/agents/slack-integration.mdx b/docs/hub/agents/slack-integration.mdx index b35d759cb76..aae0f342e2b 100644 --- a/docs/hub/agents/slack-integration.mdx +++ b/docs/hub/agents/slack-integration.mdx @@ -92,7 +92,6 @@ The Slack integration is in active development. We'd love to hear your feedback: - Report issues: [GitHub Issues](https://github.com/continuedev/continue/issues) - Feature requests: [GitHub Discussions](https://github.com/continuedev/continue/discussions) -- Questions: Join our [Discord community](https://discord.gg/continue) ## Related Resources From aa6751e7637a2cd9008df156432d957e245b3ed1 Mon Sep 17 00:00:00 2001 From: BekahHW Date: Mon, 3 Nov 2025 14:26:32 -0500 Subject: [PATCH 04/11] Updated sentence structure. and added mintlify elements --- docs/hub/agents/slack-integration.mdx | 121 +++++++++++++++++++------- 1 file changed, 91 insertions(+), 30 deletions(-) diff --git a/docs/hub/agents/slack-integration.mdx b/docs/hub/agents/slack-integration.mdx index aae0f342e2b..3eab183eecd 100644 --- a/docs/hub/agents/slack-integration.mdx +++ b/docs/hub/agents/slack-integration.mdx @@ -4,32 +4,58 @@ description: "Trigger agents from Slack by mentioning @Continue" --- - The Slack integration allows you to start and manage Continue agents directly from your Slack workspace. This is currently in beta. + + The Slack integration allows you to start and manage Continue agents directly from your Slack workspace. This feature is currently in beta. + ## Overview Continue brings AI-powered development agents to your Slack workspace. 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 -The Slack bot is great for: -- Quick bug fixes and feature implementations -- Code reviews and refactoring -- Documentation updates -- Automated development tasks + + + The Slack bot is great for: + - Quick bug fixes and feature implementations + - Code reviews and refactoring + - Documentation updates + - Automated development tasks + + ## Setup Continue's Slack Bot can be installed to a Slack workspace via the Hub, from: + - [Personal Integrations Settings](https://hub.continue.dev/settings/integrations) or - Org Integrations Settings - `https://hub.continue.dev/organizations/{your-org-slug}/settings/integrations` -1. First, connect Github by clicking "Connect" next to GitHub in the Integrations settings, and granting access to the repositories you want Continue to work with -2. Click the "Connect" button next to Slack and authorize the app in your workspace -3. Optionally, use the repository selector within the Slack tile to select a default repo for Continue Agents to work in + + + + + 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 to Slack and authorize the app in your workspace. + + + + + + Use the repository selector within the Slack tile to select a default repo for Continue Agents to work in. + + + + ## Usage @@ -37,30 +63,39 @@ Continue's Slack Bot can be installed to a Slack workspace via the Hub, from: To kick off an agent, mention `@Continue` with a description of what needs to be done. -Provide clear, detailed prompts to help Continue understand your requirements: + -✅ **Good**: `@Continue Fix the authentication timeout issue in /api/v1/auth/login. Users are getting logged out after 5 minutes instead of 30.` + Provide clear, detailed prompts to help Continue understand your requirements: -❌ **Poor**: `@Continue fix auth` + ✅ **Good**: `@Continue Fix the authentication timeout issue in /api/v1/auth/login. Users are getting logged out after 5 minutes instead of 30.` -#### Agent context + ❌ **Poor**: `@Continue fix auth` -Continue captures the context of your Slack thread when creating an agent. If mentioned directly in a channel, it will respond in the thread and not have context other than the first message. + -The agent can also use a Slack MCP to dynamically send updates and retrieve more context if needed. + -#### Repo selection + Continue captures the context of your Slack thread when creating an agent. If mentioned directly in a channel, it will respond in the thread and not have context other than the first message. -Continue determines which repo to work in with the following precedence: -1. You can specify a repository to work in by adding `repo=repo-name` to your message. The repository name should match one of your GitHub repositories that the Continue GitHub App has access to. + The agent can also use a Slack MCP to dynamically send updates and retrieve more context if needed. -``` -@Continue repo=my-app Fix the login validation bug -``` + + + -2. A default repo, if set in the integration settings + Continue determines which repo to work in with the following precedence: -3. Otherwise, it will follow up with a dropdown to select a repository to work in. + 1. **Specify in message**: Add `repo=repo-name` to your message. The repository name should match one of your GitHub repositories that the Continue GitHub App has access to. + + ``` + @Continue repo=my-app Fix the login validation bug + ``` + + 2. **Default repo**: Uses the default repo if set in the integration settings + + 3. **Interactive selection**: Continue will follow up with a dropdown to select a repository + + ### Sending Follow-up Messages @@ -88,14 +123,40 @@ To remove the Slack integration: ## Support -The Slack integration is in active development. We'd love to hear your feedback: + + + The Slack integration is in active development. We'd love to hear your feedback: + - Report issues: [GitHub Issues](https://github.com/continuedev/continue/issues) + - Feature requests: [GitHub Discussions](https://github.com/continuedev/continue/discussions) -- Report issues: [GitHub Issues](https://github.com/continuedev/continue/issues) -- Feature requests: [GitHub Discussions](https://github.com/continuedev/continue/discussions) + ## Related Resources -- [Agents Introduction](./intro) - Learn about Continue agents -- [CLI Guide](../../guides/cli) - Use Continue from the command line -- [Continuous AI](../../guides/continuous-ai) - Best practices for background agents -- [GitHub PR Review Bot](../../guides/github-pr-review-bot) - Automate code reviews + + + + + Learn about Continue agents + + + + + + Use Continue from the command line + + + + + + Best practices for background agents + + + + + + Automate code reviews + + + + From 5610a091cfc2f4768fde5d30b4dce73533252b4f Mon Sep 17 00:00:00 2001 From: BekahHW Date: Mon, 3 Nov 2025 14:36:05 -0500 Subject: [PATCH 05/11] Clean up formatting --- docs/hub/agents/slack-integration.mdx | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/docs/hub/agents/slack-integration.mdx b/docs/hub/agents/slack-integration.mdx index 3eab183eecd..c1550f23719 100644 --- a/docs/hub/agents/slack-integration.mdx +++ b/docs/hub/agents/slack-integration.mdx @@ -5,34 +5,33 @@ description: "Trigger agents from Slack by mentioning @Continue" - The Slack integration allows you to start and manage Continue agents directly from your Slack workspace. This feature is currently in beta. + Continue's Slack Agent allows you to start and manage Continue agents directly from your Slack workspace. When you summon @Continue inside an ongoing Slack thread, it automatically uses the entire conversation as context, so your agent starts with full situational awareness. This feature is currently in beta. ## Overview -Continue brings AI-powered development agents to your Slack workspace. Mention @Continue in any channel with a task description, and it will: +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 - + - The Slack bot is great for: - - Quick bug fixes and feature implementations - - Code reviews and refactoring - - Documentation updates - - Automated development tasks - +- Quick bug fixes and feature implementations +- Code reviews and refactoring +- Documentation updates +- Automated development tasks + ## Setup Continue's Slack Bot can be installed to a Slack workspace via the Hub, from: -- [Personal Integrations Settings](https://hub.continue.dev/settings/integrations) or +- [Personal Integrations Settings](https://hub.continue.dev/settings/integrations) - Org Integrations Settings - `https://hub.continue.dev/organizations/{your-org-slug}/settings/integrations` @@ -51,7 +50,7 @@ Continue's Slack Bot can be installed to a Slack workspace via the Hub, from: - Use the repository selector within the Slack tile to select a default repo for Continue Agents to work in. + Use the repository selector within the Slack tile to select a default repository for Continue Agents to work in. From bd163623cf02cb1935001bb941b89fa4f5a2673d Mon Sep 17 00:00:00 2001 From: BekahHW Date: Mon, 3 Nov 2025 18:28:56 -0500 Subject: [PATCH 06/11] Refine info messaging --- docs/hub/agents/slack-integration.mdx | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/hub/agents/slack-integration.mdx b/docs/hub/agents/slack-integration.mdx index c1550f23719..defc6e9db24 100644 --- a/docs/hub/agents/slack-integration.mdx +++ b/docs/hub/agents/slack-integration.mdx @@ -5,7 +5,7 @@ description: "Trigger agents from Slack by mentioning @Continue" - Continue's Slack Agent allows you to start and manage Continue agents directly from your Slack workspace. When you summon @Continue inside an ongoing Slack thread, it automatically uses the entire conversation as context, so your agent starts with full situational awareness. This feature is currently in beta. + Continue's Slack integration allows you to start and manage Continue agents directly from your Slack workspace. All you need is a Continue account that's connected to GitHub. This feature is currently in beta. @@ -27,6 +27,7 @@ Mention @Continue in any channel with a task description, and it will: - Automated development tasks + ## Setup Continue's Slack Bot can be installed to a Slack workspace via the Hub, from: @@ -62,6 +63,12 @@ Continue's Slack Bot can be installed to a Slack workspace via the Hub, from: To kick off an agent, mention `@Continue` with a description of what needs to be done. + + + **Thread Context**: When you mention @Continue in an ongoing Slack thread, it automatically uses the entire conversation as context, giving your agent full situational awareness. + + + Provide clear, detailed prompts to help Continue understand your requirements: @@ -72,7 +79,7 @@ To kick off an agent, mention `@Continue` with a description of what needs to be - + Continue captures the context of your Slack thread when creating an agent. If mentioned directly in a channel, it will respond in the thread and not have context other than the first message. From 832c8a2a562086d4203c768fc5aea18d2f5e0e29 Mon Sep 17 00:00:00 2001 From: BekahHW Date: Mon, 3 Nov 2025 18:45:53 -0500 Subject: [PATCH 07/11] Reorganize info and cut down on mintlify components --- docs/hub/agents/slack-integration.mdx | 30 ++++++++++++--------------- 1 file changed, 13 insertions(+), 17 deletions(-) diff --git a/docs/hub/agents/slack-integration.mdx b/docs/hub/agents/slack-integration.mdx index defc6e9db24..4bc947a9a88 100644 --- a/docs/hub/agents/slack-integration.mdx +++ b/docs/hub/agents/slack-integration.mdx @@ -59,15 +59,14 @@ Continue's Slack Bot can be installed to a Slack workspace via the Hub, from: ## Usage -### Starting an Agent +To kick off an agent, mention `@Continue` with a short task description. -To kick off an agent, mention `@Continue` with a description of what needs to be done. +### Thread Context - - - **Thread Context**: When you mention @Continue in an ongoing Slack thread, it automatically uses the entire conversation as context, giving your agent full situational awareness. +When you mention `@Continue` in a **Slack thread**, Continue automatically uses the entire conversation as context. This means your agent starts with full situational awareness. - +If you start a **new message** (not a reply), Continue only sees that single message for context. +Use this for quick standalone requests. @@ -79,27 +78,24 @@ To kick off an agent, mention `@Continue` with a description of what needs to be - - - Continue captures the context of your Slack thread when creating an agent. If mentioned directly in a channel, it will respond in the thread and not have context other than the first message. - - The agent can also use a Slack MCP to dynamically send updates and retrieve more context if needed. - - - Continue determines which repo to work in with the following precedence: - 1. **Specify in message**: Add `repo=repo-name` to your message. The repository name should match one of your GitHub repositories that the Continue GitHub App has access to. + 1. **Specify in message**: Add `repo=repo-name` to your message: ``` @Continue repo=my-app Fix the login validation bug ``` - 2. **Default repo**: Uses the default repo if set in the integration settings + + Be sure the repository name matches a GitHub repository that the Continue GitHub App has access to. + + + + 2. **Default repo**: Uses the default repository if set in the integration settings - 3. **Interactive selection**: Continue will follow up with a dropdown to select a repository + 3. **Interactive selection**: If no repository is found, Continue will follow up with a dropdown to select a repository From 06e74880a1f485a82e5395df83823589735730cb Mon Sep 17 00:00:00 2001 From: BekahHW Date: Mon, 3 Nov 2025 18:49:01 -0500 Subject: [PATCH 08/11] Update description --- docs/hub/agents/slack-integration.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/hub/agents/slack-integration.mdx b/docs/hub/agents/slack-integration.mdx index 4bc947a9a88..02e2413edb4 100644 --- a/docs/hub/agents/slack-integration.mdx +++ b/docs/hub/agents/slack-integration.mdx @@ -1,6 +1,6 @@ --- title: "Slack Integration" -description: "Trigger agents from Slack by mentioning @Continue" +description: "Bring Continue’s AI agents into Slack. Mention @Continue in any channel or thread to trigger development workflows, generate PRs, or update docs all with the context of your conversation." --- @@ -80,7 +80,7 @@ Use this for quick standalone requests. - Continue determines which repo to work in with the following precedence: + Continue determines which repository to work in with the following precedence: 1. **Specify in message**: Add `repo=repo-name` to your message: @@ -107,7 +107,7 @@ Once an agent is created, you can send additional messages by mentioning `@Conti @Continue Also add error handling for edge cases ``` -Continue will forward your message to the existing agent session instead of creating a new one. For older threads, with no running agent, a new agent will be created. +Continue will forward your message to the existing agent session instead of creating a new one. For older threads with no running agent, a new agent will be created. ## Monitoring Agent Progress From e464d326dd59e9e0b6d24ce9d18ba0d9827baeb9 Mon Sep 17 00:00:00 2001 From: BekahHW Date: Mon, 3 Nov 2025 18:50:27 -0500 Subject: [PATCH 09/11] Remove line for clarity --- docs/hub/agents/slack-integration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/hub/agents/slack-integration.mdx b/docs/hub/agents/slack-integration.mdx index 02e2413edb4..40674b28808 100644 --- a/docs/hub/agents/slack-integration.mdx +++ b/docs/hub/agents/slack-integration.mdx @@ -107,7 +107,7 @@ Once an agent is created, you can send additional messages by mentioning `@Conti @Continue Also add error handling for edge cases ``` -Continue will forward your message to the existing agent session instead of creating a new one. For older threads with no running agent, a new agent will be created. +Continue will forward your message to the existing agent session instead of creating a new one. ## Monitoring Agent Progress From 3c99f0d2b481f4888c3c19f11fa535fc36b8ccd2 Mon Sep 17 00:00:00 2001 From: Dallin Romney Date: Thu, 6 Nov 2025 11:52:22 -0800 Subject: [PATCH 10/11] fix: ty feedback for slack docs --- docs/docs.json | 2 +- .../{slack-integration.mdx => slack-agent.mdx} | 18 +++++++++--------- 2 files changed, 10 insertions(+), 10 deletions(-) rename docs/hub/agents/{slack-integration.mdx => slack-agent.mdx} (89%) diff --git a/docs/docs.json b/docs/docs.json index 2868c5f1256..1fc5a2017cf 100644 --- a/docs/docs.json +++ b/docs/docs.json @@ -57,7 +57,7 @@ { "group": "Agents", "icon": "cloud", - "pages": ["hub/agents/intro", "hub/agents/slack-integration"] + "pages": ["hub/agents/intro", "hub/agents/slack-agent"] }, "hub/sharing", "hub/source-control" diff --git a/docs/hub/agents/slack-integration.mdx b/docs/hub/agents/slack-agent.mdx similarity index 89% rename from docs/hub/agents/slack-integration.mdx rename to docs/hub/agents/slack-agent.mdx index 40674b28808..89d3ccb8da7 100644 --- a/docs/hub/agents/slack-integration.mdx +++ b/docs/hub/agents/slack-agent.mdx @@ -1,6 +1,6 @@ --- -title: "Slack Integration" -description: "Bring Continue’s AI agents into Slack. Mention @Continue in any channel or thread to trigger development workflows, generate PRs, or update docs all with the context of your conversation." +title: "Slack Agent" +description: "Bring Continue's AI agents into Slack. Mention @Continue in any channel or thread to trigger development workflows, generate PRs, or update docs all with the context of your conversation." --- @@ -20,11 +20,10 @@ Mention @Continue in any channel with a task description, and it will: - -- Quick bug fixes and feature implementations -- Code reviews and refactoring -- Documentation updates -- Automated development tasks + - Quick bug fixes and feature implementations + - Code reviews and refactoring + - Documentation updates + - Automated development tasks @@ -89,9 +88,10 @@ Use this for quick standalone requests. ``` - Be sure the repository name matches a GitHub repository that the Continue GitHub App has access to. + + Be sure the repository name matches a GitHub repository that the Continue GitHub App has access to. + - 2. **Default repo**: Uses the default repository if set in the integration settings From ec6c6a2cb108cf1d60438671494d0b891c2bd6e1 Mon Sep 17 00:00:00 2001 From: Dallin Romney Date: Thu, 6 Nov 2025 12:08:12 -0800 Subject: [PATCH 11/11] fix: slack agent docs --- docs/hub/agents/slack-agent.mdx | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/docs/hub/agents/slack-agent.mdx b/docs/hub/agents/slack-agent.mdx index 89d3ccb8da7..f515c23b8a1 100644 --- a/docs/hub/agents/slack-agent.mdx +++ b/docs/hub/agents/slack-agent.mdx @@ -1,13 +1,13 @@ --- title: "Slack Agent" -description: "Bring Continue's AI agents into Slack. Mention @Continue in any channel or thread to trigger development workflows, generate PRs, or update docs all with the context of your conversation." +description: "Kick off background Agents from Slack by mentioning @Continue" --- - + - Continue's Slack integration allows you to start and manage Continue agents directly from your Slack workspace. All you need is a Continue account that's connected to GitHub. This feature is currently in beta. + The Continue Slack app is currently in beta development and undergoing Slack's approval process. - + ## Overview @@ -32,7 +32,13 @@ Mention @Continue in any channel with a task description, and it will: Continue's Slack Bot can be installed to a Slack workspace via the Hub, from: - [Personal Integrations Settings](https://hub.continue.dev/settings/integrations) -- Org Integrations Settings - `https://hub.continue.dev/organizations/{your-org-slug}/settings/integrations` +- Org Integrations Settings - `https://hub.continue.dev/organizations/{your-org}/settings/integrations` + + + + Continue's Slack app is in Beta development. During installation, you will see a warning that it is not yet approved/official. + +