Loops

Loops let Linear take action automatically when issues match a set of conditions or on a defined schedule. Use them to reduce manual triage, keep work moving, and handle routine follow-up.

Overview⁠

Loops can be created at the workspace or team level:

• Workspace loops are useful for workflows that apply across multiple teams
• Team loops are useful for workflows owned by a specific team

Each loop includes:

• A Trigger that decides when it runs
• Instructions that tell Linear what to do
• Optional Tools the loop can use
• Permissions that control what data it can access

Setup & Permissions⁠

A Workspace admin can control who can create and manage workspace loops in Settings → Security → Workspace management → Manage loops

Team owners can control who can create and manage team loops in Settings → Teams → [Team name] → Access and permissions → Loop management.

Create a workspace loop⁠

1. Open Loops from the sidebar, or click on “More” to display
2. Click New loop
3. Choose the trigger for the loop
4. Add instructions describing the outcome you want Linear to achieve
5. Add any tools the loop should be allowed to use
6. Review the loop’s permissions and scope
7. Create the loop, then enable it when you are ready for it to run

Create a team loop⁠

1. Open the relevant team home page
2. Go to Loops
3. Click New loop
4. Choose the trigger for the loop
5. Add instructions describing the outcome you want Linear to achieve
6. Add any tools the loop should be allowed to use
7. Review the loop’s permissions and scope
8. Create the loop, then enable it when you are ready for it to run

Loop types⁠

Loops can be configured in a few different ways depending on what should cause them to run.

Issue⁠

Use when you want Linear to respond automatically to changes in issue state or issue attributes.

Examples:

• Delegate bugs reports to a coding agent for review, along with a fix
• Follow up on issues that enter a particular workflow state
• Apply routine handling to issues that match a defined pattern

Scheduled⁠

Use when you want Linear to perform checks or routine follow-up at a specified cadence. Examples:

• Review a queue every weekday and share a high-level summary
• Check for issues that need follow-up at the end of each week
• Review help documents against your codebase to maintain their accuracy

Tools⁠

Tools extend what Linear Agent can do during a loop run. When a connected tool is available and permitted for the loop, Linear Agent can use it to gather additional context or take supported actions beyond Linear itself.

Examples of what tools can enable:

• Search or retrieve content from connected sources such as GitHub, Notion, or Sentry
• Post comments or updates to external services when the loop has write access to that tool
• Fetch relevant documentation, pull request details, or error reports to enrich an issue

To use a tool in a loop, the tool must be connected to your workspace, enabled for Linear Agent, and allowed by your workspace admins. Reference the tool in your loop’s instructions to tell Linear Agent when and how to use it. For example: Use the GitHub tool to find the related pull request and summarize its changes.

Tool access still depends on the loop’s scope and permissions.

Loop Permissions⁠

Permissions let you configure which data each loop can access and which actions it can take.

Team access⁠

Defines the list of teams that the loop can access; it will be able to read and write data in these teams only. By default, a loop at the workspace level or in a public team will have access to all public teams, while a loop inside a private team will have access only to that team.

Web access⁠

If enabled, the loop can access information from external websites.

Enable this intentionally, since allowing external web access can increase the risk of exposing workspace data outside Linear.

Code Intelligence⁠

If enabled, the loop can use Code Intelligence to browse and analyze code repositories configured in your workspace.

Coding sessions⁠

If enabled, the loop can start a coding session.

Externally synced issues and comments⁠

If enabled, the loop will be able to write data on issues or comment threads that are synced with external applications, for example a thread synced with Slack or an issue synced with GitHub. Those might be accessible to users outside of your Linear workspace.

External sources⁠

Issues can be created from external sources, for example from Slack messages through Asks or from received emails. For security reasons, loops will only run on trusted issues that are created from within Linear. If you want to allow a loop to run on issues created from external sources, you can allow specific external sources on a per loop basis.

Allow changes outside of triggering issue⁠

If enabled, the loop can write data to any issues that are part of the Team access. If disabled, the loop can only write data on the single issue that triggered the loop for a given run.

Note: A workspace owner must configure the list of allowed external sources first before loops can opt-in to them.

Review loop runs⁠

Use Run history to check that a loop is behaving as expected and to investigate failed runs and recent activity.

1. Open Loops from the workspace or team where the loop lives
2. Select the loop
3. Open Run history
4. Review recent runs to see when the loop executed and whether it completed successfully

AI credits⁠

Agent loops use your workspace’s AI credits when they run. The cost varies depending on the complexity of the instructions and whether a coding session is triggered during the run.

If your workspace runs out of AI credits, loops can stop running until credits are added.

A Workspace Admin can see a live breakdown of usage and user in Settings → Workspace → Billing → AI Usage and credits.

FAQ⁠