New controls for Linear coding agent

Coding sessions are the shortest path from issue to diff. Assign a task to Linear Agent, and it works in a secure cloud environment to write and test the code before opening a pull request for review.

We’re adding more control over how each session runs, from its environment to the models behind it.

Adaptive routing

Save time and tokens by automatically routing simpler tasks to a faster model while using the default reasoning model for more complex work. If a task needs more capability than expected, you can restart the session on the default model while keeping the original pull request for reference.

Environment secrets

Coding sessions can now access environment secrets during setup to securely fetch private dependencies and other environment config.

Open-weight models

Coding sessions now support open-weight models, starting with GLM-powered sessions. Workspace admins and owners can choose which models are available from Coding sessions settings.

Visit the docs for more details.

Team organization at scale

As companies grow, it can become challenging to accommodate every team’s workflow within a single workspace-wide system. A Product team may track discovery and development, while Marketing organizes work around campaign stages. Both need workflows that reflect how they operate, without fragmenting the company-wide view.

We're giving teams more freedom to own and organize project work, without losing sight of the bigger picture.

Team project labels and statuses

Teams can now define their own project labels and statuses to reflect how they work, and extend those workflows across their sub-teams for consistency. Team project labels and statuses are available on Business and Enterprise plans.

Project lead teams

You can now define a lead team for a project to clarify ownership when multiple teams contribute. Filter by lead team to create focused views of the projects each team owns.

Team loops triggers

Loops can now run when a team is created, someone joins or leaves a team, or an issue is assigned to a team. This makes it possible to automate recurring coordination, such as sending onboarding information to new teammates or reassigning open issues when someone leaves.

Project and initiative IDs

Projects and initiatives now have durable, human-legible IDs. Reference work reliably in agent workflows and external tools, even when names change.