AI workers for Linear

Ready-made AI workers for Linear: a triage queue that keeps moving, issues that have outlived their cycle surfaced, and a cycle summary written from what actually closed.

Meeting Action Item Collector
Reads your meeting notes each evening and files every action item into your task board.
Executive Daily Briefing
Delivers a prioritized morning brief of your day: meetings, urgent email, blockers, and team chatter.
Follow-Up Tracker
Tracks every email you are waiting on a reply to, drafts a polite nudge when a thread goes quiet past your window, and keeps a live waiting-on-others board.
SEO Watchtower
Watches Search Console weekly for ranking drops, indexing problems, and easy CTR wins, and files the fixes.
Weekly Ops Reporter
Compiles a weekly status report from your task boards, chat, and GitHub: shipped, moving, blocked.
Recruiting Coordinator
Keeps candidate threads moving: replies drafted, interviews scheduled, and the pipeline board current.
Support Inbox Triager
Triages the support inbox: classifies, prioritizes, drafts replies, and files tickets for real issues.
Cross-Team Dependency Review
Explains which project dependencies need a named owner or decision.
Company Operating Review Workflow
Combines project dependencies and leadership decisions into a short operating review.
Roadmap Commitment Review
Explains current product commitments and dependencies relevant to a proposed opportunity.
Product Opportunity Brief Workflow
Connects customer problem evidence with roadmap commitments to draft a product opportunity brief.
Usability Issue Evidence Review
Checks documented usability issues for reproducible steps and testable acceptance criteria.
Design Validation Planning Workflow
Combines user-study evidence and usability issues into a focused validation plan.
Release Acceptance Review
Checks release scope against recorded acceptance and QA evidence.
Release Readiness Workflow
Combines code changes and acceptance evidence into a reviewable release readiness packet.
Incident Action Follow-Through
Reviews corrective actions for ownership, verifiable completion and prevention value.
Incident Learning Workflow
Combines incident timelines and corrective actions into a blameless learning review.
IT Request Closure Review
Checks access and asset service requests for recorded completion evidence.
Access Review Preparation Workflow
Combines an access register and IT requests into an accountable access-review packet.
New Starter Task Readiness
Checks practical onboarding tasks for owners, dependencies and completion evidence.
New Starter Readiness Workflow
Combines onboarding tasks and approved guidance into a first-week readiness plan.

What is an AI worker for Linear?

An AI worker for Linear is an AI agent scoped to one issue-tracking job, such as keeping the triage queue from growing or reporting on how a cycle really went. It reads issues through your connected Linear workspace and updates only the fields you allow, in the teams you scope it to, leaving everything else untouched.

What these workers do

Keep the triage queue moving

Reads newly filed issues, proposes the team and labels, and returns the ones missing detail to their reporter with the specific gap named.

Surface issues rolling over repeatedly

Finds work that has slipped from cycle to cycle more than once and raises it, since repeated rollover usually means the issue is wrong rather than the estimate.

Summarize what shipped this cycle

Assembles the closed work into a readable summary grouped by project, drawn from the issues themselves rather than from recollection.

Chase issues with no owner

Flags open work that nobody has picked up, so it is decided on rather than quietly inherited by the cycle after next.

How an AI worker runs in Linear

Cycles are the clock

The triage queue is the job

Fast, with the trail intact

Linear questions, answered.

Can an AI worker close issues in Linear?

Only with permission to update issue state, which many teams withhold. The common arrangement lets a worker propose that something looks finished and leave the closing to the person who did the work, so the history stays truthful.

Does it understand cycles and projects?

Yes. It reads the cycle and project an issue belongs to, which is what makes cycle level reporting possible at all. That includes the report nobody assembles by hand, the work that has rolled from one cycle into the next more than once, which usually means the issue is wrong rather than the estimate.

Which teams can it reach?

Only the teams you scope it to within your connected workspace. A worker built for one team's triage has no visibility into another team's issues, so scoping is a real boundary rather than a filter it chooses to respect.

Will it spam issues with comments?

That is a matter of how the kit is written, and the well built ones comment once with something worth reading. You can also withhold comment permission entirely and have the worker report to you instead of writing into the tracker.

What AI workers can do in Linear

The tools a worker can be granted in Linear once you connect it. A kit grants only the ones its job needs, and you can narrow them further on the worker.

List Linear teams

List teams in Linear. Paginate with 'cursor'.

Get Linear team

Get a single Linear team with its projects (returned as groups) and workflow states (returned as columns). Use it to discover valid project names and state names before create/update; those names go in the 'fields' map, not the state IDs.

List Linear issues

List issues in a Linear team. Filter by group, status, or search query. Accepts an updatedSince ISO-8601 window for a dated delta (filtered upstream via Linear's updatedAt filter). Note: totalCount reflects upstream total before assignee-rule filtering, so items.length may be smaller per page.

Get Linear issue

Get a single Linear issue with all fields, comments (when view_comments is granted), and sub-issues.

Search Linear issues

Search Linear issues across all in-scope teams (or a subset via boardIds). Accepts an updatedSince ISO-8601 window for a dated delta. Results carry boardId/boardName context. Treat boardsFailed > 0 as a partial-results warning, not an error.

Create Linear issue

Create a new issue in a Linear team. 'fields' takes friendly keys: description, status (workflow state name or ID), priority (0-4 or No priority/Urgent/High/Medium/Low), due_date (YYYY-MM-DD), assignee (email, exact name, or user ID), labels (comma-separated names or IDs), project (name or ID), estimate (integer). Unknown keys are returned in 'rejectedFields'; an unresolvable value (unknown state, ambiguous assignee) is a 400 naming the valid options.

Update Linear issue

Update an existing Linear issue. Only keys included in 'fields' are touched; omitted keys are left untouched. Same friendly keys as linear_create_item (name to rename, description, status, priority, due_date, assignee, labels, project, estimate); pass an empty string for assignee, due_date, or project to clear it. 'rejectedFields' lists keys that weren't writable or weren't recognized.

Delete Linear issue

Delete a Linear issue. Linear moves it to the workspace trash (an admin can restore it until it is purged); treat as destructive.