there is no official cursor unity plugin so i built my own setup and here is everything i did to make cursor work like a native unity ide

People keep asking me which Cursor Unity plugin to install. There is no official one. Cursor works with Unity through VS Code compatibility and some manual configuration. I spent two weeks getting Cursor to feel as close to a proper Unity IDE as possible, with correct C# syntax, Unity documentation on hover, working debugger connections, and the AI features that actually understand Unity project structure. This is the complete setup guide.

🔧 Tools mentioned in this article

Cursor

AI code editor built on VS Code, Hobby plan free, Pro plan $20 per month

cursor.sh

Visit

Unity

Game engine, Personal plan free under $100k revenue

unity.com

Visit

Unity Muse

Used alongside the Cursor setup for Unity specific AI features, $30 per month

unity.com

Visit

What Cursor Inherits From VS Code for Unity

Cursor is built on the same VS Code foundation that the official Unity VS Code support uses. This means any VS Code extension that works with Unity C# should work in Cursor. In practice there is one VS Code extension that is essential for Unity development and it works well in Cursor: the C# extension from Microsoft. This gives you C# syntax highlighting, IntelliSense for C# language features, and error underlining before you compile. The Unity specific IntelliSense that knows MonoBehaviour methods and UnityEngine classes comes from Unity generating solution files for the project, which happens when you set Cursor as the external script editor.

The Complete Setup Step by Step

# Complete Cursor for Unity Setup Guide
# This is the exact setup I use. Follow in this order.

## Step 1: Install the C# extension in Cursor
1. Open Cursor
2. Click Extensions icon in left sidebar (or Ctrl+Shift+X)
3. Search: C# (by Microsoft)
4. Install the first result (publisher: Microsoft, identifier: ms-dotnettools.csharp)
5. Restart Cursor after installation

## Step 2: Set Cursor as Unity's external script editor
1. Open Unity 6
2. Edit > Preferences > External Tools
3. External Script Editor: click Browse
4. Navigate to Cursor executable:
   Windows: C:\Users\[username]\AppData\Local\Programs\cursor\Cursor.exe
   Mac: /Applications/Cursor.app
   Linux: /usr/bin/cursor (or wherever installed)
5. Click Regenerate project files
   This creates the .sln and .csproj files Cursor needs for Unity IntelliSense
6. Now double-clicking any script in Unity opens it in Cursor

## Step 3: Open Unity project correctly in Cursor
CRITICAL: Use File > Open Folder and select the Unity project ROOT folder
(The folder containing Assets, Packages, ProjectSettings folders)
Do NOT open individual scripts or the Assets folder alone
Cursor needs the .sln file in the project root to activate Unity IntelliSense

## Step 4: Create the .cursorignore file
In your project root create a file named .cursorignore
Content:
---
Library/
Temp/
obj/
Build/
Builds/
Logs/
UserSettings/
Packages/
*.meta
---
Do NOT ignore the .sln or .csproj files - Cursor needs these

## Step 5: Create the .cursorrules file
In your project root create a file named .cursorrules
Add your Unity version and project conventions:
---
Unity 6 LTS project. C# scripting.
Use Unity 6 API only. Never use deprecated Unity API.
[Add your specific project conventions here]
---
See the Unity API post for full .cursorrules content

## Step 6: Verify Unity IntelliSense is working
1. Open any existing Unity script in Cursor
2. Type: GetComponent<
3. You should see UnityEngine type completions
4. Type: transform.
5. You should see Transform property completions
If you see these: Unity IntelliSense is working correctly
If you do not: Unity may not have generated project files yet
Go back to Unity > Edit > Preferences > External Tools > Regenerate

## Step 7: Connect the AI features to your project
1. In Cursor: open the project root folder (should already be open)
2. Wait for indexing to complete (progress shown in status bar)
3. Open Cursor chat (Ctrl+L or Cmd+L)
4. Type: describe the main systems in this project
5. If Cursor describes your project correctly: AI context is working
If Cursor says it cannot find scripts: reopen the correct root folder

Extensions That Add Unity Specific Value in Cursor

• C# by Microsoft (ms-dotnettools.csharp): Essential. Provides C# language support, IntelliSense, and error detection. This is the foundation that all Unity C# development in Cursor builds on.
• Unity Code Snippets (various publishers): Several Unity focused snippet extensions exist in the VS Code marketplace. They add shortcut completions for common Unity patterns like MonoBehaviour templates and event function signatures. I use one but the specific publisher matters less than finding one with recent Unity 6 updates.
• GitLens: Not Unity specific but useful for any project. Shows Git blame annotations inline so you can see when specific lines were last changed and by what commit. Useful for tracking down when a bug was introduced.
• Bracket Pair Colorizer: Cursor includes this natively now but if you are coming from VS Code and miss it, it is available. Less necessary than it used to be.
• Extensions to avoid: any extension that tries to run a Unity Editor connection or requires Unity Editor API access will not work from Cursor in the same way it does from the official Unity VS Code integration. Stick to code editing extensions and avoid extensions that promise live Unity Editor integration.

The IntelliSense Situation Honestly

IntelliSense in Cursor for Unity C# is good but not identical to VS Code with the official Unity plugin. The Unity specific method and property suggestions that come from the UnityEngine namespace work correctly once you have the .sln file and the C# extension installed and the project opened from the root folder. What works less consistently is the very latest Unity 6 specific additions to the API that were added after the C# extension's Unity support was last updated. For those edge cases I rely on Muse Chat for accuracy and Cursor for writing and project context. The combination covers what either tool misses alone.

Mistakes During My Two Week Setup Process

• Opening the Assets folder instead of the project root: My first week of Cursor setup I opened the Assets folder directly because that is where all my scripts are. Cursor indexed the scripts but without the .sln file in the project root, Unity IntelliSense did not activate. UnityEngine completions were absent. The fix was closing that workspace and reopening the actual project root folder. Unity project root, not Assets subfolder.
• Not regenerating project files after changing the external editor: Cursor opened but Unity IntelliSense did not work until I went back to Unity's External Tools preferences and clicked Regenerate project files explicitly. Setting the editor in preferences is not enough on its own.
• Installing too many extensions at once: Installed six Unity related VS Code extensions simultaneously. Two conflicted with each other and Cursor IntelliSense broke in a way that took 90 minutes to diagnose. Install one extension, test, confirm working, then install the next.
• Ignoring .csproj files in the .cursorignore: My first .cursorignore ignored all .csproj files thinking they were generated output files. This broke Unity IntelliSense because Cursor uses the .csproj files to understand the Unity project structure. The .cursorignore entries should not include .sln or .csproj files.

Final Thoughts

Two weeks of setup produced a Cursor environment for Unity development that I prefer over Visual Studio for my daily work. The AI features that come from opening the full project folder are the primary reason. The Unity IntelliSense through the C# extension and .sln project file makes C# editing as accurate as it was in VS Code. There is no official Cursor Unity plugin but the combination of these steps produces a Unity development environment that works well enough that the absence of an official plugin has not been a practical limitation.