Observed facts: Factory says users can assign a Linear issue to its Agent entry or mention @Factory in a comment to start Droid. The session receives the issue title, description, labels, and comments, runs on remote compute, and reports progress and results in Linear. Mechanism: The integration converts an issue into an execution request, but the run uses the delegation configuration’s service-account identity, Git credentials, connectors, plugins, and compute rather than the requester’s personal connections. This puts identity and environment choices upstream of task execution, and means configuration changes can affect other delegation apps.
Why now: Teams adopting agents need a handoff path that fits existing work queues, not a separate chat-only workflow. Factory’s documentation makes issue assignment and comments that path, and spells out the required inputs: repository, intended outcome, acceptance criteria, and verification steps. First implication: Linear can serve as a durable task boundary for delegated coding, but issue quality and shared execution setup become part of the agent’s effective capability. Factory also says to review changes and test results before merging; delegation does not replace code review.
Evidence boundary: The supplied public source is Factory’s documentation, which establishes the supported workflow and its stated configuration requirements; it does not provide adoption, reliability, or outcome metrics. First watch condition: Whether Factory adds public evidence on completion rates, review burden, or failure modes for delegated Linear issues. The prior coverage of Factory’s software-factory framing is related, but this source adds a specific issue-tracker trigger and shared-identity execution path rather than outcome analytics.