Linear adds Slack and GitHub triggers, shared templates and reasoning settings to Loops

Linear’s [October 22 changelog](https://linear.app/changelog/2026‑10‑22‑slack‑and‑github‑loops) adds external triggers, shared templates and reasoning controls to Loops, its feature for automating product work. Events in Slack and GitHub can now start a Loop automatically, extending the workflow beyond waiting for someone to notice a change and ask an agent to act. The release gives two concrete examples: answering product questions in a Slack channel, and drafting a QA plan when a GitHub pull request receives a “ready for testing” label. The latter is a plan‑writing example, not a report that the Loop executes the tests or validates a release. The full supported‑event matrix and connection permissions are not specified in this notice.

The same release lets users save a Loop as a template for others in their workspace. Linear uses a bug‑triage Loop as its example: another team can adapt that workflow instead of rebuilding its configuration from scratch.

The documented action is to open a Loop’s menu and choose Save as template. The result appears alongside Linear’s built‑in templates when someone in the workspace creates a new Loop. This establishes a reuse path for the workflow. It does not document the transfer of connected‑account credentials or expanded access to a repository or Slack channel.

Loops also gain a reasoning‑level choice. Auto uses the workspace’s default setting; the explicit alternatives are Low, Medium and High. That is a per‑Loop configuration choice in the announcement, rather than a documented mapping to a particular model or token budget.

Linear presents the setting as a way to match reasoning effort to the task. The release supplies no per‑run prices, numerical reasoning limits or measured outcome comparison. A different setting should not be described as a verified improvement in correctness, speed or cost.

The [changelog](https://linear.app/changelog/2026‑10‑22‑slack‑and‑github‑loops) describes these capabilities as available, but does not identify the applicable subscription plans, rollout cohorts, full event filters or the permissions needed for each connection. It also does not establish whether a particular workspace has already connected the required Slack or GitHub accounts. For a team adopting the features, the useful checks are the chosen starting event, the task the Loop is asked to produce, the template being reused and the selected reasoning setting. Those are separate from confirming the connected accounts and reviewing the resulting work. OpenTools has read the official release; it has not created a Loop, connected an account or tested its output. *Original source‑based feature guide by OpenTools Team, based on [Linear’s October 22 changelog](https://linear.app/changelog/2026‑10‑22‑slack‑and‑github‑loops). The guide summarizes event triggers, workspace templates and reasoning controls; it is not Linear’s interface or evidence of an executed loop. The same features and their limits are explained in the article text.*