Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.laneapp.co/llms.txt

Use this file to discover all available pages before exploring further.

The Cursor integration lets you send a Plan from Lane to Cursor’s Background Agent. Cursor clones your default repository, builds out the work described in the Plan, and opens a pull request — closing the loop between product thinking in Lane and code in Cursor without copy-paste.

​
Overview

After you’ve drafted a Plan in Lane — the problem, the scope, the success criteria, the linked Features and Customers — click Send to → Cursor and Cursor’s Background Agent picks it up. You get a link back to track the agent’s run in Cursor. Useful when:
  • The Plan is detailed enough that a coding agent can take a real first pass
  • You want to skip the “paste the PRD into Cursor” step
  • Your team works in both Lane and Cursor and wants them connected

​
Configuration and Setup

The Cursor integration is per user, not workspace-wide. Each member who wants to send Plans to Cursor adds their own API key.

​
1. Get a Cursor Cloud API key

  • Go to Cursor → Settings → API keys and create a key.
  • The Background Agent API requires Cursor’s Pro or Business plan. Free plan keys are rejected by Cursor.

​
2. Set a default repository in Cursor

  • Open the Cursor dashboard → Background Agents → Default repository.
  • Pick the repo you want the agent to work in.
This is mandatory — Lane doesn’t pass a repository to Cursor; Cursor’s agent always uses your default.

​
3. Connect in Lane

  1. Click your workspace name in the top-left.
  2. Go to Settings → Integrations → Cursor.
  3. Paste your API key and click Connect.
Lane validates the key with Cursor before saving and encrypts it at rest. Only the last 4 characters are shown for verification.

​
Sending a Plan to Cursor

  1. Open a Plan in Lane.
  2. Click Send to and pick Cursor.
  3. Lane formats the Plan and submits it as the prompt to Cursor’s Background Agent.
  4. The agent’s status link opens in a new tab so you can follow along in Cursor.
The agent clones your default repo, implements the changes, and opens a pull request when it’s done.

​
What gets sent

  • The Plan’s text content (formatted for agent consumption)
  • Nothing else — no attached files, no linked Features, no Customer data
The Background Agent uses your default repository from Cursor’s dashboard. Lane intentionally doesn’t pass a repo to avoid misrouting work to the wrong codebase.

​
Limits and good to know

  • Cursor Pro or Business plan required — Free plan API keys can’t use Background Agents and will fail at connect time.
  • Default repository required — without one set in Cursor, the run will fail with a Cursor-side error like “Set a default repository in Background Agents”.
  • Per user, per workspace — each team member adds their own key; there’s no shared connection.
  • Lane only sends, doesn’t track — the run lives in Cursor. To see the agent’s progress, the diff, or the resulting PR, use the link Lane returns.
  • Key revocation — if you rotate or revoke the API key in Cursor, the next send will fail with a 401. Reconnect with a new key from Lane’s settings.

​
Plan gating

Available on all Lane plans. Cursor’s Pro or Business plan is required on the Cursor side.

​
Disconnecting

  • Settings → Integrations → Cursor → Delete.
  • The stored API key is removed from Lane. Existing Cursor runs are unaffected.

​
FAQs

Q: Why does Lane need an API key instead of OAuth?
A: Cursor doesn’t offer an OAuth flow for Background Agent access today. The key is encrypted at rest and only used to launch runs you initiate. Q: Can I send a Plan to a specific repo other than my default?
A: Not today. The agent always uses your Cursor default repository. To switch, change the default in Cursor. Q: Can my team share one Cursor API key?
A: Each user connects their own. Cursor’s Background Agent runs and billing live on each user’s Cursor account. Q: What does the agent see — just the Plan text?
A: Yes. Linked Features, Customers, and Insights aren’t sent. If you want those reflected, include the relevant context in the Plan body before sending. Q: My Cursor key was working and now fails — what happened?
A: It was likely rotated or revoked on Cursor’s side. Reconnect with a new key from Settings → Integrations → Cursor. Q: Can I use Cursor desktop with Lane instead?
A: For desktop-side workflows, connect Lane via MCP — Cursor (desktop) can read Plans and other Lane records directly. The Cursor integration on this page is specifically for Cursor’s Cloud / Background Agent.