One contract, honest differences

Provider entry points

import { github } from "work-sdk/github";
import { linear } from "work-sdk/linear";
import { jira } from "work-sdk/jira";
import { azureDevOps } from "work-sdk/azure-devops";

Subpath exports keep provider implementations independently tree-shakeable. All adapters return the same WorkAdapter contract.

Capability matrix

GitHub Issues

github({
  owner: "acme",
  repo: "web",
  token: process.env.GITHUB_TOKEN,
})

The adapter excludes pull requests from issue results, maps open/closed reasons, verifies fields through readback, and supports multiple assignees. GitHub Projects fields are intentionally outside the portable issue contract.

Linear

linear({
  apiKey: process.env.LINEAR_API_KEY!,
  teamId: "team-id",
})

Linear uses cursor pagination, one assignee, native priorities, and team-specific workflow states. The adapter resolves state and label names against provider metadata before a mutation.

Jira Cloud

jira({
  baseUrl: "https://acme.atlassian.net",
  email: process.env.JIRA_EMAIL!,
  apiToken: process.env.JIRA_API_TOKEN!,
  projectKey: "ENG",
})

Jira status changes are transitions, not ordinary field updates. The adapter discovers available transitions and converts conservative text content to Atlassian Document Format.

Azure DevOps

azureDevOps({
  organization: "acme",
  project: "Platform",
  auth: { type: "entra", token: accessToken },
})

Azure DevOps uses WIQL for discovery and JSON Patch for mutation. Custom processes can redefine state and work-item type names, so the adapter exposes explicit normalization maps.

Provider escape hatches

Every normalized item, user, project, and comment can retain raw. Use it for reads that are not portable. For provider-specific writes outside the adapter contract, build a narrow custom tool instead of mutating raw and pretending the operation is normalized.