Is Linear AI Down?

If Prismix shows Linear as "Operational" but AI features are failing:

• AI issue creation from screenshot failing (OCR not recognizing code snippets) — Linear's AI issue creation uses vision models to extract issue details from screenshots. Terminal output and code snippets with monospace fonts often have lower OCR accuracy. Paste the code text directly into the issue body after creation, or take the screenshot with higher contrast settings (e.g., use a light terminal theme).
• AI summaries taking over 30 seconds on large projects — AI cycle and project summaries process all issues in the scope. Projects with thousands of issues hit the model's context window limit and require multiple passes, increasing latency significantly. Narrow the summary scope by filtering to a single cycle or label set before triggering the AI summary.
• Automated triage applying the wrong team or label — Linear's AI triage uses workspace-level training from past issue assignments. If your team recently reorganized or renamed teams, the triage model may route to a stale team name until the training data refreshes (typically within 24–48 hours of consistent new assignments).
• Slack notification duplicate for AI-created issues — when AI creates an issue from a Slack message via the Linear app, both the Slack integration and the AI agent can fire a "new issue" notification if both are subscribed to the same channel. Review your notification settings in Linear's Slack integration page and disable duplicate triggers.
• Linear sync with GitHub PR showing stale status — the GitHub ↔ Linear sync depends on GitHub webhooks. If a PR was merged without the expected branch naming convention (e.g., missing the Linear issue ID like ENG-123 in the branch name), the sync doesn't fire and the issue stays open. Manually link the PR from the Linear issue sidebar.
• API webhook not firing for AI-resolved issues — Linear webhooks fire on issue state changes, but AI-triggered state transitions may use a different actor identity (the "Linear AI" bot user). If your webhook consumer filters by actor user ID, it will miss AI-driven updates. Remove actor-based filtering or add the Linear AI bot user ID to your allowlist.