LinearB Launches Agentic Studio to Give Coding Agents Engineering Context

LinearB has launched Agentic Studio to turn software-delivery data into context that engineering leaders and coding agents can use to make decisions. Announced November 2, the platform combines natural-language analysis with an engineering context layer spanning the tools teams use to plan, write, review and release software.

The launch reflects a growing problem in AI-assisted development: producing more code does not automatically help an organization deliver useful software faster. Reviews can become congested, changes can grow harder to assess, and agents can begin a task without knowing which services are fragile or why a particular fix matters.

Agentic Studio is available to all LinearB customers, according to the announcement. Agent skills, including an initial capability for matching an agent’s effort to a task, are in early access.

Turning Delivery Data Into Engineering Context

LinearB collects information across software delivery and normalizes it into a common model. The company says it reconciles engineers’ identities across Git and project-management systems, connects changes from ticket to release, and adds AI attribution and benchmarks to help leaders interpret the results.

The important step is connecting those records. A pull request can look straightforward in isolation while affecting a service with recent incidents, frequent rework or complicated ownership. Linking the change to that history gives a reviewer or coding agent information that a repository snapshot alone may not provide.

In the new studio, leaders can ask questions in plain language, obtain suggested next steps and use AI assistance to create metrics, dashboards and other artifacts. LinearB says organizations can define the context available to users with role-based access built into the platform.

That direction aligns with the company’s context-engineering guidance, which emphasizes selecting relevant information rather than filling an agent’s context window indiscriminately. Its framework considers the code, the intent behind a change, connections across systems and the boundaries of what an agent may access.

An Early-Access Skill for Matching Effort to Risk

The first agent skill is designed to decide how much effort a coding task warrants. LinearB says it considers business relevance, complexity and risk, using signals such as rework rates, recent service incidents and ownership history.

A low-risk change can receive a lighter treatment with fewer tokens, while a more consequential change can receive more deliberate analysis and testing. Engineering leaders can see how frequently tasks are routed to low, medium or high effort. The company says the skill works with any coding agent, although the announcement does not provide comparative results across specific agents or quantify realized token savings.

The engineering idea is useful even before a cost claim is established. A uniform reasoning budget treats a minor maintenance change and a sensitive production fix alike. Task-specific context could help allocate more attention where mistakes are expensive, while reducing unnecessary work on simpler changes.

MCP Connects the Data to Existing AI Workflows

LinearB also exposes engineering information through the Model Context Protocol, or MCP. Its MCP product page describes natural-language access to delivery metrics, custom reporting and bottleneck analysis, alongside recommendations such as review automation and routing.

This gives teams a way to investigate engineering data from an AI client instead of manually moving between dashboards. MCP provides the connection to tools and information; the context layer supplies the delivery-specific relationships that make a question about a repository or team meaningful.

There is a distinction to resolve as the new platform rolls out. While the launch describes role-based access and enterprise guardrails, LinearB’s public MCP FAQ still lists permissions-scoped MCP access as a roadmap item. The new studio’s access-control statement should therefore not be read as confirmation that every existing MCP client already inherits every LinearB permission.

Why More AI Output Can Expose Downstream Bottlenecks

LinearB’s announcement cites 2026 AI benchmarks drawn from 2.7 million pull requests and 83,000 developers across 253 organizations. Developers using AI on at least 75% of coding days merged 96% more pull requests per week than a year earlier, according to the company.

Those figures describe observed activity, rather than proving that AI alone caused the change. More merged pull requests also does not establish that customers received twice as much value. The release separately cites findings that AI-assisted changes were larger and agent-created pull requests waited substantially longer for review, illustrating how faster code generation can shift work onto the rest of the delivery process.

A customer example makes that distinction concrete. LinearB says Kraken used its MCP server with AI to investigate review delays and found that time zones and reviewer availability mattered more than large changes. Kraken reportedly reduced review time at the 90th percentile by more than half over four months. The company’s published discussion with Kraken provides further context on using repository data and delivery metrics to uncover bottlenecks.

From Measuring AI Adoption to Improving Delivery

LinearB plans additional agent skills for downstream work such as review, merge and governance. Those are future directions, distinct from the studio’s current availability and the effort skill’s early-access status.

The broader proposition is that coding agents need an understanding of the organization around the code: what matters, who owns it, where earlier changes failed and which constraints apply. Agentic Studio brings that proposition into the developer-productivity platform, with its value ultimately measured by the quality and flow of delivered changes rather than the amount of code generated.