Linear
Linear is where many teams track bugs and features. The Linear integration will connect those issues to X4RGE — so an issue can start a cloud agent run, update status as work progresses, and show PR links where your team already plans work.
Today: Linear appears on Dashboard → Integrations, but connect is not fully available yet. This page explains what that means for you, what to use instead, and what will change when connection ships.
If Connect on Linear does not finish, that is expected. For production work now, use GitHub for repos and automations, and paste Linear issue URLs into cloud agent tasks when you need ticket context.
What this page is for
Even when Linear connects, agents work on repositories through GitHub. Connect GitHub first; Linear adds planning and visibility on top — not a replacement for repo access.
Current status
If Connect does not complete, you are not doing anything wrong — the integration is still being finished. Use What to use today until then.
Why Linear
Linear is your source of truth for what to build and what's in progress. Connecting it to X4RGE means less copy-paste and fewer manual status updates when agents work on your codebase.
Linear is for planning and visibility; GitHub remains where code and PRs live.
How Linear fits your workflow
Think of two layers:
Today: you bridge the layers manually — paste a Linear URL into a run, connect the repo on GitHub.
When Linear ships: matching issues can trigger runs and write progress back to the issue automatically.
In practice
Use this table to pick your next step. Rows marked today work now; later need the connect flow.
What to use today
Until Linear is connectable, this is the reliable path most teams use:
- GitHub — connect repos for all cloud agent and automation work.
- Issue URLs in prompts — include the Linear link so the agent has full context.
- Schedule automations — periodic triage on GitHub issues or labels while Linear triggers are pending.
- Agents workspace — track run progress when status is not yet written back to Linear.
Include the issue link and acceptance criteria: "Fix ENG-123 per https://linear.app/…/issue/ENG-123 — update tests and open a PR."
Connect GitHub and prove one repo on cloud agents before waiting on Linear — same staged rollout most teams use for agent adoption.
When Linear is available
When connect ships, your organization admin (or someone with Integrations access) will set this up from the dashboard. Plan for these steps:
Authorize Linear
From Integrations in the dashboard, connect your Linear workspace. A workspace admin may need to approve the app.
Map teams and projects
Choose which Linear teams or projects X4RGE may use. Unmapped teams will not trigger automations or appear in pickers.
Set status mapping
Decide which Linear statuses match agent lifecycle — for example In progress when a run starts, In review when a PR opens.
Test one issue
Use a low-priority bug: confirm a run starts, links back to the issue, and updates status as expected.
Your org may require integration approval before Linear goes live.
What it will enable
Once connected, Linear becomes a trigger and record for agent work — not just a link in a prompt.
- Trigger runs from labels, assignees, or status changes on issues.
- Sync status as the agent starts, opens a PR, completes, or fails.
- Attach links — PR and run summary on the issue for reviewers.
- Automate triage on new issues that match team filters (within Usage and policy).
Until then, use schedule or GitHub triggers and keep referencing issue URLs in prompt templates.
Issue → run workflow
When the integration is live, a typical flow looks like this — from ticket to PR without manual handoffs:
Issue matches your rule
Someone creates, labels, or assigns an issue that matches an automation filter.
Cloud agent starts
The agent works on the linked repository (via GitHub), on a branch tied to the issue.
Updates on the issue
Comments and status reflect run progress — links to the run and PR when available.
Done or in review
Status moves to your configured state when the PR is ready or the run finishes.
Pair with cloud agents and automations once Linear connection ships.
Security habits
When Linear triggers paid cloud runs, treat team mapping and filters as spend and visibility controls — not just convenience.
Still blocked on connect?
- Confirm you are not expecting a bug — connect is not finished yet.
- Use What to use today — GitHub + issue URLs in prompts.
- See Troubleshooting → Integrations for Slack/Linear status.
- Ask your org admin about integration approval for when Linear goes live.