What Hai Does with Your Linear Workspace
Connecting Linear gives Hai the engineering context around a report before it decides anything. Hai reads related issues, documented mitigations, accepted-risk decisions, and work already in progress on the affected component so its validation reasoning reflects what your engineering team already knows.
While Hai reviews a report, it searches Linear (read-only) for signals such as:
Related or previously reported issues on the same asset or component.
Documented mitigations, compensating controls, or accepted-risk decisions.
Evidence that the reported behavior is by design.
Evidence that the affected asset is deprecated, sunset, or non-production.
Work already in progress on the affected component and who owns it.
That context reaches you in two places:
Hai conversations: Ask Hai about related Linear work while you review a report, and it answers using information from your workspace.
Validation reasoning: Before Hai recommends an outcome, it searches Linear and cites what it found in its reasoning.
In both cases, Hai is strictly read-only: it reads issues and comments and cannot create, edit, or close anything in Linear. Writing to Linear is a separate, opt-in setting covered further down.
See It in Action
When Hai searches Linear while validating a report, the search appears in the reasoning stream. You can expand the step to see what Hai found and how it weighed that information.
The report's outcome summary then shows Linear as one of the sources behind the recommendation, next to the validation status and any other evidence Hai gathered.
Example: Linear Context Changing an Outcome
A researcher reports a missing-authorization issue on the payments API.
Before recommending an outcome, Hai searches Linear: "How have past missing-authorization (CWE-862) reports on the payments API been handled: fixed, accepted as risk, or considered by design?"
It finds ENG-2481, closed three weeks ago, documenting that the endpoint is reachable only from an internal network segment, plus a comment from the service owner describing the intended behavior.
Hai's recommendation cites ENG-2481, notes the compensating control, and provides that history to the reviewer instead of presenting the finding without engineering context.
Without the Linear connection, the same report has no history attached, and the reviewer must find ENG-2481 manually.
Before You Begin
Linear must be enabled for your organization. Contact your HackerOne representative if the integration does not appear in your settings.
A Linear account with permission to create an API token and access the teams you want to connect.
Organization admin access in HackerOne.
Step 1: Connect Your Linear Workspace
Go to Organization settings > Integrations > Linear > New Linear Workspace.
Click Set up new integration.
Configure the connection:
Workspace Name: A descriptive name (for example, "Linear prod").
Workspace Description: Optional, to help identify the workspace.
Linear API Token: In Linear, go to Settings > API, create a token with appropriate permissions, then copy and paste it here.
Once connected, you'll see the message "Connected to Linear workspace: user."
Step 2: Turn On Contextual Enrichment
Go to Organization settings > Integrations > Linear > Global features.
Toggle | What it does |
Hai integration | "Let Hai pull in Linear context when investigating reports — duplicates, related work, and more." |
Validation agent | "Automatically pulls context from your Linear workspace to enrich validation reasoning on reports." |
Both toggles grant read-only access only. Neither lets Hai write to Linear.
Step 3: Map Programs to Linear Teams
Program-to-team mapping scopes where Hai looks in Linear and where it would file an issue if you turn on issue creation.
Select a Linear team for each HackerOne program using the dropdown (for example, "Security team").
You can map multiple programs to the same Linear team.
Note: If you leave a program unmapped, Hai suggests a team when creating issues, based on which teams already own related issues for the affected asset and vulnerability class.
Optional: Automatic Issue Creation
Everything from here down is optional. Leave these settings off, and contextual enrichment will still work.
Enable or disable Automatic issue creation.
Select when issues should be created:
When report is triaged.
When report moves to pending program review (PPR).
When bounty is awarded.
When enabled, Hai creates a Linear issue when the selected trigger occurs. Issues include the severity, affected asset, vulnerability description, and a link back to the HackerOne report.
Note: The selected trigger must occur for automation to work. For example, if you select PPR, issues are created only when reports reach that state.
Optional: De-duplication Control
When issue creation is enabled, Hai checks Linear for an existing issue before creating a new one.
Set the Confidence threshold between 0% and 100% (default is 75%). Lower thresholds result in more aggressive de-duplication:
75–100%: Conservative: only links to very similar issues.
60–75%: Balanced: recommended for most teams.
Below 60%: Aggressive: may link to less similar issues.
Before creating an issue, Hai:
Searches by title keywords from the report.
Searches by asset combined with vulnerability type (for example, "api.example.com XSS").
Reviews all search results for issues describing the same vulnerability on the same asset.
Compares technical details across titles and descriptions.
Links to the existing issue if the match is above your threshold; otherwise, it creates a new one.
Optional: Report Updates Posted to Linear
When a linked report changes, such as when its state or severity changes, Hai can post a summary comment on the corresponding Linear issue so engineering can see the update.
This is one-directional: HackerOne → Linear. Comments and status changes made in Linear are not mirrored back onto the HackerOne report, and Hai never edits or closes a Linear issue on its own.
Setup Complete
After completing the steps above, click Finish to save your configuration. Your Linear workspace appears on the Integrations page under Hai integrations. Click View to manage or edit the configuration at any time.
Looking for Two-Way Ticket Sync?
This page covers the Hai Linear integration, which focuses on contextual enrichment and can optionally create and comment on issues.
If you need two-way synchronization, use the separate manual Linear integration. It supports Linear comments, state changes, assignee changes, and priority changes flowing back to the HackerOne report, plus automatic report resolution when a Linear issue closes.
Those syncing capabilities belong to the manual Linear integration, not the Hai integration described here.
FAQ
Does Hai Change Anything in Linear Just Because I Connected It?
No. Connecting the workspace enables read-only context. Issue creation and update comments are separate, opt-in settings.
Do I Have to Enable Issue Creation to Get the Context Benefits?
No. Contextual enrichment works with issue creation turned off.
Is My Linear Data Copied into HackerOne?
No. Hai queries Linear on demand for a specific report and uses what it finds in that investigation.
Why Don't I See the Global Features Toggles?
They appear only once your organization has the corresponding features enabled. Contact your HackerOne representative.






