Field noteOct 22, 20261 min read1 source

Factory now supports @SlackHQ delegations.

In one minute

Factory has documented Slack delegations for Droid, its coding agent.

What changed: Factory now documents Slack delegations in the app: teams can mention @Factory in channels or DM it to run Droid, with channel work using shared service-account configuration and DMs using personal identity.

Teams can mention @Factory in a Slack channel or send it a direct message to request investigation, implementation, and testing work. Droid posts progress and results back to the same conversation.

Channel requests run with an organization's shared Apps configuration and service-account identity. Direct messages use the requesting person's Factory identity, Git credentials, and connected apps. Setup requires a Factory organization on a paid plan, a Manager or Owner role, Slack workspace admin access, and configured compute and service-account access for shared channel work.

Factory can move person-started delegated sessions into Slack code channels. Those channels show the repository, branch, and a diff against the base branch; users can request one with !new. Factory says it withholds diffs that may contain secrets, are binary, or are too large. Inactive code channels receive a warning after seven days and are archived 24 hours later unless activity resumes.

The documentation does not state a launch date, separate price, supported Slack plan requirements, or measured task-success rates. It also does not establish that every request will open a pull request or enter a code channel.

Evidence / sources

  1. 1docs.factory.com/delegations/slack
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicHarness EngineeringExplore the harness-engineering topic hub.
  2. 02topicAgent RuntimeExplore the agent-runtime topic hub.
  3. 03archiveField NotesOpen the latest editorial analysis.
  4. 04source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract