@parke.dev/pi-linear

Linear issues: read, search, comment on and transition tickets, as a Pi extension.

pi install npm:@parke.dev/pi-linear      # once published

What it does

Run linear_status first — it reports what is reachable, which credential is in use, and what this package deliberately will not do.

Credentials

For most interactive coding-agent users, the simplest setup is Linear's official hosted MCP server at https://mcp.linear.app/mcp: it supports browser OAuth 2.1 with dynamic client registration and needs no copied API key. Use that through pi-mcp-adapter instead of this extension when OAuth is the priority; loading both creates duplicate tool surfaces.

This REST extension remains useful for its smaller curated tool surface and explicit write confirmations. Its cleanest setup is interactive and keeps the secret out of the model conversation:

/linear-login

The command uses a masked prompt, validates the credential with the provider, then stores it with 0600 permissions.

$LINEAR_API_KEY (or $LINEAR_TOKEN), else ~/.pi/agent/integration-auth.json — written by /linear-login, 0600, beside Pi's own auth.json. A bare pi session and Pi extensions read the same file, so you connect once.

Get a key from Linear → Settings → API.

A GraphQL failure arrives as HTTP 200

Linear returns { errors: [...] } with a 200 status. Every call here checks it — without that, a permissions failure becomes an empty issue list, which reads as "you have no issues" rather than "the integration could not read them".

Writes ask first

Every write calls Pi's ctx.ui.confirm and shows you the full text before anything leaves your machine.

| Where you are | What happens | | ------------------------------------- | -------------------------------------------------------------------------------------- | | A Pi TUI session | a confirmation dialog | | A host app speaking Pi's RPC protocol | the request arrives as extension_ui_request; the app renders it however it likes | | pi -p (non-interactive) | refused, because nobody can be asked. Pass yes: true if you have already decided |

That last row matters: in print mode ctx.ui.confirm returns false without prompting, so a naive implementation would report "you declined" when nobody was ever asked. This one tells you which happened.

linear_connect has no yes escape hatch, deliberately. A flag that skips confirmation on a credential-storing tool is one injected instruction away from an attacker's token being used for all your writes.

What it deliberately will not do

Published in describe().refuses, and a test asserts each is genuinely absent from the source — so the list cannot become a lie. Run linear_status to see it.

Using it from your own code

src/ has no Pi dependency, so a UI can render its view models without going through a tool call:

import { LINEAR_DESCRIPTION } from "@parke.dev/pi-linear";

LINEAR_DESCRIPTION declares every segment, every field on a row, and every refusal — so a UI can render a panel for this provider with no provider-specific code, and a conformance test fails the build if it stops being true.

Status words, never colour alone

Every status is a word a reader can read. Colour is decoration on top. A red dot says nothing to a screen reader, and nothing to someone who cannot distinguish it from the green one.