jq.
Setup
Create an API key using Linear setup.SKILL.md
The SKILL.md an agent reads withlinear installed.
- Rendered
- Raw
Available commandsThese commands are registered with this shell;
--help after a command or subcommand shows its usage.linearSupported commands
Runlinear <command> --help for the supported flags and operands.
This list is generated from Mirage’s registered command tree.
Usage
Find work
ENG-42 or a raw ID. --team accepts
a team key, name or ID. Use the list commands to discover project, cycle,
label and document IDs.
Update work
Descriptions and comment bodies can come from stdin. Issue creation requires
--team and --title; updates use the values explicitly supplied.
Issue relations
ISSUE RELATION RELATED, matching
linear-cli v3.1.0.
Relation names are case insensitive. blocked-by stores the inverse of
blocks. Deletion matches the exact stored direction, including related.
Both issue references are validated before contacting the service. Relation
commands accept full keys such as eng-42, Linear issue URLs, UUIDs and opaque
IDs of the form prefix_value. UUID and opaque ID operands extend the upstream
interface. An explicit issue is required for listing; branch inference and
bare issue numbers are unavailable in this virtual CLI.
Adding ENG-42 duplicate ENG-43 marks ENG-42 as the duplicate and ENG-43 as
its original. Linear applies the reserved Duplicate status through the relation
mutation. Mirage does not submit a separate state update. Removing that
relation lets Linear restore the previous status. See
Linear issue properties and the
June 18, 2026 changelog.
Add and delete return one normalized JSON relation. List returns an array,
outgoing relations first, followed by incoming relations, with all pages read.
Each row contains relation_id, type, direction, issue_id, issue_key,
related_issue_id, related_issue_key and related_issue_title. issue_id
always identifies the queried or first operand issue. Incoming blocks rows
have type blocked-by. Incoming duplicate rows keep type duplicate and
direction: "incoming"; the other issue is the duplicate in that case.
This JSON contract deliberately differs from upstream’s text output.
Deletion requires --yes, also spelled -y, -f, --force or --confirm.
The virtual CLI cannot prompt. The relation is looked up before confirmation,
so a missing relation still reports that failure first. Service errors and
false mutation success flags fail the command. Mutations are not retried
automatically, including when a response cannot confirm the outcome.
Failure output follows the virtual CLI’s conventions. Missing required operands
and unknown options exit 2. Extra operands, relation validation, missing issues
or relations, missing confirmation and service failures exit 1. Upstream instead classifies invalid
relation names and missing confirmation as usage errors with exit 2, and missing
entities with exit 3. Its authentication and availability failures use exits 4
and 5. Error wording also follows the virtual CLI rather than upstream text.
Behavior
The Linear VFS lets agents browse the same service as files. The CLI takes service IDs and its own config; piping a mounted file into a body does not make that mount the CLI’s account. Only the commands above are implemented. Commands, flags and JSON output follow this reference; Mirage does not promise full compatibility withschpet/linear-cli.
License
See compatibility and licenses.