Skip to content
Per-pair page

Claude + Linear: AI-first triage and writing inside the issue tracker.

Use Claude to triage Linear issues, summarize project status, draft technical specs, or auto-link related work. Built for engineering teams that already think AI-first.

Trigger app
Linear as the trigger

Workflows fire when something happens in Linear.

See all 6 triggers →
Action app
Anthropic as the action

Workflows do something in Anthropic, instantly.

See all 21 actions →
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

LinearAnthropic

When something happens in Linear, do it in Anthropic.

6 Linear triggers wired to 21 Anthropic actions. Most-used pairing: Comment CreatedAnalyze Image.

AnthropicLinear

Or fire it the other way around.

0 Anthropic triggers wired to 8 Linear actions downstream.

  • Use any trigger in the catalog as the upstream.
See AnthropicLinear
Popular pairings

Common Linear → Anthropic workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 126 combinations
When comment created in Linear, analyze image in Anthropic.

Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.

When comment created in Linear, cancel message batch in Anthropic.

Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.

When comment created in Linear, computer use in Anthropic.

Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.

When comment created in Linear, count tokens in Anthropic.

Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.

When new cycle in Linear, analyze image in Anthropic.

Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.

When new cycle in Linear, cancel message batch in Anthropic.

Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.

When new cycle in Linear, computer use in Anthropic.

Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.

When new cycle in Linear, count tokens in Anthropic.

Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.

When new issue in Linear, analyze image in Anthropic.

Fires when a new issue is created in Linear. The standard inbound hook for routing, enrichment, and SLA-aware notifications.

How it works

Connect Linear and Anthropic in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize Linear and Anthropic

    Open Tiny Command, authorize Linear and Anthropic once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Linear trigger

    Drop the Linear → Comment Created trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/linear.trigger-comment-created
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Anthropic action

    Drop the Anthropic → Analyze Image action below it. Map fields from the Linear payload into the Anthropic inputs.

    anthropic.create-message-with-image
  5. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Linear + Anthropic.

How does Claude triage new Linear issues?
Linear Issue Created → Claude reads title + description → returns team, project, priority, estimate, and labels. Workflow applies via Update Issue and adds a "triaged-by-ai" label so humans know what touched it.
Can Claude write technical specs from a Linear issue?
Yes. Prompt: "Expand this issue into a technical spec with problem statement, proposed approach, alternatives considered, and rollout plan". Save as a Linear document attached to the issue, ready for engineer review.
How do I detect Linear issues that depend on other issues?
On Issue Created, search the project for similar issues, pass them to Claude with "identify dependencies — issues that block or are blocked by this new one". Apply relationships via Linear's Issue Relations API.
Can Claude generate a weekly Linear status update?
Yes. Scheduled Friday afternoon: list closed and in-progress issues for the team this week, pass to Claude with "write a weekly engineering update for stakeholders, group by project, highlight risks". Email to the team and slack ##all-eng.
How do I prevent Claude from changing fields a human already set?
Skip triage if the issue already has the "triaged-by-ai" or "triaged-by-human" label. Or only run on issues created from external sources (Intercom, Slack, support widget) where no human has touched them yet.
What's the right Claude model for Linear automation?
Haiku for triage and label suggestions (fast, cheap). Sonnet for spec writing and status updates (the default). Opus only for long-context analyses across many issues — usually overkill for per-issue workflows.
Related

Other apps that pair well with Linear.


Wire Linear to Anthropic in 2 minutes.

Free tier available. No credit card. No onboarding call.