Slack
Connect Factory to Slack and delegate work from channels and direct messages using your organization's Agent Profile.
Mention @Factory in a Slack channel or send Factory a direct message to have Droid investigate, implement, and test work on a remote computer. Droid posts progress and results in the same conversation.
Channel requests run as one of your organization's Agent Profiles. Unless a custom profile is assigned to Slack for you, that profile is Org Default. Direct messages use your personal identity and connectors.
This page covers the Factory Slack app. A personal Slack connector gives Droid tools to use inside sessions; it does not install the app in your workspace.
If an existing Factory Slack install lacks permission to read images or upload files, rerun its authorization flow to enable those capabilities. A Slack admin may need to approve the updated permissions.
Prerequisites
To install the Factory Slack app and configure Slack delegation, you need:
- A Factory organization on any paid plan, including individual plans and organization plans.
- The Manager or Owner role in Factory.
- Admin access to your Slack workspace and permission to install apps in it.
- Access to Settings → Delegations in Factory.
- The Org Default Agent Profile, with the Git credentials and connectors shared channel work needs, and an Environment for Dynamic compute or its own computers for Persistent compute.
Each team member who delegates work must have a Factory account in the connected organization. Their Slack account email must match their Factory account email.
Set up the Org Default Agent Profile
Before you connect Slack, a Manager or Owner sets up your organization's Org Default Agent Profile. It sets the model, instructions, plugins, compute, Git credentials, and connectors Slack delegations use. Follow configure an Agent Profile, and make sure the profile has repository access for the work. Until Org Default is saved for the first time, Factory asks you to set it up when you connect an app.
Channel delegations run as the Agent Profile, with its Git credentials and connectors. Personal DMs don't. Org Default serves everyone no custom profile serves on every delegation app, so changes can affect more than Slack.
To route some people to a different setup, a Manager or Owner can assign custom Agent Profiles to Slack: in Settings → Delegations, open Slack's ... menu and choose Assign agent profiles. Each mention runs on the first assigned profile the requester has access to, or Org Default. See assign profiles to delegation apps. Slack automations do not use these assignments.
Connect Slack
- 1Open Slack delegation settings
Open Settings → Delegations. Under Delegation Apps, find Slack and select Set Up for Org, or Configure if it is already connected.
- 2Connect or reconnect Slack
On the Slack setup page, click Connect. For an existing installation, click Manage, then Reconnect to refresh its permissions.
- 3Authorize Factory's Slack app
You'll be redirected to Slack. Review the requested permissions and click "Allow" to authorize Factory access to your Slack workspace. If you belong to multiple workspaces, select the workspace you want to connect.
- 4Confirm the integration
After authorization, you'll be redirected back to Factory. Verify that the integration status shows as "Connected".
- 5Add Factory to channels
Factory must be a member of a channel to respond there. Run
/invite @Factoryin the channel, or accept Slack's prompt to add Factory the first time you mention it.
Delegate and follow up
Mention @Factory in a thread in a channel where the app has been invited, or send the app a direct message. Include the repository, desired outcome, and how Droid should verify the result:
@Factory Investigate the failing checkout test in the storefront repository. Fix the cause, run the relevant tests, and open a pull request with a summary of the change.
Droid runs the work with the identity appropriate to the conversation. Review its response and any linked pull request. Slack links to the session whenever you can open it, including channel delegations that run as the Agent Profile. Continue with follow-up instructions in the same Slack conversation, or in the code channel if Droid opened one. Check the test results and proposed changes before merging.
In Slack, Droid can:
- Use the full thread as context when you mention it in a thread.
- Use supported image attachments from Slack as context.
- Post messages, generated files, artifacts, and result videos back to Slack.
- Receive follow-up messages and attachments from Slack in an active session.
- Handle CI in a subagent when it creates a pull request, so it can respond faster.
The session's model comes from the Agent Profile that serves you, or from your personal delegation defaults when organization policy allows it. You can also reference a Slack thread in any Factory chat by pasting its URL.
Code channels
A code channel is a Slack channel dedicated to one Factory session. Instead of following the work in a thread, your team gets a channel for the task. Factory posts its updates there, and the channel shows the repository and branch Factory is working on and a diff of its changes.
Code channels are available for delegated sessions that a person starts. Automation and Incident Response runs stay in their thread. Code channels also depend on Slack's own code channels feature. If your workspace does not have it yet, or your Factory Slack app was installed before code channels were available, sessions stay in the thread. To grant the code channels permission to an existing installation, reconnect the app using the connection steps.
A session moves into a code channel in one of two ways:
- Droid moves it. Before starting substantial work, such as a multi-step change across several files, a pull request, or extended debugging, Droid opens a code channel named after the task. Droid stays in the thread for questions, small fixes, and conversational replies, or when you ask it to stay there.
- You ask for one with
!new. Post@Factory !new <task>to start a new session in its own code channel. Send@Factory !newin an existing session's thread to move that session into a code channel. In DMs and code channels, you can leave out the@Factorymention.
When a session moves, the original thread gets a "Working on this in #channel" notice. Replies in that thread no longer reach the session, so Droid asks you to send them in the channel instead.
Work in a code channel
- Post top-level messages in the channel. You do not need to mention
@Factory. Droid reads the channel's messages, replies top-level, and stays quiet when a message is not meant for it. - Droid keeps the repository and branch shown in the channel current as it switches repositories or branches.
- When Droid has changes, Slack shows a diff of its branch against the base branch. Factory withholds the diff when it may contain secrets or is binary or too large, and shows a notice instead.
- Questions from Droid appear in the channel. Answer them with a regular message.
Archive a code channel
When the work is done, ask Droid to archive or wrap up the channel. Droid posts a summary of the outcome, pull request links, and anything left open, then archives the channel. Droid does not archive a channel on its own initiative.
If a code channel has no activity for 7 days, Factory posts a warning and archives the channel 24 hours later unless someone sends a message. Archived channels stay in Slack as a record of the work. To pick the work back up, mention @Factory in the original thread.
Personal DMs and shared channels
The Slack conversation determines whose access Droid uses:
| Where you send the request | Session identity | Credentials and connectors |
|---|---|---|
| A direct message to Factory | Your personal Factory identity | Your personal Git credentials and connected apps |
An @Factory mention in a channel | The Agent Profile that serves you | That Agent Profile's Git credentials and connected apps |
Connect the tools you want to use in DMs under your own Factory account. For shared channel work, configure them on the Agent Profile. Mentioning Factory in a channel does not pass your personal connectors to the shared session.
Send the DM to the Factory app itself. If you mention @Factory in a DM with yourself, Slack does not let Factory join that conversation, so Factory asks you to open a code channel instead.
A DM uses the instructions and model defaults of the Agent Profile that serves you on Slack. By default, Factory provisions a computer owned by you from that Agent Profile's Environment instead of using the Agent Profile's computer pool.
To run your DMs on one of your own computers, such as a Droid Computer, or on a different Environment, open Settings → Session Defaults → Delegations and choose a DM delegation machine. See Set personal delegation defaults. If you have not chosen a machine and the Agent Profile has no Environment, Factory replies that it cannot start the delegation.
Slack commands
Start a message with a command to control Factory instead of sending a task. In channels, mention @Factory before the command, for example @Factory !help. In DMs and code channels, send the command on its own.
| Command | What it does |
|---|---|
!new <task> | Starts a new session for the task in its own code channel. Without a task, Factory opens the code channel so you can describe the work there. In an existing session's thread, !new moves that session into a code channel. |
!connect | Replies with SSH instructions for the computer running an existing session. Start a session first, then send !connect in its thread or code channel. In channels, only you can see the reply. |
!help | Lists the available commands. |
Send !help and !connect on their own. If a message has any other text, Factory treats it as a normal request.
Best practices
- Add the Factory app only to channels where development discussions occur.
- Use threads rather than channel messages when mentioning Factory. For larger tasks, Droid may move the work into a code channel.
- Provide sufficient context in the Slack thread before mentioning Factory.
- Regularly review the permissions granted to the Factory app in your Slack settings.
Troubleshooting
Visit Factory's Trust Center for compliance documents, certifications, and security resources
Review Factory's Privacy Policy and Terms of Service.