Linear — one issue per feedback item, not an OAuth app

What it does

• One Linear issue per feedback item. Create Linear issue on the feedback detail page (or MCP create_tracker_issue) files one issue in the project's default team. A second click returns the existing issue — it does not file a duplicate.
• Same body as the GitHub issue. The description is the source-mapped draft: component and source file (file:line when the SDK captured it), console errors, failed network calls, and a link back to the dashboard item. A captured replay stays on that dashboard item — it is not pasted into Linear.
• Click, not automatic. Connecting Linear does not file an issue on every new report. GitHub can auto-export; Linear does not.

How to connect

1. In Linear, open Settings → API and create a personal API key (it starts with lin_api_). Copy the team id from that team's settings, or from Linear's API.
2. On the Feedback DevTools project page, paste the key and the team id in the Linear section and click Save. The badge turns Connected. The key is not shown again.
3. Open a feedback item and click Create Linear issue. A second click returns the same issue instead of filing a duplicate.

Create a personal API key in Linear → Settings → API. The team id is on that team's settings page, or from Linear's API. The key is stored encrypted and never sent back to the browser.

Honest limits

• This is a personal API key, not a Linear OAuth app.
• No status sync back from Linear. Closing or reassigning the issue in Linear does not update the feedback item. One-way only.
• One default team per project. MCP create_tracker_issue can override teamId on that call; the dashboard button uses the saved team id.
• Not a Destinations sink. Slack and signed webhooks (Zapier Catch Hook, Make, n8n) still route new items. Linear is the one-click issue export.

See also GitHub, Slack and Zapier Catch Hook.