Skip to main content
The gap between deciding what to build and building it is usually a copy-paste: the spec goes from one tool into another, and context gets lost on the way. The Cursor integration closes that gap. From any Doc, open it in Cursor and the work starts from the full brief.
  • Cursor cloud hands the Doc to a Cursor cloud agent, which clones your default repository, implements the work and opens a pull request.
  • Cursor app opens the Cursor desktop app with the Doc already in a new chat, so you can build it with Cursor yourself.

​
Open a Doc in Cursor

  1. Open a Doc in Lane.
  2. Open the Send to menu at the top of the page, and under Open in choose Cursor cloud or Cursor app.
  3. For Cursor cloud, the agent’s run opens in a new tab so you can follow it in Cursor.
Cursor app needs no setup. Cursor cloud needs the one-time setup below.

​
Set up Cursor cloud

The connection is per person: each member who wants to use Cursor cloud adds their own Cursor API key.
  1. Create a Cursor API key in your Cursor dashboard. Cloud agents need a paid Cursor plan; free-plan keys are rejected by Cursor.
  2. Set a default repository in Cursor’s dashboard under Background Agents. The cloud agent always works in this repository.
  3. Connect in Lane: go to Settings → Integrations → Cursor, paste the key and choose Connect.
Lane checks the key with Cursor before saving it and stores it encrypted.

​
What gets sent

The Doc you’re viewing: its title and content. Linked feedback, Signals and customers aren’t sent, so put anything the agent needs into the Doc itself.

​
Good to know

  • Default repository required. Without one, Cursor tells you to set a default repository in Background Agents.
  • The run lives in Cursor. Follow progress, review the diff and merge the pull request there.
  • Rotated or revoked keys make the next run fail. Reconnect with a new key from Settings → Integrations → Cursor.
  • Disconnecting. Choose Delete in Settings → Integrations → Cursor. Runs already started in Cursor aren’t affected.
Available on all Lane plans.

​
FAQs

Q: Why does Lane need an API key instead of a sign-in?
A: Cursor doesn’t offer a sign-in flow for cloud agents. The key is stored encrypted and used only for runs you start. Q: Can I send a Doc to a repo other than my default?
A: Not today. The cloud agent always uses your Cursor default repository; change it in Cursor to switch. Q: Can my team share one Cursor key?
A: Each person connects their own. Cloud agent runs and billing live on each person’s Cursor account. Q: Can Cursor read Lane while I’m coding?
A: Yes. Connect Lane to Cursor through the MCP server and Cursor can check customer demand and read your Docs as you work.