use-linear

Essential Principles

• Use file-based flags for markdown. Pass descriptions and comment bodies via --description-file / --body-file, not inline -d / -b. Inline flags mangle multi-line content (literal \n, shell escaping). Reserve inline flags for single-line content.
• Pass --no-interactive on issue create. The CLI prompts interactively by default, which hangs an agent waiting on input; --no-interactive makes it fail loudly on missing required fields instead. Only create has this flag — update doesn't prompt for missing fields.
• Priority is numeric 1–4, descending. 1 = Urgent, 2 = High, 3 = Medium, 4 = Low. Not High/Low strings.
• Issue ID is optional on most commands — when omitted it's inferred from the current git branch (e.g. a branch like eng-123-fix-thing). Pass an explicit ID (ENG-123) when not on the issue's branch.
• list/mine vs query. issue list (alias mine) shows your issues and defaults to unstarted state. issue query is structured search across teams with --json; use it for anything beyond your own active work.
• --json for scripting. Use it on issue view and issue query when parsing or piping results.
• linear api is the escape hatch. Anything the typed commands don't cover, do via raw GraphQL.
• --help is the source of truth. The flag tables cover the v2.3.0 surface for one-shot use; if a flag is rejected or a subcommand is missing, run linear <cmd> --help.
• Confirm before mutations (create, update, delete, relation, PR). Don't mutate without user approval.

Prerequisites

command -v linear >/dev/null 2>&1