Independent Linear CLI Reference

Linear CLI Commands, Setup and Issue Workflows

Find clearly labelled commands for installing Linear CLI tools and managing issues, branches, comments, pull requests and developer workflows from your terminal.

Browse Commands Installation Guide
  • Tool-labelled commands
  • Clear examples
  • No account required
Command Finder

What do you want to do?

Ready
CLI implementation schpet/linear-cli
Your command Terminal
linear issue mine
Lists unstarted Linear issues currently assigned to you.

Run this after authentication and project configuration.

View command details
Install · Authenticate · Run

From installation to your first issue list

Follow four commands in the correct order. Choose your installation method, authenticate your account, configure the project and list the work assigned to you.

Before authentication You will need a personal API key from your Linear account settings.
Read the complete installation guide
Guided setup schpet/linear-cli
Commands checked
  1. 01
    Install Install with Homebrew
    Required
    brew install schpet/tap/linear
  2. 02
    Authenticate Connect your Linear account
    API key
    linear auth login
  3. 03
    Configure Connect the current project
    Project
    linear config
  4. 04
    Run List your assigned issues
    First result
    linear issue mine

Expected result: a list of unstarted Linear issues assigned to your account.

Terminal · CLI · Workspace

What is Linear CLI, and how does it work?

Linear CLI is a general name for command-line tools that let you interact with Linear from your terminal. You can view, create and update work without repeatedly opening the Linear web application.

One name, multiple CLI tools

Linear CLI commands can differ between implementations. That is why every command on this website clearly shows the tool it belongs to.

  • Manage issues without leaving your terminal
  • Connect issue IDs with branches and pull requests
  • Use repeatable commands in developer workflows
Understand the different CLI tools
Command journey From terminal to Linear and back
Connected flow
  1. 01
    Your terminal You enter a task command
    linear issue mine
  2. 02
    CLI implementation The tool reads your command

    It uses your authentication and project configuration to understand the request.

  3. 03
    Linear workspace Linear processes the request

    The tool fetches information or updates the permitted workspace data.

  4. 04
    Terminal result The result returns to your screen

    Assigned issues loaded successfully

The exact behavior depends on the CLI implementation and the permissions connected to your Linear account.

From issue to pull request

Follow the complete Linear CLI workflow

These commands work together as one practical development path. Start with assigned work and finish with a pull request connected to the current Linear issue.

Browse workflow guides
Practical developer path Issue → Branch → Context → Pull Request
Linear authenticated Git repository GitHub CLI for PR
  1. 01
    Find

    Choose assigned work

    List the unstarted Linear issues currently assigned to your account.

    linear issue mine
    Result: issue selected Guide
  2. 02
    Start

    Begin the issue

    Start a specific issue and create or switch to its connected development branch.

    linear issue start ENG-123
    Result: branch ready Guide
  3. 03
    Review

    Keep issue context visible

    Read the issue associated with your current branch without leaving the terminal.

    linear issue view
    Result: context loaded Guide
  4. 04
    Complete

    Create the pull request

    Prepare a GitHub pull request using information from the issue connected to your current branch.

    linear issue pr
    Result: PR prepared Guide
Workflow complete

Your issue, development branch and pull request remain connected through the issue identifier.

schpet/linear-cli
Git · Agents · Automation

Use Linear CLI inside your developer workflow

Connect Linear issues with version control, pull requests, AI-agent workflows and structured terminal output.

Explore integration guides
01
Version control

Git and Jujutsu

schpet/linear-cli
linear issue start ENG-123

Connects an issue with development context by creating or switching to its working branch.

Configured Git or jj repository View guide
02
Pull requests

GitHub CLI

schpet/linear-cli
linear issue pr

Prepares a GitHub pull request using information from the Linear issue connected to your current branch.

GitHub CLI installed and authenticated View guide
03
AI workflow

Agent Skills

schpet/linear-cli
npx skills add schpet/linear-cli

Adds the included Linear CLI skill for compatible coding-agent environments.

Compatible agent and Node.js environment View guide
04
Structured output

