Linear

The Linear integration links your issue tracking to 4RGE so agents can pick up issues and report progress back. When fully connected, a Linear issue becomes a first-class trigger for cloud agents and automations.

Planned capabilities

Current dashboard behavior

Linear appears on Dashboard → Integrations with a Connect button, but no OAuth flow is wired yet. Clicking Connect shows a toast: Linear integration setup is not connected yet. Team and project mapping UI is present in the product shell, but selections are not persisted to the backend. Automation triggers that list kind: linear in the picker are not active — use schedule or GitHub triggers instead.

Why GitHub is still required

Even when Linear connects, cloud agents clone repositories through the GitHub integration. Until Linear repo linking ships, map issues to work by pasting Linear URLs into cloud agent prompts and connecting the target repo via GitHub. Scheduled automations scoped to a GitHub repository can reference issue numbers in prompt templates as an interim triage pattern.

Connecting (when available)

1. Authorize Linear

   From the Integrations page in the dashboard, connect your Linear workspace. A workspace admin may need to approve the OAuth application.

2. Map teams and projects

   Choose which Linear teams or projects 4RGE should work with. Unmapped teams will not trigger automations or appear in the issue picker.

3. Configure status mapping

   Define which Linear statuses correspond to agent lifecycle events — for example, move to "In Progress" when a run starts and "In Review" when a PR opens.

4. Test with a single issue

   Assign a low-priority bug to the 4RGE bot and confirm a cloud run starts and links back to the issue.

What it will enable

• Trigger an agent (or automation) from a Linear issue label, assignee, or status change.
• Keep issue status updated as work progresses — run started, PR opened, run failed.
• Attach PR and diff links to the issue for reviewers.
• Triage new issues automatically on a schedule paired with Linear filters.

Example automation trigger (planned)

{
  "kind": "linear",
  "teamId": "ENG",
  "event": "issue",
  "action": "create",
  "filter": { "label": "agent-triage" }
}

Until Linear triggers are active, triage issues with schedule automations scoped to your GitHub repository and reference issue URLs in the prompt template.

Issue → run workflow (planned)

1. Issue labeled or assigned

   Linear webhook fires to 4RGE when the issue matches automation filters.

2. Cloud agent run starts

   Agent clones the linked repository (from issue metadata or team default), checks out a branch named after the issue ID, and executes the prompt template.

3. Progress updates

   Linear issue receives comments with run status and links.

4. Completion

   On PR open or run complete, issue status moves to the configured "In Review" or "Done" state.

Workaround today

Until Linear is connectable:

1. Paste Linear issue URLs into cloud agent task descriptions manually.
2. Use GitHub-linked issues — connect the repo via GitHub and reference issue numbers in prompts.
3. Use scheduled automations: "Review open GitHub issues labeled bug and summarize triage recommendations."

Security considerations