| name | linear |
| description | Manage Linear issues via the local streamlinear-cli wrapper. Use when the user asks to search Linear issues, inspect a ticket, change status, priority, or assignee, add comments, create issues, list teams and workflow states, or run GraphQL queries against Linear. |
| compatibility | Requires streamlinear-cli on PATH and a Linear API token available via ~/.config/streamlinear/token (managed by sops-nix in this setup) or LINEAR_API_TOKEN. |
Linear
Use the local streamlinear-cli wrapper for Linear work.
Before you start
- Never print or expose the API token.
- If you need to discover available teams or workflow states first, run:
streamlinear-cli teams
- IDs can be provided as:
- short IDs like
ABC-123
- full Linear issue URLs
- UUIDs
Search issues
streamlinear-cli search
streamlinear-cli search "auth bug"
streamlinear-cli search --state "In Progress"
streamlinear-cli search --assignee me
streamlinear-cli search --assignee user@example.com
streamlinear-cli search --team ENG
streamlinear-cli search --state "In Progress" --assignee me --team ENG
Get issue details
streamlinear-cli get ABC-123
streamlinear-cli get "https://linear.app/acme/issue/ABC-123"
Update an issue
streamlinear-cli update ABC-123 --state Done
streamlinear-cli update ABC-123 --state "In Progress"
streamlinear-cli update ABC-123 --priority 1
streamlinear-cli update ABC-123 --assignee me
streamlinear-cli update ABC-123 --assignee user@example.com
streamlinear-cli update ABC-123 --assignee null
streamlinear-cli update ABC-123 --state Done --priority 3
Comment on an issue
streamlinear-cli comment ABC-123 "Fixed in commit abc123"
streamlinear-cli comment ABC-123 "Blocked on dependency update"
Create an issue
streamlinear-cli create --team ENG --title "Bug: Login fails"
streamlinear-cli create --team ENG --title "Bug: Login fails" --body "Users see an error on submit"
streamlinear-cli create --team ENG --title "Urgent fix" --priority 1
Raw GraphQL
Use this only when the standard actions are not enough.
streamlinear-cli graphql "query { viewer { name email } }"
streamlinear-cli graphql "query { projects { nodes { id name } } }"
Working pattern
- Discover teams/states when unclear with
streamlinear-cli teams
- Search first when the user refers to an issue vaguely
- Use
get before mutating when you need confirmation about current state
- Prefer targeted commands (
search, get, update, comment, create) over raw GraphQL
- Use GraphQL only for unsupported or highly specific queries