Just in
Platform Overview

Engineering context on demand

Agents and engineering leaders both depend on context about how your organization builds software. LinearB's new Agentic Studio lets you ask for it in plain language.

AI Assistant

Ask anything about your engineering org
Plain-language questions answered with the context behind them, plus a builder for your own custom metrics.
Explore AI assistant

Pick a metric to ask why it moved

LinearB AI assistant

Why did our cycle time jump this month?

Ran cycle time breakdown on the Engineering health dashboard, Aug 30 to Sep 29

Cycle time is up 39% this month, and most of the increase is in review. PRs spend 26.6 hours there on average against a 5.9 hour median, so most reviews clear quickly while a subset sits stuck.

Cycle time breakdown

Last monthThis month
0h10h20h30h9.4Coding12.4Pickup26.6Review1.7Deploy
5.9hmedian review time
14 PRswaiting 3+ days, 11 opened by agents

Pickup is next, at 12.4 hours on average before a first review. Want me to show which reviewers these PRs are waiting on?

ClaudeScheduled task · Mondays at 9:00

Every Monday at 9:00, post each team’s delivery summary for the last week to its Slack channel. Flag pickup time over 12 hours and list PRs waiting more than two days.

get_teamsget_metricsget_metrics_benchmarkssearch_pull_requests+
# payments-eng14 members
ClaudeAPP9:00 AM

Payments · delivery brief for the week of Oct 12

  • Cycle time 1d 9h, down from 2d 1h · Good
  • Pickup time 14h, up from 11h · Fair
  • Deploy frequency 0.8 a day · Good
  • Change failure rate 3% · Good

⚠️ Pickup time is over the 12 hour target for the second week running.

Waiting more than two days:
Retry budget for ledger sync · 2d 6h
Refund webhook timeouts · 2d 2h

👀 3✅ 2🙏 1
Message #payments-eng

Sample data · LinearB tool names as the MCP server lists them

MCP Server

Bring LinearB context to your AI
Let Claude, Cursor and any MCP client answer questions and run automations with your delivery data.
Explore MCP server

AI Code Reviews

Review that keeps up with AI
Every pull request reviewed as it opens, with fixes suggested and the right reviewer pulled in.
Explore AI code reviews

Document the new public API rate limits #4127

OpenSam Ortizwants to merge into main from docs/rate-limits+46 −12 · 3 files
SOSam Ortizopened this pull request · description by LinearB AI
Purpose

Documents the new per-key rate limits for the public API, including the burst allowance, and updates the sample config to match.

Main changes
  • Adds a rate limits section to api/README.md
  • Updates the example limits in config/api.sample.yaml
  • Adds a 429 response example to the errors page
  • Fixes two broken links in the authentication guide
LinearB AIbotreviewed 3 files
Looks good to me
No issues found. The new limits match the values in api/limits.ts, and the sample config uses the same key names as the docs.

LinearB AI approved these changes

gitStream found only docs and config changes, so no reviewer is needed

Approved by LinearB AINo issues found in a docs and config change, so gitStream approved it.

Combine LinearB with every other tool you connect

The LinearB MCP server covers delivery, quality, throughput, developer experience, DORA metrics and AI adoption. Your AI tool combines it with any other MCP server or connector you add.
ClaudeChatGPTCursorVS CodeWindsurfZedClineAny MCP client
LinearB and PagerDuty

LinearB brings

Releases and their PRsChange failure rateAI-assisted PRs

PagerDuty brings

Alerts and escalationsOn-call schedulesResolve times

What you can build with both

  • Draft a postmortem with what shipped before the incident
  • Check whether incidents follow releases heavy on AI-assisted PRs
  • Put who’s on call next to each team’s deploy frequency

Natively secure, obsessively compliant

Independently audited, with evidence of our controls, and EU data hosting available on request. LinearB participates in the EU-U.S. Data Privacy Framework.
AICPA SOC 1 Type II
AICPA SOC 2 Type II
GDPR: General Data Protection Regulation
ISO 27001 Certified

Give your agents and leaders the context to act