Factory's Droid Now Takes Coding Tasks Directly From Slack and Jira
Factory makes Delegations generally available, letting teams hand coding tasks to its Droid agent directly from Slack, Linear, Jira, and Microsoft Teams.
- Factory made Delegations generally available for handing Droid tasks from Slack, Linear, Jira, and Teams.
- Admins set default model, instructions, plugins, service account, and compute once in Settings.
- Delegated sessions run under a dedicated service account with its own Git credentials and connectors.
- Builds on recent GA releases of Custom Automations and prebuilt Environments for Droid agents.
- Current limits: Everyone-only access scope, no airgapped support, Slack mention context only.
- More tool integrations coming next week, per Factory's announcement.
Factory brings Droid assignments into chat and issue trackers
Factory has made Delegations generally available, allowing organization members to start work with its Droid coding agent from Slack, Microsoft Teams, Linear, and Jira. After an administrator configures the feature, requesters can assign tasks without opening Factory or preparing a local development environment.
Droid runs each delegated task on preprovisioned remote compute using the organization’s shared instructions, plugins, credentials, and model settings. Depending on those instructions, the agent can inspect code, run tests, summarize its work, and open a pull request for review.
A handoff in four steps
- An administrator sets the defaults. A Manager or Owner selects the model and reasoning level in Settings under Delegations. Choosing Auto Model lets Factory Router select the model.
- The administrator defines shared behavior. Organization-wide instructions can specify required tests, completion-summary formats, pull request policies, and available plugins.
- A teammate submits a task. The request arrives through a supported chat or issue-tracking integration.
- Droid starts on remote compute. The job uses an existing machine pool, avoiding local setup and sandbox warm-up time.
Each integration handles context differently
| Integration | How to delegate | Context available to Droid |
|---|---|---|
| Slack | Mention Factory in a message | The mentioning message only; earlier channel and thread messages are excluded |
| Microsoft Teams | Mention Factory with the task details | The context included with the mention |
| Linear | Assign the issue to Factory or mention Factory in a comment | The issue description and submitted request |
| Jira | Use the Agents picker or mention Factory in an issue comment | The issue details and submitted comment |
Slack requests require enough detail in the message that mentions Factory because Droid currently receives no earlier thread history. Linear and Jira tasks should place requirements, repository details, acceptance criteria, and relevant links in the issue description.
A dedicated identity contains access
Every delegated job runs through a dedicated service account rather than the requester’s identity. That account has its own Git credentials and connectors, giving administrators one place to limit repository and service access while preserving a consistent audit trail.
Factory separates delegation apps from connectors. Delegation apps accept incoming requests from Slack, Teams, Linear, or Jira, while connectors provide the tools Droid uses during execution. Adding a personal connector does not install the corresponding delegation app for the organization, which keeps individual integrations separate from shared workflows.
Delegations completes the execution path
Factory now offers three related mechanisms for starting and running agent work. Custom Automations handle scheduled and event-triggered jobs, Environments provide reusable development sandboxes, and Delegations accept ad hoc requests from chat and issue trackers.
Factory described a broader plan in its Terminal Bench post: make Droid available across the CLI, IDEs, code review, CI/CD systems, terminals, and servers. Delegations provides the intake layer for work that begins in team conversations or ticket queues.
Current rollout limits
- Access applies organization-wide. The current setting is Everyone; support for custom groups is planned.
- Air-gapped deployments are excluded. Delegations settings are unavailable in those environments.
- Slack history is limited. Droid receives the mentioning message without preceding channel or thread context.
- Configuration requires elevated roles. Only Managers and Owners can configure Delegations.
- Some Slack features need extra permissions. Code-channel functionality depends on specific workspace permissions.
Factory says additional integrations are coming. Teams already using Droid through the CLI or desktop app can use Delegations to accept work from product managers, SREs, and on-call engineers while keeping execution under a controlled service identity. Clear task descriptions and scoped credentials remain central to producing reviewable results.
Comments
