The first integrations are here. From v0.39, you can connect Lanes to GitHub and Linear, import tickets straight onto your board, and hand your agents an MCP surface that reaches all the way back into your tracker. No copy-paste, no second window.
Pull a ticket in, in one click
From any project view, click the GitHub or Linear icon in the header. The dialog shows a picker for your repos or teams, the first 50 open issues sorted by what's recent, and a search box that understands shorthand. Type #9 or ENG-9 and the exact match pins to the top. Anything you've already pulled in is greyed out with the local issue number next to it, so you don't import the same ticket twice.
Click one and it lands on your board as a draft. The title and description copy across, with a marker line back to the original ticket. The imported issue picks up an upstream badge in its detail panel: hit Open to jump to the original, or Refresh to pull the latest title and description down if it's been edited since you imported.
Connect once, in Settings
Open Settings, head to GitHub or Linear under Integrations, and click Connect. Your browser opens, you approve the scopes Lanes asks for, and the page flips to Connected. That's the whole setup. If you mostly work out of one team or repo, pin it as the default and the import dialog will surface it first next time.
Tokens are stored locally in your Lanes data directory and never leave your machine. Linear's access tokens are short-lived, so Lanes refreshes them proactively before every call. You don't have to think about it. Disconnect from the same page whenever you want, and the tokens get wiped immediately.
What it unlocks for your agents
The integrations are not just a UI. The moment you connect GitHub or Linear in Settings, every lanes_github_* and lanes_linear_* tool on the Local MCP lights up. An agent in a Lanes session, or any chat with the Local MCP wired in, can list teams, search issues, read a specific ticket, open new ones, and comment back. The agent reads your tokens out of the local integrations file directly, so there's nothing extra to paste or configure on the agent side.
The pattern that gets interesting is the round trip. Pull a ticket out of your tracker, drop it on your board, run a session on it in a fresh worktree, then push the PR link back as a comment on the original ticket. The whole thing fits in a prompt.
"Pull every open Linear ticket with the frontend label into Lanes, then start Claude Code in plan mode on the highest-priority one."
"Once the session on ENG-321 lands, summarise the work, post it as a comment on the Linear ticket, and open a follow-up issue for the cleanup the agent flagged."
Pair the Lanes Local MCP with Linear's or GitHub's hosted MCP in the same chat and the two surfaces meet in the middle. The connective tissue is whatever you type next, no integration layer in between. For a full walkthrough of that two-MCP pattern, see From Linear to Lanes.
GitHub and Linear are available in Lanes from v0.39. We'd love your feedback. Join our Discord to stay updated.