Who can use the AI assistant?

Admins, editors and viewers. LinearB scopes every answer to the teams that person can already see, so a team lead asking about delivery gets answers about their own teams.

Where do the answers come from?

From the same widgets and metric definitions behind your LinearB dashboards. Each answer names the widget, dashboard and date range it used, so you can open the same view and compare.

Can I keep an answer?

Answers stay in the chat, and you can copy them. To keep a metric on a dashboard, switch to Builder, describe the widget, and save it to Studio.

Can I see and edit the query Builder writes?

Yes. The Agentic Studio shows the SQL behind every widget. You can edit it, run it again, and change the widget type and axes before you save.

Does it respect individual metric privacy settings?

Yes. If your organization has turned off individual-level metrics, the assistant doesn't return individual-level data.

How accurate are the answers?

LinearB grounds every answer in your LinearB data and names the widget it ran. As with any AI-generated answer, check important numbers against the dashboard before you act on them.

Workflow automation that keeps PRs moving

Cut the wait between opening a pull request and merging it. gitStream approves safe changes, routes the rest to the engineers who know the code and applies your policies on every repo, so reviewers spend their time where it matters.

Read the docs

6PRs in one queue, none with a reviewerA docs fix waits behind an auth change. The oldest has waited 2d 4h.

Approved automaticallysafe_changes.cm

Update the onboarding guide#483

docs/ · 3 files · +48 −12

Waiting 1d 6h · no reviewer

Cover invoice export in tests#488

test/ · 2 files · +96

Waiting 19h · no reviewer

Sent to code expertscode_experts.cm

Retry budget for ledger sync#482

src/ledger/ · 6 files · +214 −38

Waiting 2d 4h · no reviewer

Paginate the invoices endpoint#485

src/api/ · 4 files · +132 −20

Waiting 1d 2h · no reviewer

Security reviewsensitive_files.cm

Rotate session tokens on sign-in#484

src/auth/ · 3 files · +126 −41

Waiting 22h · no reviewer

Check webhook signatures#487

src/billing/ · 2 files · +58 −14

Waiting 9h · no reviewer

Trusted by the teams transforming software delivery

Write the rules your team already follows

gitStream reads the .cm files in your repository and runs them whenever a pull request opens or gets a new commit. Start from the automation library, or write rules for how your team already works.

Ifa PR only changes docs or teststhenlabel it safe-changeapprove itsay why in a comment

safe_changes.cm

automations:
  safe_changes:
    if:
      - {{ is.docs or is.tests }}
    run:
      - action: add-label@v1
        args:
          label: 'safe-change'
      - action: approve@v1
      - action: add-comment@v1

Update the onboarding guide#483

Openmaya-r wants to merge 2 commits into main from docs/onboarding

Labelssafe-change

Reviewersgitstream-cmApproved

MRmaya-r pushed 2 commits

3 files changed+48−12

docs/onboarding.md+32−8

docs/setup.md+14−4

README.md+2

gitstream-cmbotcommented

Approvedgitstream-cm approved these changes. Ready to merge.

review_sensitive_files.cm

automations:
  review_sensitive_files:
    if:
      - {{ files | match(list=sensitive_files) | some }}
    run:
      - action: add-reviewers@v1
        args:
          reviewers: [acme/security]
      - action: set-required-approvals@v1
        args:
          approvals: 2

Rotate session tokens on sign-in#484

Opensam-o wants to merge 3 commits into main from auth/rotate-tokens

Reviewersgitstream-cm

SOsam-o pushed 3 commits

3 files changed+126−41

src/auth/session.ts+88−31

src/auth/tokens.ts+26−10

test/auth/session.test.ts+12

gitstream-cmbotcommented

2 approvals requiredWaiting on acme/security before this can merge.

estimated_time_to_review.cm

automations:
  estimated_time_to_review:
    if:
      - true
    run:
      - action: add-label@v1
        args:
          label: "{{ calc.etr }} min review"

Retry budget for ledger sync#482

Opendana-k wants to merge 1 commit into main from ledger/retry-budget

Labels12 min review

Reviewersgitstream-cm

DKdana-k pushed 1 commit

3 files changed+191−31

src/ledger/sync.ts+96−22

src/ledger/retry.ts+54−9

src/ledger/budget.ts+41

gitstream-cmbotcommented

Review requiredAt least 1 approving review is required to merge.

label_claude_code.cm

automations:
  tag_claude_pr:
    if:
      - {{ is.claude_author or is.claude_co_author }}
    run:
      - action: add-label@v1
        args:
          label: "Claude Code"

Paginate the invoices endpoint#485

Openli-w wants to merge 1 commit into main from api/invoice-pages

LabelsClaude Code

Reviewersgitstream-cm

LWli-w pushed 1 commit

1 file changed+64−12

src/api/invoices.ts+64−12

gitstream-cmbotcommented

Review requiredAt least 1 approving review is required to merge.

Automate the work around every pull request

The gitStream automation library covers the jobs that slow pull requests down, from finding reviewers to running CI. Use each automation as it is, or change it to fit how your team works.

Send each PR to the engineers who know the code

Assign code experts based on who has worked on and knows the changed files, request reviewers by directory, or spread reviews around to share knowledge.

gitstream-cm · Code experts

PKpriya-k54%

MTmarco-t27%

JMjo-m12%

gitstream-cm requested review from priya-k and marco-t

