Slack

Tag @Devin in Slack as soon as bugs, feature requests, and questions come in. Devin responds in-thread with updates and questions when it’s tagged.

​

Get started

​

Installation

1. Go to Settings > Connections > Slack
2. Click “Connect”
3. You’ll be prompted to install the Devin app for Slack in your workspace
4. Make sure to link your individual user. All users in your organization will need to complete this step to use Devin.
5. Tag @Devin in Slack to start a session

Note: If your user account is not properly connecting, ensure that your Slack email is the same as your email in https://app.devin.ai/settings. If not, please authenticate the correct email on Slack.

​

How to use Devin from Slack

Once you’ve installed the Devin integration for Slack, simply trigger Devin with @Devin in any channel. You may include attachments to your message. Devin will respond in-thread to your session. Now, you can communicate back and forth as you would in the regular chat interface. Note that Devin may make mistakes. Please double-check responses.

​

Inline Slack Keywords & Functions

​

Slash commands

Run either command with no arguments (or with help) to get usage instructions back privately.

​

Message shortcuts

Right-click (or use the ⋮ overflow menu on) any Slack message to act on it without retyping it:

• Ask Devin about this — uses the message as the question for a quick codebase answer, same as /ask-devin.
• Create a new session — opens a modal pre-filled with the message text, where you pick the channel to post the session in, optionally attach a playbook, and edit the prompt before submitting.

​

Sync sessions with Slack threads

Sessions can sync bidirectionally with a Slack thread: messages you send in the webapp appear in the thread, and replies in the thread reach Devin. This means you can start a session anywhere and keep your team in the loop.

• Use the Slack toggle in the session composer to turn sync on or off for that session. The icon is colored when synced and greyed out when not.
• The first time you sync to a channel, Devin offers to make it your default so new sessions sync there automatically.
• Send unsync (or !unsync) in a synced thread to immediately stop syncing that session. Toggle sync back on in the webapp to resume.

A couple of related behaviors:

• Mentioning @Devin in the thread of an archived session unarchives it so you can continue the conversation.
• When Devin suggests an environment configuration change, the Slack message includes the proposed diff and an Apply button so you can accept it without leaving Slack.

​

Code channels

A code channel is a Slack channel dedicated to a single Devin session. Instead of following the run in a thread, you get a channel whose name tracks the session title, a status chip showing whether Devin is working / blocked / done, a link back to the session in the webapp, chips and tabs for the pull requests it opens, and a live worklog of the thoughts and tool calls behind each message. Every message you send in the channel goes to that session — no @Devin mention needed. There are two ways a session ends up in a code channel:

• Start it there with !new. @Devin !new <task> creates the channel and runs the session in it from the beginning. A !new from inside a code channel spawns a separate sibling channel for the new session.
• Let Devin move the conversation. When a thread conversation turns into real work, Devin can move the session into a code channel itself. The original thread keeps its history and gets a “This session moved to #channel” notice; the session continues in the new channel, and further replies in the old thread no longer reach it. Devin won’t move a session whose Slack sync you turned off (see Sync sessions with Slack threads).

You can also create the channel from Slack’s own affordance on a message. The first message in an empty code channel becomes the task that starts the session — and if Devin isn’t a member of the conversation the channel was spawned from, it says so in the channel, since the quoted message is all the context it has.

​

Automations triggered from Slack

Automations can be triggered by Slack activity — for example a reaction added to a message, or Devin monitoring a channel and jumping in when it can help — and can post run results back to a channel you designate. See the Automations guide for setup.

​

Turn on Slack Notifications

You can enable Slack notifications for specific runs and Devin will privately message you whenever there’s a status update. To do so, simply click “Enable Slack notifications” in the menu at the top of any run.

​

Dedicated Devin channel

Set up a #devin-runs channel (or similar) to keep all Devin conversations in one place. This helps your team collaborate on Devin runs together and draw inspiration for different use cases from each other.

​

How to Rename Devin

You may change Devin’s name in your Slack workspace by going to your Slack Workspace Admin panel -> Configure apps -> Installed Apps -> Devin. Then click on App Details, and go to the Configuration tab of that page. If you scroll down you will find a section called ‘Bot User’ where you may change Devin’s name.

​

Pricing

If you don’t yet have a Devin account, you can learn more about pricing and plans here.

​

Privacy

Our privacy policy is available here.

​

Permissions Details