# Linear Loops connects a changed project plan with the follow-up work

> The September expansion adds project and cycle triggers, document edits, and Slack updates. The target is the coordination that happens after a plan changes.

Canonical: https://stacktak.com/news/linear-loops-project-changes-documents-slack
Author: Stacktak Editorial
Published: 2026-10-12T14:00:00.000Z
Modified: 2026-10-20T19:30:27Z

Moving a deadline is easy. Updating every place that deadline appears is the part teams miss. Linear’s September 14 expansion of Loops targets that follow-through, with recurring agent workflows that can react to more workspace events.

The added triggers include changes to initiatives, projects, cycles, and issues. Loops can edit Linear documents and post updates to Slack. A completed run also leaves a conversation that a person can continue to review or redirect the work. [Linear’s announcement](https://linear.app/changelog/2026-09-14-loops-for-product-management) describes the changes.

## A trigger needs a clear boundary

For a launch plan, the useful starting point is one narrowly defined event: the project’s target date changes. The team can specify which document should reflect it, who needs an update, and which decisions must remain with a person.

The risk is ambiguity. If a plan contains an old date quoted as historical context, replacing every date could damage the record. Our suggested pilot would compare the document before and after each run and inspect the message intended for colleagues. Success means the right follow-up happened with the right context, not simply that an automation fired.

## Source

[Linear — Loops for product management, September 14](https://linear.app/changelog/2026-09-14-loops-for-product-management).