Scripts and JSON

schpet/linear-cli
linear issue query --all-teams --json --limit 0

Returns machine-readable issue data that can be used inside scripts and automated workflows.

Authenticated CLI and workspace access View guide

These examples are labelled for schpet/linear-cli. Other Linear CLI implementations may use different commands.

Check · Identify · Fix

Find where your Linear CLI setup is failing

Run these checks in order. Each successful result confirms that one part of your installation is working correctly.

View all solutions
Linear CLI health check Run each command from top to bottom
schpet/linear-cli Ready to diagnose
  1. 01
    Installation check

    Is the Linear command available?

    Start here

    This confirms whether the CLI is installed and available in your terminal path.

    linear --version

    Expected: the installed version number appears.

    If it fails: the CLI may not be installed or available in your terminal path.

    Fix command not found
  2. 02
    Authentication check

    Can the CLI access your Linear account?

    API access

    Authenticate the CLI using a valid personal API key from an account with the required permissions.

    linear auth login

    Expected: authentication is accepted and stored.

    If it fails: verify the API key and your Linear account permissions.

    Fix authentication
  3. 03
    Configuration check

    Is the current project configured?

    Repository

    Configure the repository so the CLI knows which Linear team and workspace context to use.

    linear config

    Expected: project configuration is created or updated.

    If it fails: run it inside your repository and select an accessible Linear team.

    Fix configuration
  4. 04
    Workspace check

    Can the CLI load your assigned issues?

    Final check

    Request your unstarted assigned issues to confirm that authentication and workspace access work.

    linear issue mine

    Expected: your assigned unstarted issues are displayed.

    No issues shown? You may simply have no unstarted issues currently assigned to your account.

    Check an empty result

Using the npm installation? Replace linear with npx linear when running these checks.

Practical Linear CLI Reference

Understand Linear CLI before building your terminal workflow

A clear, tool-neutral explanation of Linear CLI commands, installation, authentication, integrations and automation.

What does Linear CLI mean?

Linear CLI is a general term used for a Linear command line interface. It allows developers to read or change Linear workspace data by entering commands in a terminal. Instead of repeatedly switching to a browser, a CLI for Linear can help users view issues, begin work, create branches, add comments and prepare pull requests from their development environment.

The term does not always refer to one identical application. Search results can contain different community-maintained tools, older packages and command-line projects with their own syntax. A command that works in one Linear issue tracker CLI may not work in another. For this reason, LinearCli.com labels every command with its relevant implementation rather than presenting unrelated commands as interchangeable.

Linear CLI installation, authentication and configuration

A reliable setup normally has three parts: installation, authentication and project configuration. The installation method depends on the selected CLI implementation. Some tools provide Homebrew packages, npm packages, Deno installation or downloadable binaries.

  • Install the correct package: confirm the package name and executable before copying any Linear CLI commands.
  • Authenticate securely: connect the tool using the supported login method or a personal Linear API key.
  • Configure the project: select the correct workspace, team and repository context before managing issues.

Follow the complete Linear CLI installation guide, then review authentication and configuration separately. Keeping these steps separate makes setup errors easier to identify.

Manage Linear issues from the terminal

The most useful Linear CLI workflow connects issue tracking with development work. A developer can list assigned issues, start a selected issue, create or switch to its branch, read the current issue context and prepare a pull request. This reduces unnecessary context switching while keeping the Linear issue ID connected to Git activity.

Linear GitHub integration workflows may also depend on the GitHub CLI and the branch naming rules used by the selected implementation. Before creating a pull request, confirm that the current repository is configured, the issue identifier is present and the required GitHub authentication is active.

Use the Linear CLI command reference for individual commands or follow the task-based workflow guides when several commands must be run in sequence.

Linear CLI for AI agents, JSON output and automation

Some Linear CLI implementations support structured JSON output, making issue data easier to use in shell scripts, development tools and automated processes. Machine-readable output can help an automation inspect issues, filter work or pass selected information to another approved step.

