A sample Next.js app that talks to Linear using Vercel Connect for credentials, and displays your overdue or soon to breach SLA tasks.

Clicking Deploy clones this repo, walks you through creating a Linear connector, and writes its UID into the CONNECTOR env var. After it deploys, open the app and click Authorize Linear to grant access.

When Linear hasn't been authorized yet, the app shows an "Authorize Linear" button. After consent, it renders a small dashboard built from the Linear GraphQL API:

• Due soon / Overdue — open issues due in the next 14 days (works on every workspace).
• SLA at risk — issues that are breached / at high or medium SLA risk. Linear SLAs require the Business plan and per-team configuration, so this panel shows an empty state if SLA isn't set up.
• Assigned to me — your active issues.
• Teams — the teams in your workspace.

Browser ──▶ Next.js (server)
                │  getTokenResponse("oauth/linear", { subject:{ type:"user", id }, scopes:["read"] })
                ▼
          Vercel Connect ──▶ Linear OAuth
                │  short-lived Linear token
                ▼
          api.linear.app/graphql  (Authorization: Bearer <token>)

• lib/linear.ts — getLinearConnection() exchanges the deployment's Vercel OIDC token for a Linear token. If the user hasn't authorized, it returns needs_auth; the UI then links to /api/linear/authorize.
• app/api/linear/authorize/route.ts — calls startAuthorization() and redirects the browser to the hosted consent screen. Vercel completes the OAuth handshake server-side, then redirects back to /?connected=1. There is no app-side callback step — the next token request just works.
• app/api/linear/disconnect/route.ts — revokeToken() tears down the grant.

No Linear secrets ever live in the app or its environment variables.

Either directly deploy using the 1-click deploy button above, that deploys to your Vercel account, or follow these steps below to get started locally.

Prerequisites: Vercel CLI (npm i -g vercel), Node ≥ 24, and a Linear workspace you can authorize.

1. Link a Vercel project (issues the OIDC token the SDK authenticates with):

   vercel link

2. Create the Linear connector (opens a browser to authorize Linear), then attach it to the project:

   vercel connect create linear            # or: vercel connect create mcp.linear.app --name linear
   vercel connect list                     # note the UID it was given
   vercel connect attach <connector-uid>

   The connector UID varies — a managed Linear connector looks like linear/yellow-house, a Custom OAuth one like oauth/linear. Whatever yours is, set it as CONNECTOR in .env.local (step 3). If CONNECTOR doesn't match a connector linked to the project, the app shows a "connector not found" hint with the fix.

3. Pull env vars (writes VERCEL_OIDC_TOKEN into .env.local):

   vercel env pull

   The OIDC token is short-lived — re-run vercel env pull if you see auth errors during local dev.

4. Install and run:

   pnpm install
   pnpm dev

   Open http://localhost:3000, click Authorize Linear, approve, and you're in.

Copy .env.local.example for reference. Vars:

Note on the demo user id: this template has no auth system, so it uses a single stable LINEAR_DEMO_USER_ID as the token subject. That keeps the consent grant persistent across reloads. In a real app, replace it with your signed-in user's id (getSubject() in lib/connect.ts) so each user authorizes Linear for themselves.

Push to a repo and import it on Vercel, or:

vercel deploy

On Vercel, the OIDC token is injected automatically — no vercel env pull needed in production. Make sure the connector is attached to the deployed project's environment (vercel connect attach oauth/linear).

• Write data: add scopes (write, issues:create) in lib/connect.ts and re-authorize, then send GraphQL mutations through linearGraphQL().
• More views: the dashboard query in lib/linear.ts uses aliased issues(...) lists — add another alias with a different Linear filter (e.g. by cycle, project, or label).
• Per-user auth: wire getDemoUserId() to your session.

Built with @vercel/connect. See the Vercel Connect docs and the Linear API docs.