Linear is expanding Loops, its recurring agent workflows for teams, so they now respond to more workspace activity, including changes to initiatives, projects, and cycles. They can also edit Linear documents and post updates to Slack. The update targets product managers and engineering leads who use Linear as their source of truth and want the coordination work around plan changes handled automatically.
The practical shift is in triggers and outputs. New triggers cover project and initiative changes to status, ownership, target dates, milestones, membership, and labels, plus new updates and comments, cycles being created, started, or completed, and issue changes to status, priority, assignee, cycle, project, or labels. When a project's target date changes, for example, a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act. Loops can also draft and post tailored Slack updates using context from Linear and connected tools, keeping the right people informed about what changed and what happens next.
The timing matters because Loops itself is still new to most workspaces. Each loop run starts a conversation with Linear Agent, and once it finishes, teams can continue that conversation like any other agent session to review the work, add context, or direct what happens next. Linear has extended introductory Loops credits through December 31 , giving product and engineering teams a window to test whether agent-run coordination actually reduces the follow-through burden that plan changes create.
Comments (14)
Sign in to join the discussion.
P
Priya Kothari25d ago
Loops editing documents automatically is either going to save my PMs eight hours a week or generate the world's most confident nonsense inside my roadmap. I will report back.
O
Oakley Renn25d ago
"The product development system for teams and agents" reads like a legal disclaimer. Try: "Ship faster. With humans or without." Free of charge, you're welcome.
D
Damilola A.25d ago
Hot take: this is Zapier for engineering orgs and nobody wants to admit it. Which is fine because Zapier prints money.
M
Marisol Quezada25d ago
Already telling my portfolio to look at this. Reminds me of the automation layer Retool grew into, except purpose-built and not a Swiss Army knife.
K
Kenji Matsuo25d ago
The launch video's cut is doing a lot of heavy lifting. Whoever timed the Slack notification ping to the beat drop, raise.
H
Hiroko M.25d ago
The thread structure is chef's kiss. Feature list, gif, link, done. Half of X could learn from not burying the demo in tweet nine.
S
Sofía Berg25d ago
ok wait, tailored Slack updates means I can finally stop writing the same Friday recap every week. If this works I owe someone at Linear a coffee.
V
Vikas R. Mehta25d ago
Nice to see initiative-level triggers. We shipped something adjacent last month and I can confirm the edge cases around cycle rollovers are genuinely evil.
N
Nadia El-Amin25d ago
Before my legal brain lets me flip this on: where do the agent actions get logged, and can we scope which documents Loops can edit? Asking for a very nervous CISO.
L
Luca Fenwick25d ago
Curious how many teams actually build multi-step Loops versus just one trigger and done. Feels like the classic Zapier long tail problem waiting to happen.
E
ethan builds25d ago
Genuine question: how big is the Loops team internally? Every Linear release makes me suspect it's four people and a very tired golden retriever.
R
Rhea Solanki25d ago
"For teams and agents" is the quiet part out loud. Every PM tool shipping this year without agent primitives is cooked.
T
Tomás Vieira25d ago
Would love to chat with someone on the Loops team about how the agent triggers were designed. DMs open, promise I'm friendly.
F
Feyisayo O.25d ago
Editing documents automatically is the scary one. Undo history better be bulletproof or someone's PRD is getting rewritten at 2am by a very confused Loop.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
Linear
The product development system for teams and agents.
The product development system for teams and agents.
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
Linear is expanding Loops, its recurring agent workflows for teams, so they now respond to more workspace activity, including changes to initiatives, projects, and cycles. They can also edit Linear documents and post updates to Slack. The update targets product managers and engineering leads who use Linear as their source of truth and want the coordination work around plan changes handled automatically. The practical shift is in triggers and outputs. New triggers cover project and initiative changes to status, ownership, target dates, milestones, membership, and labels, plus new updates and comments, cycles being created, started, or completed, and issue changes to status, priority, assignee, cycle, project, or labels. When a project's target date changes, for example, a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act. Loops can also draft and post tailored Slack updates using context from Linear and connected tools, keeping the right people informed about what changed and what happens next. The timing matters because Loops itself is still new to most workspaces. Each loop run starts a conversation with Linear Agent, and once it finishes, teams can continue that conversation like any other agent session to review the work, add context, or direct what happens next. Linear has extended introductory Loops credits through December 31 , giving product and engineering teams a window to test whether agent-run coordination actually reduces the follow-through burden that plan changes create.
Comments (14)
Loops editing documents automatically is either going to save my PMs eight hours a week or generate the world's most confident nonsense inside my roadmap. I will report back.
"The product development system for teams and agents" reads like a legal disclaimer. Try: "Ship faster. With humans or without." Free of charge, you're welcome.
Hot take: this is Zapier for engineering orgs and nobody wants to admit it. Which is fine because Zapier prints money.
Already telling my portfolio to look at this. Reminds me of the automation layer Retool grew into, except purpose-built and not a Swiss Army knife.
The launch video's cut is doing a lot of heavy lifting. Whoever timed the Slack notification ping to the beat drop, raise.
The thread structure is chef's kiss. Feature list, gif, link, done. Half of X could learn from not burying the demo in tweet nine.
ok wait, tailored Slack updates means I can finally stop writing the same Friday recap every week. If this works I owe someone at Linear a coffee.
Nice to see initiative-level triggers. We shipped something adjacent last month and I can confirm the edge cases around cycle rollovers are genuinely evil.
Before my legal brain lets me flip this on: where do the agent actions get logged, and can we scope which documents Loops can edit? Asking for a very nervous CISO.
Curious how many teams actually build multi-step Loops versus just one trigger and done. Feels like the classic Zapier long tail problem waiting to happen.
Genuine question: how big is the Loops team internally? Every Linear release makes me suspect it's four people and a very tired golden retriever.
"For teams and agents" is the quiet part out loud. Every PM tool shipping this year without agent primitives is cooked.
Would love to chat with someone on the Loops team about how the agent triggers were designed. DMs open, promise I'm friendly.
Editing documents automatically is the scary one. Undo history better be bulletproof or someone's PRD is getting rewritten at 2am by a very confused Loop.