Our take
Activeregular commits and releases- Activity
- 58
- Community
- 35
- Issues
- 46
- Pull requests
- 25
+0 stars in the last 30 days
- Slower to merge pull requests than 98% of the projects we track
linctl is an actively maintained, broad Linear CLI with useful automation interfaces, but its development is heavily concentrated in one contributor.
Good fit if
- Your team uses Linear and wants issue and project workflows available from the terminal.
- You need JSON-based scripting or agent access, including GraphQL and MCP operations.
- Go and the MIT license suit your environment and adoption requirements.
Look elsewhere if
- You need an interface independent of Linear or support for a different issue tracker.
- Your team requires development ownership to be spread across contributors, since most project contributions come from one person.
- You need a project with demonstrated fast issue resolution: recent issue closures are sparse, and merged pull requests have taken a relatively long time on average.
All health signals
| Last commit | 2026-10-13 (1 day ago) |
|---|---|
| Commits, last 90 days | 17 |
| Releases, last 12 months | 11 (latest v0.1.12, 2026-08-23) |
| Contributors | 11 (top contributor: 84% of commits) |
| Issues closed, last 90 days | 1 |
| Pull requests merged, last 90 days | 3 (typically merged in 33 days) |
| Project age | 15 months |
Checked on 2026-10-15 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
145Forks
26Change since Nov 17, 2026: 0 stars·0 forks
Overview
linctl is a command-line interface for Linear’s API, implemented in Go with Cobra. It brings common issue, project, team, user, label, and comment workflows into the terminal, so people and automation can work with Linear without relying on its web interface for every operation.
The project is explicitly designed with agents in mind as well as human users. JSON output, raw GraphQL access, and a dynamic MCP namespace make it useful for scripts and agent workflows, while interactive authentication and table output support direct use by people.
Key Features
- List, search, create, update, assign, and relate issues, including cycles, labels, projects, and parent/sub-issue links.
- Manage projects, teams, workflow states, users, labels, and issue comments.
- Authenticate with a Linear personal API key, with environment-variable overrides and optional
passstorage. - Produce table, plaintext, or JSON output for interactive use and automation.
- Execute arbitrary Linear GraphQL queries and mutations using the configured authentication context.
- Discover and call schema-backed operations through the
linctl mcpcommand namespace. - Inspect agent sessions on issues and mention delegated or active agents.
- Filter and sort listings by creation time, status, assignee, team, and other criteria.
Use Cases
- An engineer can update issue status, assign work, add comments, and attach a pull request from a terminal during development.
- An agent workflow can read Linear issues as JSON, make supported updates, or use MCP and GraphQL for operations beyond the built-in commands.
- A team can script recurring triage or reporting tasks by combining list commands with JSON output and tools such as
jq. - A project lead can review projects, milestones, team states, and issue relationships without manually navigating each record in Linear.
What you need
Detected in the repository
- Go 1.23.0 or newer (from go.mod)
- Automated checks on GitHub Actions
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Install with Homebrew and authenticate with a Linear personal API key:
brew tap dorkitude/linctl
brew install linctl
linctl auth
See the README for other installation options, command details, and configuration.
Considerations
- By default, issue and project listings are limited to items created in the last six months. Issue lists and searches also omit completed and canceled items unless the relevant flags are supplied, so historical or complete reports need explicit filters.
- The project is active, with regular commits and releases, but contributor activity is concentrated heavily in one person. Recent issue closures are limited, and pull requests have a relatively long median time to merge, which may matter when evaluating support expectations.
- Building from source requires Go 1.23.0 or later according to the project’s module metadata; prebuilt installation options are also documented.
- The CLI can create, update, delete, and permanently delete records, so automation should use appropriate credentials and take care with mutation commands.
- The project is licensed under MIT. Review the license and your organization’s policies before adopting it.
Found this useful?
Share it with someone who would like linctl.