---
title: "Zentrik + Cursor"
canonical_url: https://zentrik.ai/docs/integrations/cursor
markdown_url: https://zentrik.ai/docs/integrations/cursor.md
category: "Integrations"
learning_track: null
last_reviewed: 2026-03-28
---

# Zentrik + Cursor

Send reviewed tasks, stories, and agent plans from Zentrik to Cursor with their product context attached.

## Overview

Once a workspace admin saves a **Cursor API key**, everyone who can reach the relevant initiatives and projects can use Cursor-backed actions without managing their own secret. Exports and agent runs reuse that identity so behavior stays consistent across the team.

Open an initiative’s **Agents** tab to see the **workflow graph**—plan nodes, execution agents, and dependencies. Configure model, repository, and branches from a plan node, and review **governance** next to the execution plan before automation runs.

## Configure Cursor

One **Cursor** integration per Zentrik workspace. An owner or admin should add or rotate the key so all permitted teammates share the same automation identity.

### Save the API key

1. Create a **Cursor API key** in Cursor.
2. In Zentrik: **Settings → Integrations → Cursor**.
3. Paste the key, save, and run any **connection check** offered.

If validation fails, confirm the key is active in Cursor or generate a new one.

### Rotate or remove

- **Rotate:** paste a new key and save; Zentrik replaces the previous secret server-side.
- **Remove:** disconnect in Zentrik and revoke unused keys in Cursor so they cannot be reused elsewhere.

## Where it shows up

Cursor surfaces anywhere Zentrik sends **structured product context** into coding assistants: **task and story export** from initiatives and projects, and the initiative **Agents** experience where plans and governance are defined before runs.

### Tasks and stories

Export or sync **tasks** and **stories** into Cursor-ready payloads so engineering starts from the same acceptance criteria, links, and background PMs signed off on in Zentrik.

### Agents & automation

The **Agents** graph shows how work breaks into execution agents under each **Agent plan** node. Click a plan to edit model, repo, branches, and plan text; open the **governance / execution plan** view when you need policy checks beside the run definition. When agents execute, they use the **shared Cursor key** from Settings so runs stay tied to the initiative that started them.

## For workspace admins

- The key is **shared** across users who can trigger Cursor flows; Zentrik **never shows the secret again** after save.
- **Permissions** still apply: teammates only see actions on initiatives and projects they can already open.
- Treat the key like any other automation credential: rotate on schedule, scope it to least privilege, and remove it when you retire the integration.

## Troubleshooting

### Connection check fails

Generate a **new key** in Cursor, paste it into **Settings → Integrations → Cursor**, and save. If your org restricts Cursor, work with **IT or your Cursor admin**, then [contact us](https://zentrik.ai/contact) if Zentrik still cannot validate.

### Teammate cannot use Cursor from Zentrik

Confirm they are in the **same workspace** and can open the initiative or project where the action appears. The key is shared, but Zentrik permissions are not bypassed.

## Related guides

- [Zentrik + Vercel's v0](https://zentrik.ai/docs/integrations/v0)
- [Zentrik + Lovable](https://zentrik.ai/docs/integrations/lovable)
- [Zentrik + Bolt](https://zentrik.ai/docs/integrations/bolt)