Define custom AI tools with Tool Detection

Overview

Use Tool Detection to define how LinearB recognizes in-house or niche AI tools from git activity. Activity that matches a custom tool’s detection rules is attributed as AI in AI Analytics and AI Insights, alongside the built-in AI tools.

Tool Detection is separate from AI Tools → Integrations. Integrations connect a provider’s API or telemetry. Tool Detection recognizes a tool from branch names, PR titles, authors, AI rule files, and review comments.

This feature is in Closed Beta. To enable it for your organization, contact your CSM or LinearB Support.

Before You Begin

Verify that you have:

Company Admin access in LinearB. Other roles cannot view the Tool Detection tab.
A unique name for the tool. The name cannot match a built-in LinearB tool (for example, Claude Code or GitHub Copilot) or another custom tool in your organization, including stopped tools.
At least one pattern that identifies the tool’s activity, such as a branch prefix, a PR title tag, a bot author name, or an AI rule file path.

Add a Custom Tool

Go to Settings → Company Settings → AI Tools → Tool Detection.
Click to add a custom tool.
Enter a name for the tool. LinearB checks the name as you type and blocks the save if it matches an existing tool.
Under Categories, select at least one category. Detected activity is attributed to the selected categories in AI Analytics and AI Insights.
- AI Assistant — Tools that help developers write code.
- AI Agent — Tools that complete coding tasks and open PRs on their own.
- AI Review — Tools that review pull requests.
Under Detection rules, add one or more rules. Each rule is a regular expression (regex) checked against one signal. See Detection Rules.
Click Save.

After you save, LinearB detects matching activity from the last 90 days. This takes up to about 30 minutes. While detection runs, the tool shows an Updating data… status and cannot be edited or deleted.

LinearB validates the definition before saving. Save is blocked if a regex does not compile, a pattern is empty, or the tool has no rules or no categories.

Detection Rules

Each rule checks one signal. A match counts the related commits, PRs, or reviews as activity from this tool.

Rule	What it checks	Example
Author name	Regex checked against commit authors, co-authors, and PR authors. Matching commits and PRs are counted.	`acme-agent`
Branch name	Regex checked against branch names. Matching PRs are counted.	`^acme-agent/`
PR title	Regex checked against PR titles. Matching PRs are counted.	`\[acme-bot\]`
AI rule files	Regex checked against the repo-relative paths of files added or changed in a PR. Matching PRs are counted.	`\.acme/rules/.*\.md$`
Review comment	Regex checked against PR review comments. Matching reviews are counted.	`^Acme Review:`

If a commit or PR matches more than one custom tool, each matching tool is credited for it.

Verify Detection

When detection finishes, the Updating data… status clears. The custom tool then appears in AI Analytics, AI Insights, and any filter or breakdown that lists AI tools, under each selected category and alongside the built-in tools.

Edit a Custom Tool

Go to Settings → Company Settings → AI Tools → Tool Detection and select the tool.
Change the name, categories, or detection rules.
Click Save, then choose what to do with the activity LinearB already detected for this tool:
- Keep historical data (default) — Activity detected so far stays as is. The updated rules apply to new activity only.
- Update historical data — Activity detected so far is replaced by applying the updated rules to the last 90 days. This takes up to about 30 minutes.
Click Save changes.

Stop or Delete a Custom Tool

Go to Settings → Company Settings → AI Tools → Tool Detection and select Delete for the tool.
Choose an option:
- Stop detection, keep data (default) — New activity is no longer detected. Existing data in AI Analytics and AI Insights stays as is. The tool stays in the list as Stopped, and its name stays reserved.
- Delete tool and data — The tool and all activity it detected are removed from AI Analytics and AI Insights, including history. The tool name becomes available again. Removal takes up to about 30 minutes.
Click Stop detection or Delete tool and data.

Delete tool and data cannot be undone.

To resume a stopped tool, edit it and save. To remove a stopped tool and its data, select Delete on the stopped tool and click Delete tool and data.

Troubleshooting

The Tool Detection Tab Is Not Visible

Verify that you are signed in as a Company Admin.
Verify that the feature is enabled for your organization. Contact LinearB Support if it is not.

The Name Is Rejected

Verify that the name does not match a built-in LinearB tool or another custom tool, including stopped tools. The check ignores letter case and surrounding spaces.
If the name belongs to a stopped custom tool you no longer need, delete that tool with Delete tool and data to free the name.

Couldn't Update Data

The status shows Couldn't update data. Save again to retry. Open the tool and save it again.
If the error persists, contact LinearB Support.

No Activity Appears for the Tool

Verify that detection has finished. It takes up to about 30 minutes after saving.
Verify that each regex matches real values from your repositories, such as an actual branch name or file path.
Verify that the selected categories match where you are looking in AI Analytics and AI Insights.