Factory ships Delegations for org-wide agent task handoff

Factory's Delegations, now generally available, change who sets up an agent task and whose identity the work runs under (Factory thread). An administrator configures the defaults once, in a Delegations section of Factory's settings: the model that Droid, Factory's coding agent, uses, custom instructions, plugins, a service account and the compute it runs on. After that, anyone in the organization can hand Droid a task, and Droid picks it up on a remote computer that is already prepared, so the person delegating does not have to configure the agent or a machine themselves.

The second change is identity. Shared work runs under that dedicated service account, an account belonging to the organization rather than a person, with its own Git credentials and connectors, not as whoever made the request, and administrators decide what Droid can access. That means the agent's reach is set centrally instead of following the permissions of each requester; the thread does not describe how that access is configured or reviewed. Factory calls Delegations the foundation for bringing Factory into the tools teams already use and promises more the following week, without naming those tools. It had already announced that Jira users can assign tasks to Factory as they would to a teammate, covered separately, but the thread does not say how that integration relates to Delegations. The launch video attached to the first post could not be transcribed, so this explanation rests on the thread's text alone.