Linear CLI for AI agents can provide a controlled way for compatible coding agents to read issue context or perform permitted actions. The exact features depend on the installed CLI, its agent instructions and the permissions granted through the connected Linear account. Always review a command before allowing an automated workflow to create, update or delete data.

Our integration guides separate Git, GitHub, AI-agent and JSON automation workflows so users can understand the requirements of each one.

Linear CLI vs MCP: what is the difference?

The Linear CLI vs MCP question depends on how the user wants to work. A CLI is operated through terminal commands and fits naturally into shell scripts, Git workflows and manual developer tasks. MCP provides a structured connection that supported AI applications can use to access tools and context.

They are not automatically replacements for one another. A developer may prefer a CLI for direct, repeatable terminal work, while an AI-assisted workflow may use MCP or an agent-compatible CLI integration. The correct choice depends on the environment, permissions and level of automation required.

Read the complete Linear CLI vs MCP guide for a clear feature and workflow comparison.

API-key safety and Linear CLI troubleshooting

Treat a Linear API key like a password. Do not place it inside public code, screenshots, shared command history or a Git repository. Use the storage method supported by the selected CLI and grant only the access needed for the workflow.

If a command fails, check the installation, executable name, authentication, project configuration and account permissions in that order. Also confirm that the command belongs to the CLI implementation you actually installed. The Linear CLI troubleshooting guide covers command-not-found errors, authentication failures, missing configuration and empty issue results.

Browse Linear CLI commands Start the installation guide
Clear Answers · No Guesswork

Linear CLI frequently asked questions

Straightforward answers about Linear CLI tools, commands, installation, authentication, integrations and common errors.

01 What is Linear CLI used for?

Linear CLI is used to interact with Linear from a terminal. Depending on the installed implementation, users may list, view, create or update issues, work with projects, connect issue IDs to branches and prepare pull requests without repeatedly opening the Linear web interface.

02 Is there only one official Linear CLI?

No single command syntax is shared by every tool called Linear CLI. Search results may include the older @linear/cli package and several community-maintained implementations. Always confirm the package name, executable and command documentation for the tool you installed.

03 How do I install Linear CLI?

Installation depends on the selected implementation. Common methods include Homebrew, npm, Deno and downloadable binaries. Verify the exact package first, then follow the Linear CLI installation guide for that implementation.

04 Does Linear CLI require an API key?

Many Linear CLI tools use a personal Linear API key for authentication, while another implementation may support a different login method. Follow the authentication instructions for the exact tool and never place an API key in public code, screenshots or a Git repository.

05 Why does my terminal say “linear: command not found”?

The CLI may not be installed, its executable may not be available in your terminal path, or you may be using a local npm installation. For a local npm package, try the documented npx linear form. Use the command-not-found guide for complete checks.

06 Can I manage Linear issues entirely from the terminal?

Many common issue workflows can be completed from the terminal, including listing, viewing, creating, starting and updating issues. Available actions depend on the installed CLI implementation and the permissions of the connected Linear account.

07 Does Linear CLI work with GitHub pull requests?

Some implementations connect Linear issues with Git branches and GitHub pull requests. For example, a pull-request command may use the issue associated with the current branch and require GitHub CLI to be installed and authenticated. Check the GitHub integration guide before running it.

08 Can Linear CLI be used with AI coding agents?

Some Linear CLI implementations provide agent skills, structured JSON output or commands suitable for automated workflows. Compatibility depends on the agent environment and installed tool. Review permissions carefully before allowing an agent to create, update or delete Linear data.

09 What is the difference between Linear CLI and MCP?

Linear CLI uses commands entered in a terminal and works well for manual developer tasks, Git workflows and shell scripts. MCP provides a structured connection that supported AI applications can use to access tools and context. Read the Linear CLI vs MCP comparison for more detail.

10 Is LinearCli.com an official Linear website?

No. LinearCli.com is an independent documentation and command-reference website. It clearly labels CLI implementations so users can identify which package and command syntax each example belongs to.

Still experiencing an error? Run the four-step Linear CLI health check.
Open health check