Give reviewers context before they open the diff

Label every PR with its estimated review time, flag PRs that skip tests or delete files, and link each one to its Jira ticket.

Move session store to Redis#491

18 min reviewmissing-testsdeleted-files

Jira ticket: PLAT-1284

Add CSV export to invoices#494

3 min review

Jira ticket: PAY-311

Approve the changes that don't need a reviewer

Approve docs, tests, formatting and one-line fixes automatically, or let a team approve changes to the directories it owns.

Fix typo in the setup guide#492

safe-changeApproved by gitstream-cm

Bump the retry limit to 5#493

1 line, 1 fileApproved by gitstream-cm

Enforce your policies in every repo

Require security review for sensitive files and a second approval for large PRs, and check PR titles and changelogs, across every repository at once.

Semantic PR titlefeat(billing): …

Changelog updatedCHANGELOG.md

Jira ticket linkedBILL-207

Security reviewacme/security

Second approval34 min review

Run only the CI each change needs

Trigger GitHub Actions workflows based on what a pull request changes, its branch or its labels, so a docs fix doesn't wait on your full test suite.

GitHub Actions for #492 · docs only

lintRan · 38s

docs-previewRan · 1m 12s

unit-testsNot triggered

e2e-suiteNot triggered · 24 min suite

mobile-buildNot triggered

Work with the tools you already run

Merge Dependabot and Snyk updates once checks pass, approve code that clears your SonarCloud quality gate, and post to Slack or Microsoft Teams when a rule needs someone.

Bump axios from 1.7.2 to 1.7.4#495

approved-dependabotMerged once checks passed

Add rate limits to the export API#496

Sonar: Clean CodeApproved by gitstream-cm

#billing-reviews

#487 touches src/billing/ and needs a security review

Put AI to work on every pull request

Reviewers open pull requests to a clear summary and an AI review that's already done. And work from AI coding tools gets its own label, so you can see where it lands.

GitHub CopilotCursorClaude CodeWindsurfCodex

Retry budget for ledger sync #482

dana-k commented

/gs desc

👀👍

/:\

gitstream-cm bot updated the description

Summary

Adds a retry budget to ledger sync, so a sync that keeps failing stops after five attempts and logs why.

budget.ts adds the budget, with a limit you can configure
retry.ts counts attempts for each sync job
sync.ts stops and logs once the budget runs out

Need a description or a review now? Type /gs desc or /gs review in any pull request comment.Comment commands work on GitHub.See AI code reviews

Customers

How engineering teams keep pull requests moving

Gartner® Magic Quadrant™

LinearB is a Leader

Alex L.Senior Engineering Manager, Pizza Hut Digital Ventures (Yum! Brands)Read the Yum! story

Jeremy LamitHead of Engineering, Rabbit CareRead the Rabbit Care story

Bart DziekanHead of Cloud Solutions, SurveyMonkeyRead the SurveyMonkey story

Natively secure, obsessively compliant

Independently audited, with evidence of our controls available on request. LinearB participates in the EU-U.S. Data Privacy Framework.

GDPR: General Data Protection Regulation

Measure what each automation changes

Filter any LinearB metrics report by the labels gitStream adds, and see how those pull requests compare with the rest on cycle time.

See engineering metrics

Workflow automation FAQs

GitHub, including GitHub Enterprise Server through a custom app, GitLab and Bitbucket Cloud. Most actions work on all three, with some exceptions: labels aren't available on Bitbucket, required approvals aren't available on GitLab, and comment commands and GitHub Actions triggers are GitHub only.

Minutes: about 2 to 5 on GitHub Cloud, 5 to 10 on GitHub Enterprise Server and 10 to 15 on GitLab or Bitbucket Cloud. You can install it on one repository, a few, or your whole organization.

Yes. When a pull request changes a .cm file, gitStream runs in dry run mode and comments with what each automation would have done, without doing it. You can also try rules against any GitHub pull request in the gitStream playground.

Yes. Rules can live in each repository's .cm folder, or in one organization-level cm repository that applies them everywhere.

Not on the Essentials plan. Managed Mode runs a set of ready-made automations, including AI review, AI descriptions, AI tool labels, review time labels, missing Jira labels and Dependabot approvals, from switches in LinearB. It works with GitHub. Custom rules live in .cm files in your repositories.

CODEOWNERS assigns reviewers by file path. gitStream rules can also look at what changed, who knows that code, how long the review will take and who wrote it, then label, approve, request changes, require more approvals or trigger a GitHub Actions workflow.

No. gitStream reads code and repository metadata only as needed to evaluate your rules and run AI features. It acts on the pull request, with labels, comments, reviewers, approvals and the merges your rules allow, and doesn't modify your code.

Yes. Rules can label pull requests from GitHub Copilot, Cursor, Claude Code and other AI tools, for example by the co-author on their commits. LinearB can then compare those pull requests with the rest on cycle time.

Workflow automation that keeps PRs moving

Write the rules your team already follows

Automate the work around every pull request

Send each PR to the engineers who know the code

Give reviewers context before they open the diff

Approve the changes that don't need a reviewer

Enforce your policies in every repo

Run only the CI each change needs

Work with the tools you already run

Put AI to work on every pull request

How engineering teams keep pull requests moving

Natively secure, obsessively compliant

Measure what each automation changes

Workflow automation FAQs

Write the rule once, and every pull request follows it