---
schema_version: "newruntime-agent-readable-v0.1"
type: "post"
slug: "linear-loops-agent-workflows"
title: "Linear Loops Turns Recurring Work into Agent Workflows"
description: "Linear Loops shows how product systems are starting to embed agents not as chat, but as repeatable workflows with schedules, events, run memory, and context access."
status: "published"
published_at: "2026-07-21"
topics: ["linear","agent-workflows","product-ops"]
source_urls: ["https://linear.app/now/introducing-loops"]
routes: {"html":"https://newruntime.com/posts/linear-loops-agent-workflows/","markdown":"https://newruntime.com/posts/linear-loops-agent-workflows.md","json":"https://newruntime.com/posts/linear-loops-agent-workflows.json"}
source_format: "markdown"
---

# Linear Loops Turns Recurring Work into Agent Workflows

Linear Loops is important because the agent appears not as a separate chatbot, but as part of the product operating system. A loop can run on a schedule or event, work with workspace context, and return to repeated tasks.

This is closer to an agent workflow than an AI assistant. A loop has context, a trigger, run history, integrations, and an expectation of repeatable output.

## What changed

Product teams gain new operating units:

- recurring investigation;
- automatic triage;
- task follow-up;
- links between Linear, codebases, and MCP;
- loops that live longer than one chat turn.

## New Runtime Read

When an agent gets a schedule and memory of previous runs, it becomes a small work process. This is no longer "ask AI". It is "put AI on duty".