Linearis CLI
Linearis manages Linear issues and projects from the terminal, returns JSON and exposes focused command references to agents.
- 265 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The CLI reads and modifies Linear data with its API key, including issues, discussions and attachments.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/linearisDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The CLI reads and modifies Linear data with its API key, including issues, discussions and attachments.
This is third-party code. Review the repository files before installing.
What it does
Linearis provides terminal commands for everyday Linear work: finding issues, reading discussions and updating fields, projects or cycles. JSON-only output feeds subsequent steps without table parsing. Human-readable issue IDs and team names resolve to service identifiers. Help separates a compact overview from domain-specific detail, letting an agent discover only the commands needed.
Who it is for. Engineering leads using Linear who need structured issue selections and reviewable agent updates.
Good fit when
- Planning needs issue selections as JSON.
- A known issue needs its discussions and attachments inspected.
- Several issues need one proposed field change.
- An agent should discover only the relevant command domain.
Not a fit when
- You need unsupported workspace or integration administration.
- A human-facing interactive table is mandatory.
- Task access should be read-only but the token has broad write rights.
Example request
Find unassigned Platform issues and prepare a JSON assignment plan without applying changes.Limitations
Node.js 22 or newer and a Linear API key with the intended workspace permissions are required. Coverage targets daily operations rather than the full API, so verify unusual workflows in help first. Output is always JSON and may need a separate human-readable presentation. In batch updates null clears a field and unknown keys fail the request; review the entire change document before submitting it.
How to disable. Uninstall the CLI and any agent plugin, then revoke unused Linear credentials. Issues and discussions remain in the service.
FAQ
How do I get focused help?
Run `linearis usage`, followed by a domain such as `linearis issues usage`.
Must I look up an issue UUID?
No. Human-readable IDs such as ENG-42 are accepted. Inspect the target before updating.
Where is the login key stored?
Encrypted in `~/.linearis/token`. Keep that file out of reports.
What happens if a batch is invalid?
The transaction changes every issue or none. Inspect the error and correct the document.
How do I reply to a discussion?
Use the root thread ID, after listing and selecting the intended thread.
Discussion
No questions or reviews yet.
Related
CLI toolsLinear CLI
linear-cli
A Linear CLI for the terminal: list, start and create issues, PRs from a branch, JSON output and an agent skill, with git and jj support
A Linear MCP server with one tool and seven actions that takes about 500 tokens of context against 17,000
Go CLI for the Linear API built with agents in mind: issues, projects, comments, raw GraphQL, JSON output and a built-in MCP
An MCP server for Linear: issues, projects, cycles, milestones, documents and project updates via the GraphQL API
MCP server for Linear: the agent creates and updates issues, searches the tracker and adds comments through the Linear API
Jira CLI displays issues and sprints as tables or script data, keeping work-item queries in the terminal beside source code.
README in short
The CLI includes document and file operations. Separate skills and plugins guide Claude Code and Codex through the interface.