linear

name	linear
description	Browse and manage Linear issues, projects, teams, and workflow states.
scope	agent
requires	["linear"]

Typical flows:

Find the team first → most mutations need a teamId. If the user says "create an issue for the backend team" without a team ID, call linear_list_teams and match by name or key (the short prefix like "ENG"). Don't guess.

List issues → linear_list_issues with a teamId filter. Unfiltered lists can be huge — always scope. Add assigneeId or stateId when the user narrows further.

Read one issue → linear_get_issue with either the UUID or the identifier (ENG-123). Returns full body, state, assignee, team, labels, and recent comments.

Create an issue → linear_create_issue. Required: teamId, title. Confirm team + title with the user before calling. For priority, use integers: 1=Urgent, 2=High, 3=Medium, 4=Low, 0=none.

Change state (close, move to In Progress, etc) → state is referenced by stateId, not name. linear_list_states with the issue's teamId → pick the target state → linear_update_issue with that stateId. State type tells you what it represents: 'completed' closes, 'cancelled' rejects, 'started' / 'backlog' / 'unstarted' are in-flight.

Update other fields → linear_update_issue with only the changed fields. Note: labelIds REPLACES the existing label set — to add a label, first read the issue, then pass the combined set.

Comment → linear_comment_issue with issueId and a Markdown body. Issue IDs accept both UUID and identifier form.

Cross-project view → linear_list_projects to see what's active. Projects contain issues across teams; they're for milestone-style tracking.

Always show issue identifiers (ENG-123) when referring back — they're what users see in the Linear UI.