linear-sdk-cli 0.3.2 → 0.4.0

package/CHANGELOG.md

@@ -4,6 +4,18 @@ Release Please generates this file from Conventional Commits. Feature and fix pu
 not edit it directly; their squash-commit titles are the release-note source of truth. This project
 adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.4.0](https://github.com/zhendalf/linear-sdk-cli/compare/v0.3.3...v0.4.0) (2026-08-28)
+
+### Features
+
+- add custom view commands ([#38](https://github.com/zhendalf/linear-sdk-cli/issues/38)) ([fa99ae6](https://github.com/zhendalf/linear-sdk-cli/commit/fa99ae64ccbb23538bf53dc5fb8778e63ebd1b64))
+
+## [0.3.3](https://github.com/zhendalf/linear-sdk-cli/compare/v0.3.2...v0.3.3) (2026-08-28)
+
+### Bug Fixes
+
+- **deps:** publish @linear/sdk 92.0.0 upgrade ([eb7cb94](https://github.com/zhendalf/linear-sdk-cli/commit/eb7cb942a76ee810f1c79f614a369809258d2bc1))
+
 ## [0.3.2](https://github.com/zhendalf/linear-sdk-cli/compare/v0.3.1...v0.3.2) (2026-08-28)
 
 ### Bug Fixes

package/COVERAGE.md

@@ -1,17 +1,17 @@
 # SDK Coverage Audit
 
-Generated by `bun run audit:coverage`. Total LinearClient members: **470**.
+Generated by `bun run audit:coverage`. Total LinearClient members: **472**.
 
 | Status   | Count | Meaning                                         |
 | -------- | ----- | ----------------------------------------------- |
-| curated  | 102   | Has a first-class CLI command                   |
-| raw-only | 140   | Reachable via `linear api` (no bespoke command) |
-| excluded | 228   | Out of scope (admin/integration/SDK plumbing)   |
+| curated  | 107   | Has a first-class CLI command                   |
+| raw-only | 142   | Reachable via `linear api` (no bespoke command) |
+| excluded | 223   | Out of scope (admin/integration/SDK plumbing)   |
 
 Every member is classified — CI fails otherwise. `raw-only` members are still
 100% reachable through the raw GraphQL escape hatch; they simply lack a tailored command.
 
-## Curated (102)
+## Curated (107)
 
 - `agentSession` — issue
 - `agentSessions` — issue
@@ -27,6 +27,7 @@ Every member is classified — CI fails otherwise. `raw-only` members are still
 - `comments` — comment
 - `createAttachment` — attachment
 - `createComment` — issue
+- `createCustomView` — custom-view
 - `createCycle` — cycle
 - `createDocument` — document
 - `createFavorite` — favorite
@@ -42,10 +43,13 @@ Every member is classified — CI fails otherwise. `raw-only` members are still
 - `createRoadmap` — roadmap
 - `createTeam` — team
 - `createWebhook` — webhook
+- `customView` — custom-view
+- `customViews` — custom-view
 - `cycle` — cycle
 - `cycles` — cycle
 - `deleteAttachment` — attachment
 - `deleteComment` — comment
+- `deleteCustomView` — custom-view
 - `deleteDocument` — document
 - `deleteFavorite` — favorite
 - `deleteInitiative` — initiative
@@ -96,6 +100,7 @@ Every member is classified — CI fails otherwise. `raw-only` members are still
 - `unarchiveInitiative` — initiative
 - `unarchiveIssue` — issue
 - `updateComment` — comment
+- `updateCustomView` — custom-view
 - `updateCycle` — cycle
 - `updateDocument` — document
 - `updateInitiative` — initiative
@@ -116,7 +121,7 @@ Every member is classified — CI fails otherwise. `raw-only` members are still
 - `workflowState` — state
 - `workflowStates` — state
 
-## Excluded (228)
+## Excluded (223)
 
 - `agentActivities` — specialized/raw api only
 - `agentActivity` — specialized/raw api only
@@ -141,7 +146,6 @@ Every member is classified — CI fails otherwise. `raw-only` members are still
 - `createAgentSkill` — specialized/raw api only
 - `createContact` — specialized/raw api only
 - `createCsvExportReport` — specialized/raw api only
-- `createCustomView` — specialized/raw api only
 - `createCustomer` — specialized/raw api only
 - `createCustomerNeed` — specialized/raw api only
 - `createCustomerStatus` — specialized/raw api only
@@ -165,9 +169,7 @@ Every member is classified — CI fails otherwise. `raw-only` members are still
 - `createTimeSchedule` — specialized/raw api only
 - `createTriageResponsibility` — specialized/raw api only
 - `createViewPreferences` — specialized/raw api only
-- `customView` — specialized/raw api only
 - `customViewHasSubscribers` — specialized/raw api only
-- `customViews` — specialized/raw api only
 - `customer` — specialized/raw api only
 - `customerMerge` — specialized/raw api only
 - `customerNeed` — specialized/raw api only
@@ -181,7 +183,6 @@ Every member is classified — CI fails otherwise. `raw-only` members are still
 - `customerUpsert` — specialized/raw api only
 - `customers` — specialized/raw api only
 - `deleteAgentSkill` — specialized/raw api only
-- `deleteCustomView` — specialized/raw api only
 - `deleteCustomer` — specialized/raw api only
 - `deleteCustomerNeed` — specialized/raw api only
 - `deleteCustomerStatus` — specialized/raw api only
@@ -321,7 +322,6 @@ Every member is classified — CI fails otherwise. `raw-only` members are still
 - `unsuspendUser` — admin/enterprise (raw api only)
 - `updateAgentSession` — specialized/raw api only
 - `updateAgentSkill` — specialized/raw api only
-- `updateCustomView` — specialized/raw api only
 - `updateCustomer` — specialized/raw api only
 - `updateCustomerNeed` — specialized/raw api only
 - `updateCustomerStatus` — specialized/raw api only
@@ -347,7 +347,7 @@ Every member is classified — CI fails otherwise. `raw-only` members are still
 - `userRevokeSession` — admin/enterprise (raw api only)
 - `userUnlinkFromIdentityProvider` — admin/enterprise (raw api only)
 
-## Raw-only (140)
+## Raw-only (142)
 
 <details><summary>Show</summary>
 
@@ -486,6 +486,8 @@ Every member is classified — CI fails otherwise. `raw-only` members are still
 - `updateUserFlag`
 - `updateUserSettings`
 - `updateWorkflowState`
+- `usageAlert`
+- `usageAlerts`
 - `userDiscordConnect`
 - `userSessions`
 - `userSettings`

package/README.md

@@ -4,11 +4,11 @@
 [`@linear/sdk`](https://www.npmjs.com/package/@linear/sdk).**
 
 It's designed to be pleasant for humans _and_ dependable for scripts and agents. By default you
-get clean, aligned tables and detail views; add `--json` to any command for a stable,
+get clean, aligned tables and detail views; add `--json` to any data command for a stable,
 machine-readable shape. It's git-aware (the "current issue" comes from your branch name) and
 forgiving about input (`--assignee me`, team key `TES`, state and label by name). Anything the
 curated commands don't wrap is still reachable through a raw GraphQL escape hatch (`linear api`),
-so nothing in the Linear API is out of bounds.
+subject to the permissions granted to your Linear credential.
 
 ```sh
 linear issue list --assignee me --state started   # what's on my plate
@@ -19,6 +19,43 @@ linear issue list --json | jq -r '.[].identifier'  # ready for scripts
 > Design influenced by [`schpet/linear-cli`](https://github.com/schpet/linear-cli) (human-first,
 > git-aware) and [`linearis`](https://github.com/linearis-oss/linearis) (JSON-first for agents).
 
+## Why this project exists
+
+This project grew from strong ideas in earlier tools, especially the human-first, git-aware
+workflow credited above. Four requirements made a separate implementation the better fit for our
+use case:
+
+- **A smaller cloud deployment surface.** The reference implementation and its development path
+  centered on the full Deno runtime. Carrying that runtime into our cloud environments was more
+  infrastructure than the CLI warranted. This package ships its TypeScript source directly and
+  reuses the Bun runtime already present in our environment instead of packaging another runtime
+  for one tool. Later prebuilt releases moved that runtime into the artifact rather than
+  eliminating its footprint: for example, the
+  [v2.5.0 macOS ARM build](https://github.com/schpet/linear-cli/releases/tag/v2.5.0) expands to a
+  146 MB executable. Avoiding a heavyweight per-tool binary keeps cloud images and ephemeral agent
+  environments simpler and smaller.
+- **Lower invocation overhead for agent loops.** An interactive CLI may start once; an agent can
+  start it dozens or hundreds of times while completing one workflow, so even modest cold-start
+  latency compounds. A public
+  [startup-time report](https://github.com/schpet/linear-cli/issues/261) documented the difference
+  against a compiled alternative and identified repeated agent calls as the motivating case. The
+  Bun-first implementation makes process startup a product constraint and reduces that recurring
+  overhead in our deployment model.
+- **Alignment with Linear's official SDK.** The CLI is built directly on `@linear/sdk` and follows
+  its release cycle. Linear's SDK remains the source of truth for the API model, generated types,
+  connections, and transport; this project can focus on command design and stable output instead
+  of recreating official API machinery. A coverage audit catches additions, removals, and
+  classification drift among the SDK client's top-level members.
+- **Agent-native development and maintenance.** This project was built from scratch by coding
+  agents, and agents continue to implement features, update dependencies, regenerate
+  documentation, run verification, and prepare maintenance and release work. Versioned maintenance
+  policy, CI, coverage checks, and release automation provide the guardrails that make that model
+  repeatable rather than ad hoc.
+
+Together, those requirements made `linear-sdk-cli` the default for our deployments and automation
+workflows. That is a statement about fit, not a claim that earlier tools are obsolete; this CLI
+retains their best ideas and provides a careful compatibility and migration path.
+
 ## Highlights
 
 - **Human-first by default** — aligned tables, rendered Markdown, safe paging for long detail,
@@ -32,8 +69,8 @@ linear issue list --json | jq -r '.[].identifier'  # ready for scripts
 
 ## Install
 
-Requires [Bun](https://bun.sh) **1.1 or newer** and a Linear API key
-(Settings → Security & access → **Personal API keys**). The CLI ships as TypeScript and runs
+Requires [Bun](https://bun.sh) **1.1 or newer**. Authenticate with browser OAuth (the default), an
+invocation-scoped OAuth access token, or a personal API key. The CLI ships as TypeScript and runs
 directly on Bun — no build step, no bundle, no Node.
 
 ```sh
@@ -44,35 +81,12 @@ lin --help
 This installs two equivalent binaries: **`linear`** and the shorter **`lin`**. If you already
 have a different tool named `linear` on your `PATH`, just use `lin`.
 
-### If you already have `schpet/linear-cli` installed
-
-Both CLIs install a binary called **`linear`**, so whichever is earlier on your `PATH` wins and
-the other is silently shadowed — `linear --version` tells you which you got (`0.x` is this one,
-`2.x` is schpet's), and `which -a linear` lists both. Three ways out, pick one:
-
-- **Use `lin`.** It is ours alone; nothing of theirs claims it. Every example in this README works
-  with `lin` in place of `linear`. Zero-risk for the transition week.
-- **Keep theirs reachable as `linear-schpet`** and let ours have `linear`:
-
-  ```sh
-  # installed with deno: reinstall under a new name, then drop the old one
-  deno install -A --reload -f -g -n linear-schpet jsr:@schpet/linear-cli
-  deno uninstall -g linear
-  # installed with homebrew (schpet/tap/linear): keep the keg, relink under a new name
-  brew unlink schpet/tap/linear
-  ln -s "$(brew --prefix)/opt/linear/bin/linear" ~/.local/bin/linear-schpet   # any dir on your PATH
-  # installed with npm/bun globally: rename the shim in place
-  mv "$(command -v linear)" "$(dirname "$(command -v linear)")/linear-schpet"
-  ```
+### Existing `linear` installations
 
-  (A package-manager upgrade of theirs may put `linear` back; re-run the line for your channel.)
-
-- **Uninstall theirs** once you no longer need it. Your credentials survive: they are in the OS
-  keyring under the same service and account, and we read them — see [Authentication](#authentication).
-
-Their project-pinned install (`bun add -D @schpet/linear-cli`, run as `bunx linear`) does not
-collide with a global install of ours; inside such a project `bunx linear` is theirs and
-`linear`/`lin` on your `PATH` is ours.
+Another CLI may already provide a binary named `linear`; whichever appears first on `PATH` wins.
+Use this package's collision-free **`lin`** alias while evaluating or migrating. See
+[`MIGRATING.md`](MIGRATING.md) for side-by-side installation, credential and config compatibility,
+and the few commands whose behavior intentionally differs.
 
 <details>
 <summary>Run from source instead</summary>
@@ -88,7 +102,7 @@ bun run src/bin/linear.ts --help     # or: bun run dev -- --help
 ## Quickstart
 
 ```sh
-export LINEAR_API_KEY=lin_api_xxxxxxxx     # quickest way to get going
+linear auth login                          # browser OAuth; or set LINEAR_API_KEY
 linear whoami                              # confirm you're connected
 
 linear issue list --assignee me --state started        # my in-progress work
@@ -141,10 +155,10 @@ with `LINEAR_OAUTH_REDIRECT_URI`. No OAuth client secret is embedded, accepted,
 
 For a personal API key, `auth login --key -` reads stdin, validates the viewer/workspace, stores the
 key in the system keyring by default, and writes only a marker to the config. `--plaintext` is an
-API-key-only compatibility option. API-key entries use `account = <workspace slug>`, matching
-[schpet/linear-cli](https://github.com/schpet/linear-cli). Passing a key as `--key <value>` works but
-warns because argv is visible to other processes. `auth migrate` moves legacy plaintext keys into
-the keyring, and `auth token` exports stored API keys only; OAuth tokens are never printed.
+API-key-only compatibility option. API-key entries use `account = <workspace slug>`, preserving
+compatibility with existing keyring profiles. Passing a key as `--key <value>` works but warns
+because argv is visible to other processes. `auth migrate` moves legacy plaintext keys into the
+keyring, and `auth token` exports stored API keys only; OAuth tokens are never printed.
 
 ### Apps, agents, and service accounts
 
@@ -269,8 +283,8 @@ linear issue pr --json | jq -r .url        # the created PR URL is the only thin
 ```
 
 `issue describe` prints a whole commit message — `TES-123 Title`, a blank line, then two git
-trailers, `Linear-issue: Fixes TES-123` and `Linear-issue-url: <url>` (the same text
-schpet/linear-cli prints, so `git interpret-trailers` and jj read it back). The magic word sits
+trailers, `Linear-issue: Fixes TES-123` and `Linear-issue-url: <url>` (compatible with existing
+workflows, so `git interpret-trailers` and jj read it back). The magic word sits
 right before the id, which is where Linear's
 [git integration](https://linear.app/docs/github#link-prs-and-commits) reads it, so the issue is
 linked — and closed on merge — when the commit lands; `-r` swaps in `References` to link without
@@ -306,6 +320,35 @@ Status updates (`project-update`/`pu`, `initiative-update`/`iu`) take the body f
 `--body-file <path>` (`-` for stdin), or `--editor` (`$EDITOR`), plus an optional
 `--health <onTrack|atRisk|offTrack>`.
 
+**Custom views** — create and inspect saved Issue, Project, and Initiative filters without writing
+GraphQL. A filter is the current Linear `IssueFilter`, `ProjectFilter`, or `InitiativeFilter` JSON
+object; pass it inline or from a file/stdin. The selected `--type` decides which typed SDK input
+field receives it, and an omitted filter becomes `{}` so the view type still round-trips.
+
+```sh
+linear custom-view list
+linear cv create --name "Urgent" --type issue \
+  --filter '{"priority":{"eq":1}}' --shared
+linear cv view 01234567-89ab-cdef-0123-456789abcdef
+linear cv results 01234567-89ab-cdef-0123-456789abcdef --all
+linear cv update 01234567-89ab-cdef-0123-456789abcdef \
+  --filter-file issue-filter.json --personal
+linear cv delete 01234567-89ab-cdef-0123-456789abcdef --yes
+```
+
+Create can attach a view with one of `--scope-team`, `--scope-project`, or `--scope-initiative`.
+Linear marks project/initiative scope fields internal on update, so update exposes only the public
+team scope (`--scope-team` / `--clear-team-scope`) and never rewrites an unspecified scope. View
+references are UUID-only: names are not unique, and Linear's `customViews` query intentionally
+omits project- and initiative-scoped views. Those scoped views remain accessible by UUID. Initiative
+views require an eligible Linear plan.
+
+```sh
+linear cv list --json | jq -r '.[] | [.id, .name, .type] | @tsv'
+linear cv results 01234567-89ab-cdef-0123-456789abcdef --json
+# [{"type":"issue","id":"…","identifier":"ENG-42","name":"Fix login","url":"…"}]
+```
+
 ## Command overview
 
 Every group has `--help` with full options and (for the busy ones) an Examples section. Aliases
@@ -327,6 +370,7 @@ are shown in parentheses. For a machine-readable tree of _every_ command, run
 | **`document`** (`doc`)         | `list` · `view` · `create` · `update` · `delete`                                                                                                                                                                                                                                    |
 | **`attachment`** (`at`)        | `list` · `create` · `delete`                                                                                                                                                                                                                                                        |
 | **`favorite`** (`fav`)         | `list` · `add` · `remove`                                                                                                                                                                                                                                                           |
+| **`custom-view`** (`cv`)       | `list` · `view` · `results` · `create` · `update` · `delete`                                                                                                                                                                                                                        |
 | **`initiative`** (`init`)      | `list` · `view` · `create` · `update` · `archive` · `delete`                                                                                                                                                                                                                        |
 | **`initiative-update`** (`iu`) | `create` · `list` (initiative status updates, with `--health`)                                                                                                                                                                                                                      |
 | **`roadmap`** (`rm`)           | `list` · `view` · `create` · `update` · `delete` &nbsp;<sup>†</sup>                                                                                                                                                                                                                 |
@@ -458,15 +502,15 @@ versioned maintenance policy. See [`skills/README.md`](skills/README.md) for the
 contract.
 
 The CLI skill is self-contained: an agent that has only the skill and no CLI is told to
-`bun add -g linear-sdk-cli`, and one arriving from `schpet/linear-cli` is told not to re-enter a
-key before `linear auth status`, since existing credentials are found. `linear commands --json`
-gives it the full command surface at runtime, so the reference docs are a starting point, not a
-cage.
+`bun add -g linear-sdk-cli`, and a migrating user is told to check `linear auth status` before
+re-entering a key because compatible credentials are discovered automatically. `linear commands
+--json` gives it the full command surface at runtime, so the reference docs are a starting point,
+not a cage.
 
 ## Coming from linear-cli
 
 > The full guide — install without a collision, credentials found without a re-login, config
-> read from the same files, and the three places the two CLIs would silently differ — is
+> compatibility, and the places where behavior intentionally differs — is
 > [`MIGRATING.md`](MIGRATING.md). This section is the flag-level cheat sheet.
 
 If your fingers or your scripts learned the other `linear-cli`, most of its spellings work here
@@ -524,12 +568,11 @@ Precedence, highest first — `linear config` prints each value with the tier an
 1. the flag (`--team`, `--workspace`, `--sort`)
 2. the environment (`LINEAR_TEAM`/`LINEAR_TEAM_ID`, `LINEAR_WORKSPACE`, `LINEAR_ISSUE_SORT`)
 3. the **project config**: the first file found walking up from the working directory, checking in
-   each directory `linear.toml`, then `.linear.toml`, then `.config/linear.toml` — the same
-   names and order as [schpet/linear-cli](https://github.com/schpet/linear-cli), so a repo set
-   up with its `linear config` (which writes `<git root>/.config/linear.toml`) is picked up as-is
+   each directory `linear.toml`, then `.linear.toml`, then `.config/linear.toml`; compatible
+   existing project configuration is picked up as-is
 4. the **user config**, `~/.config/linear/config.toml` (`$XDG_CONFIG_HOME` honored)
-5. schpet/linear-cli's **global config**, `~/.config/linear/linear.toml` — read for non-secret
-   settings only, so a migrating user's defaults carry over
+5. the legacy **global config**, `~/.config/linear/linear.toml` — read for non-secret settings
+   only, so a migrating user's defaults carry over
 
 Keys: `team` (or `team_id`), `workspace`, and `sort` (or `issue_sort`). You can write these from
 the CLI — comments and layout in an existing file are preserved, and the write is atomic:
@@ -586,8 +629,8 @@ Use `linear schema` to discover types and fields first, then reach for `linear a
 ### Coverage
 
 Coverage of the SDK is **measured, not asserted.** `linear api` reaches the full GraphQL API, and
-a generated audit ([COVERAGE.md](./COVERAGE.md)) classifies every one of the ~460 `LinearClient`
-members as `curated` (a first-class command), `raw-only` (reachable via `linear api`), or
+a generated audit ([COVERAGE.md](./COVERAGE.md)) classifies every current `LinearClient` member as
+`curated` (a first-class command), `raw-only` (reachable via `linear api`), or
 `excluded` (admin/integration/SDK plumbing). CI fails on any drift from the committed snapshot, so
 the claim stays honest as the SDK evolves.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "linear-sdk-cli",
-  "version": "0.3.2",
+  "version": "0.4.0",
   "description": "Ergonomic command-line interface for Linear, built on @linear/sdk",
   "type": "module",
   "license": "MIT",
@@ -70,7 +70,7 @@
   },
   "dependencies": {
     "@inquirer/prompts": "^8.7.0",
-    "@linear/sdk": "^91.0.0",
+    "@linear/sdk": "^92.0.0",
     "commander": "^15.0.0",
     "graphql": "^17.0.2",
     "picocolors": "^1.1.1",

package/skills/linear-sdk-cli/SKILL.md

@@ -317,6 +317,14 @@ linear config init
 linear config set
 linear config show
 
+linear custom-view
+linear custom-view create
+linear custom-view delete
+linear custom-view list
+linear custom-view results
+linear custom-view update
+linear custom-view view
+
 linear cycle
 linear cycle create
 linear cycle current
@@ -481,6 +489,7 @@ prints the same). These are supplementary — `--help` on any command is authori
 - [comment](references/comment.md) — Manage comments
 - [completion](references/completion.md) — Output a shell completion script
 - [config](references/config.md) — Show the resolved configuration (secrets redacted)
+- [custom-view](references/custom-view.md) — Create and manage saved custom views
 - [cycle](references/cycle.md) — Work with cycles
 - [document](references/document.md) — Work with documents
 - [favorite](references/favorite.md) — Manage your favorites

package/skills/linear-sdk-cli/references/custom-view.md

@@ -0,0 +1,205 @@
+# linear custom-view
+
+> Create and manage saved custom views
+
+Group alias: `cv`
+
+_Generated from `linear commands --json`. `linear custom-view --help` (or `<subcommand> --help`) is authoritative._
+
+Every command also accepts the global flags `-j/--json`, `--no-input`, `-y/--yes`, `-q/--quiet`, `--workspace <slug>`, `--api-key <key>`, `--access-token <token>`, `-t/--team <key>`, `-n/--limit <n>`, `--all`, `-f/--fields <a,b,c>`, `--no-ansi` (alias `--no-color`), and `--debug`. Only command-specific options are listed below.
+
+### `linear custom-view`
+
+Create and manage saved custom views
+
+Aliases: `cv`
+
+```
+linear custom-view [options]
+```
+
+**Output (`--json`)**: a bare object — runs `custom-view view` by default
+
+```text
+id: string
+name: string
+type: string
+shared: boolean
+owner: {id: string, displayName: string} | null
+team: {id: string, key: string, name: string} | null
+slugId: string
+updatedAt: string
+description: string | null
+filter: object
+color: string | null
+icon: string | null
+creator: {id: string, displayName: string} | null
+createdAt: string
+archivedAt: string | null
+```
+
+### `linear custom-view create`
+
+Create an issue, project, or initiative custom view
+
+Aliases: `new`
+
+```
+linear custom-view create [options]
+```
+
+| Option                          | Description                                    |
+| ------------------------------- | ---------------------------------------------- |
+| `--name <name>`                 | view name                                      |
+| `--type <type>`                 | entity type                                    |
+| `--owner <who>`                 | owner (me\|email\|name\|id)                    |
+| `--color <hex>`                 | icon color                                     |
+| `--icon <icon>`                 | emoji or decorative icon identifier            |
+| `--scope-team <key\|name\|id>`  | attach the view to a team                      |
+| `--scope-project <id\|name>`    | attach the view to a project                   |
+| `--scope-initiative <id\|name>` | attach the view to an initiative               |
+| `-d, --description <text>`      | view description                               |
+| `--description-file <path>`     | read description from a file ('-' = stdin)     |
+| `--filter <json>`               | typed Linear filter as a JSON object           |
+| `--filter-file <path>`          | read the filter JSON from a file ('-' = stdin) |
+| `--shared`                      | share the view with the workspace              |
+| `--personal`                    | make the view owner-only                       |
+
+**Output (`--json`)**: a receipt object
+
+```text
+id: string
+name: string
+type: string
+shared: boolean
+slugId: string
+```
+
+### `linear custom-view delete`
+
+Delete a custom view by UUID
+
+Aliases: `rm`
+
+```
+linear custom-view delete [options] <id>
+```
+
+**Output (`--json`)**: a receipt object
+
+```text
+id: string
+name: string
+deleted: boolean
+```
+
+### `linear custom-view list`
+
+List accessible workspace and team custom views
+
+Aliases: `ls`
+
+```
+linear custom-view list [options]
+```
+
+**Output (`--json`)**: a bare array of objects
+
+```text
+id: string
+name: string
+type: string
+shared: boolean
+owner: {id: string, displayName: string} | null
+team: {id: string, key: string, name: string} | null
+slugId: string
+updatedAt: string
+```
+
+### `linear custom-view results`
+
+List issues, projects, or initiatives matched by a view UUID
+
+Aliases: `items`
+
+```
+linear custom-view results [options] <id>
+```
+
+**Output (`--json`)**: a bare array of objects
+
+```text
+type: string
+id: string
+identifier: string | null
+name: string
+url: string
+```
+
+### `linear custom-view update`
+
+Update mutable fields on a custom view UUID
+
+Aliases: `edit`
+
+```
+linear custom-view update [options] <id>
+```
+
+| Option                         | Description                                    |
+| ------------------------------ | ---------------------------------------------- |
+| `--name <name>`                | new name                                       |
+| `--owner <who>`                | new owner (me\|email\|name\|id)                |
+| `--color <hex>`                | new icon color                                 |
+| `--clear-color`                | clear the icon color                           |
+| `--icon <icon>`                | new icon                                       |
+| `--clear-icon`                 | clear the icon                                 |
+| `--clear-description`          | clear the description                          |
+| `--scope-team <key\|name\|id>` | set the public team scope                      |
+| `--clear-team-scope`           | clear the public team scope                    |
+| `-d, --description <text>`     | new description                                |
+| `--description-file <path>`    | read description from a file ('-' = stdin)     |
+| `--filter <json>`              | typed Linear filter as a JSON object           |
+| `--filter-file <path>`         | read the filter JSON from a file ('-' = stdin) |
+| `--shared`                     | share the view with the workspace              |
+| `--personal`                   | make the view owner-only                       |
+
+**Output (`--json`)**: a receipt object
+
+```text
+id: string
+name: string
+type: string
+shared: boolean
+slugId: string
+```
+
+### `linear custom-view view`
+
+Show a custom view by UUID
+
+Aliases: `show`
+
+```
+linear custom-view view [options] <id>
+```
+
+**Output (`--json`)**: a bare object
+
+```text
+id: string
+name: string
+type: string
+shared: boolean
+owner: {id: string, displayName: string} | null
+team: {id: string, key: string, name: string} | null
+slugId: string
+updatedAt: string
+description: string | null
+filter: object
+color: string | null
+icon: string | null
+creator: {id: string, displayName: string} | null
+createdAt: string
+archivedAt: string | null
+```

package/src/cli.ts

@@ -29,6 +29,7 @@ import { registerRoadmap } from "./commands/roadmap.js";
 import { registerNotification } from "./commands/notification.js";
 import { registerOrganization } from "./commands/organization.js";
 import { registerWebhook } from "./commands/webhook.js";
+import { registerCustomView } from "./commands/custom-view.js";
 import { registerOpen } from "./commands/open.js";
 import { registerCommands, registerSchema } from "./commands/discover.js";
 import { Context, type GlobalOptions } from "./context.js";
@@ -87,6 +88,7 @@ export function createProgram(): Command {
   registerNotification(program);
   registerOrganization(program);
   registerWebhook(program);
+  registerCustomView(program);
 
   // Discovery commands need the fully-built program tree, so register them last.
   registerCommands(program);