Linear

Use linear in twins and put this configuration under seed_config.linear. Linear issue tracker with teams, projects, cycles, issues, labels, and comments.

Example seed

This is the complete Scenario request body for creating a Scenario. You can also import it with arga test-runner scenarios import --file scenario.json.

{
  "name": "Linear eval fixture",
  "twins": [
    "linear"
  ],
  "seed_config": {
    "linear": {
      "uploads": [
        {
          "id": "11111111-2222-4333-8444-555555555555",
          "filename": "review.txt",
          "content_type": "text/plain",
          "content_base64": "UmV2aWV3IGNvbXBsZXRlLgo="
        }
      ],
      "teams": [
        {
          "key": "ENG",
          "name": "Engineering"
        }
      ],
      "projects": [
        {
          "name": "Q3 Roadmap",
          "team_key": "ENG",
          "description": "Coordinate the quarterly release",
          "content": "## Release plan\n\nConfirm readiness and document the rollout.",
          "member_ids": [
            "user_twin_me",
            "user_twin_teammate"
          ],
          "state": "started"
        }
      ],
      "issues": [
        {
          "team_key": "ENG",
          "title": "Wire the new auth flow",
          "description": "Steps to reproduce\u2026",
          "priority": 2,
          "labels": [
            "bug"
          ],
          "project": "Q3 Roadmap"
        }
      ],
      "comments": [
        {
          "id": "comment-root",
          "issue_identifier": "ENG-1",
          "body": "Please review this approach",
          "resolved": true,
          "resolving_comment_id": "comment-reply"
        },
        {
          "id": "comment-reply",
          "issue_identifier": "ENG-1",
          "parent_id": "comment-root",
          "body": "Reviewed and approved"
        }
      ]
    }
  }
}

Parameters

The following fields belong directly inside seed_config.linear. Required nested fields are marked in their tables. Provider-native objects can contain service-specific fields beyond the representative record shapes below.

Parameter	Type	Description
`uploads`	`object[]`	Uploads fixtures in provider-native format.
`teams`	`object[]`	Teams fixtures in provider-native format.
`projects`	`object[]`	Projects fixtures in provider-native format.
`issues`	`object[]`	Issues fixtures in provider-native format.
`comments`	`object[]`	Comments fixtures in provider-native format.
`advanced_state`	`object`	Advanced state.

Resource fields

These tables describe the record shapes used by the example. Keep native field names and casing. Map keys such as property names, IDs, and metadata keys are supplied by your fixture.

`uploads[]`

Parameter	Type	Description
`id`	`string`	Explicit resource identifier, when supported.
`filename`	`string`	Filename.
`content_type`	`string`	Content type.
`content_base64`	`string`	Content base64.

`teams[]`

Parameter	Type	Description
`key`	`string`	Key.
`name`	`string`	Human-readable name.

`projects[]`

Parameter	Type	Description
`name`	`string`	Human-readable name.
`team_key`	`string`	Team key.
`description`	`string`	Description.
`content`	`string`	Text content.
`member_ids`	`string[]`	Member ids fixtures in provider-native format.
`state`	`string`	State.

`issues[]`

Parameter	Type	Description
`team_key`	`string`	Team key.
`title`	`string`	Human-readable name.
`description`	`string`	Description.
`priority`	`integer`	Priority.
`labels`	`string[]`	Custom label names or objects containing name.
`project`	`string`	Project.

`comments[]`

Parameter	Type	Description
`id`	`string`	Explicit resource identifier, when supported.
`issue_identifier`	`string`	Issue identifier.
`body`	`string`	Text content.
`resolved`	`boolean`	Enable or set resolved behavior.
`resolving_comment_id`	`string`	Resolving comment id.
`parent_id`	`string`	Parent id.

API coverage and limitations

Twin name: linear Supports

The Linear GraphQL endpoint at POST /graphql for teams, projects, cycles, issues, labels, comments, workflow states, users, organization, and webhooks.
Personal API keys sent directly in the Authorization header, plus OAuth 2.0 tokens issued via /oauth/authorize, /oauth/token, and /oauth/revoke.
@linear/sdk wire compatibility including __typename on entities, { id } relation payloads in default selections, and SDK-shaped GraphQL error envelopes.
Webhook registration and replay flows, with Linear-Signature, Linear-Delivery, Linear-Event, and Linear-Timestamp headers on deliveries.
Admin endpoints for state inspection, config updates, reset/clock control, webhook replay, and fidelity checks.

Known limitations

Teams, projects, cycles, issues, labels, comments, tokens, and webhook subscriptions start empty unless seeded or created through API calls.
The fidelity target is the GraphQL surface used by Arga workflows and the @linear/sdk, not every Linear feature or internal UI behavior.
The Linear twin is backend-only — there is no browsable UI surface in the Arga app.

MCP tools: get_twin_catalog, provision_twins, start_url_validation, get_validation_results. See Scenario seeding for saving, provisioning, and resetting fixtures.

Get started

Digital twins

Tests

Setup

Integrations

Resources

Example seed

Parameters

Resource fields

`uploads[]`

`teams[]`

`projects[]`

`issues[]`

`comments[]`

API coverage and limitations

​Example seed

​Parameters

​Resource fields

​uploads[]

​teams[]

​projects[]

​issues[]

​comments[]

​API coverage and limitations

Example seed

Parameters

Resource fields

`uploads[]`

`teams[]`

`projects[]`

`issues[]`

`comments[]`

API coverage and limitations