{"slug": "run-agents-on-github-and-linear-issues", "title": "Run agents on GitHub and Linear issues", "summary": "Lanes launched an integration that lets developers run AI agents directly on GitHub and Linear issues, importing tickets with full context and writing results back as comments or pull request links. The tool creates isolated worktrees per ticket for parallel execution and uses OAuth tokens stored locally, aiming to eliminate manual copy-paste between issue trackers and development environments.", "body_md": "Your work already lives in GitHub and Linear. Lanes connects to both, so you can turn a ticket into a running agent session without retyping anything.\n\n## How Lanes does it\n\n**Import tickets.** Pull issues from GitHub or Linear directly onto the board. The import dialog lists the first 50 open issues per repo or team, filters out pull requests and completed tickets, and pins the exact match when you search by number (`#9`\n\n,`9`\n\n, or`ENG-9`\n\non Linear).**Run with context.** Start a session on an imported ticket and the agent picks up the issue details. Import copies the title and body onto a draft[issue](/docs/desktop/issue-board), adds a marker line pointing back at the original, and shows an external link badge in the detail panel that jumps upstream in one click.**Write results back.** Pull request links and comments flow to the source. Once connected, an agent can comment on the upstream GitHub or Linear issue through the MCP tools, posting the PR link when the session lands; the PR itself comes from`gh`\n\ninside the session.**Isolated per ticket.** Each runs in its own worktree, so a sprint of tickets runs in parallel without conflicts.\n\nBoth connections are OAuth, done once from Settings. [GitHub](/docs/desktop/github-integration) asks for the `repo`\n\nand `read:user`\n\nscopes; [Linear](/docs/desktop/linear-integration) uses a read-scope grant that also lets Lanes create issues and post comments. Tokens are stored locally in `integrations.json`\n\nand never leave your machine, and agents use the connection without ever seeing a token. If a token gets revoked, a one-click Reconnect banner restores the connection.\n\nTickets drift, so imports can follow. If the upstream issue was edited after import, the refresh button on the external link badge re-fetches it, and Lanes warns before overwriting any local edits.\n\nThe limits are documented plainly: pull request creation is not exposed through the MCP tools, and Linear states and priority are not mapped automatically, so you decide where an imported ticket lands on the board.\n\nThere is also a zero-click path in the other direction: [deep links](/docs/desktop/deep-links). Linear's coding-tools setting can point at a `lanes://new`\n\nURL, so the coding-tool button on any Linear issue opens Lanes with a draft already populated, no import dialog involved.\n\n## Why it matters\n\nThe loop from ticket to pull request closes inside one workspace. Your team keeps planning in GitHub and Linear, and Lanes handles the local execution.\n\nNothing about your tracker changes. The ticket stays the source of truth; Lanes holds the working copy, the worktree, and the session, then reports back where the team already looks.\n\n## Set it up\n\n**Connect the tracker.** Open Settings, then GitHub or Linear, and click Connect. Approve the OAuth screen in your browser.**Import a ticket.** Click Import from GitHub or Import from Linear in the project header, search, and click the ticket.**Start a session** on the imported issue with Plan or Implement. The copied title and body become the agent's context.**Report back.** Have the agent comment the result upstream via MCP, or do it yourself from the external link badge.\n\n## Where this breaks without Lanes\n\nWithout the connection, every ticket is copy-paste: title into the terminal, body into the prompt, then the reverse trip to carry results back, once per ticket. Nothing links the local branch to the upstream issue, so a sprint of ten leaves you reconciling by hand. Import once, run in parallel, comment back is the whole point.\n\n## Further reading\n\n[GitHub integration](/docs/desktop/github-integration): the OAuth flow, import dialog, and agent-side tools.[Linear integration](/docs/desktop/linear-integration): token refresh, the team picker, and search shorthand.[Deep links](/docs/desktop/deep-links): pre-filled drafts straight from a Linear button or a script.[The issue board](/docs/desktop/issue-board): where imported tickets live and run.", "url": "https://wpnews.pro/news/run-agents-on-github-and-linear-issues", "canonical_source": "https://lanes.sh/use-cases/run-agents-on-github-and-linear-issues", "published_at": "2026-07-16 22:49:53+00:00", "updated_at": "2026-07-16 23:17:30.345961+00:00", "lang": "en", "topics": ["developer-tools", "ai-agents", "ai-tools"], "entities": ["Lanes", "GitHub", "Linear"], "alternates": {"html": "https://wpnews.pro/news/run-agents-on-github-and-linear-issues", "markdown": "https://wpnews.pro/news/run-agents-on-github-and-linear-issues.md", "text": "https://wpnews.pro/news/run-agents-on-github-and-linear-issues.txt", "jsonld": "https://wpnews.pro/news/run-agents-on-github-and-linear-issues.jsonld"}}