how to install every unity ai tool in 2026 the way i actually did it without breaking my project or losing half a day to setup
Installing Unity AI tools is not complicated but there are a specific set of mistakes that cost you hours when you hit them in the wrong order. I have installed Unity Muse, Sentis, Motion Matching, and the AI Navigation package across four different Unity projects and machines. This is the sequence that works without breaking anything, the mistakes I made early on that cost me time, and the exact settings to check after each install.
Marcus Webb
June 27, 2026
This guide covers: installing Unity Muse, Unity Sentis, Motion Matching package, AI Navigation package, setting up Cursor with Unity, and connecting Claude to your design workflow. Every step is documented in the exact order I follow when setting up a new Unity 6 project with the full AI stack. If you follow these steps in this order you will not hit the three common setup problems I documented from my own wrong-order installs.
Before Anything: Check Your Unity Version
Every AI feature in this guide requires Unity 6 LTS minimum. Unity 2022 LTS does not support Sentis at the current API level, does not have Motion Matching as a stable package, and Muse Chat inside the Editor requires the Unity 6 Editor integration. If you are on Unity 2022 you will need to upgrade the project before anything else. The upgrade from Unity 2022 to Unity 6 is not trivial on an active project. If you are starting fresh, start in Unity 6 from day one.
Step 1: Install Unity Muse
# Installing Unity Muse
# Requires: Unity 6 LTS, active Unity account, Muse subscription
## Subscribe first
1. Go to unity.com/products/muse
2. Subscribe at $30 per month
3. The subscription is tied to your Unity account email
4. You do NOT install Muse via Package Manager
## Enable Muse in the Editor
1. Open Unity 6 Editor
2. Go to Window > Muse (should appear after subscription is active)
3. Sign in with the Unity account that has the Muse subscription
4. Muse Chat panel will open as a dockable panel
5. Test: type 'what is the NavMeshAgent component?' and confirm you get a response
## If Muse does not appear in the Window menu:
- Ensure you are signed into the correct Unity account in the Editor
(Edit > Sign In to Unity Account)
- Ensure you are on Unity 6, not Unity 2022
- Restart the Editor after signing in
- Check unity.com account portal to confirm subscription is active
and not in a failed payment state
## Muse tools available after activation:
- Muse Chat: visible as dockable panel
- Muse Animate: Window > Muse > Animate
- Muse Texture: accessible in Project view context menu on materials
- Muse Sprite: Window > Muse > Sprite
- Muse Behavior: Window > Muse > BehaviorStep 2: Install Unity Sentis
# Installing Unity Sentis
# Free, requires Unity 6 LTS
# DO NOT install Barracuda alongside Sentis - they conflict
## Install via Package Manager
1. Window > Package Manager
2. Click the + button (Add package)
3. Select 'Add package by name'
4. Enter: com.unity.sentis
5. Click Add
6. Unity will resolve dependencies and install
## Verify installation
1. In the Package Manager list, confirm Sentis appears as installed
2. In Project > Assets, you should now see Sentis in the namespace
3. Create a test script:
using Unity.Sentis;
If no red underline: Sentis is installed correctly
## Remove Barracuda if present
If you previously installed Barracuda (the deprecated predecessor):
1. In Package Manager, find com.unity.barracuda
2. Remove it before using Sentis
3. Restart the Editor
Having both installed causes namespace conflicts
## First time Sentis use checklist:
- Install Netron (netron.app) in your browser
You will use this to inspect ONNX model layer names
- Always wrap TensorFloat in using blocks to prevent memory leaks
- Test your target platform's BackendType before designing AI systems
around GPU inference speedStep 3: Install Motion Matching
# Installing Motion Matching
# Free, requires Unity 6 LTS
# Requires Animation Rigging package as dependency
## Install Animation Rigging first (dependency)
1. Package Manager > Add package by name
2. Enter: com.unity.animation.rigging
3. Install
## Install Motion Matching
1. Package Manager > Add package by name
2. Enter: com.unity.motionmatching
(name may vary, check unity.com/features/motion-matching for current package name)
3. Install
## Minimum animation database to get good results:
Motion Matching requires source animation clips to select from.
With fewer than 8 clips the blending is mediocre.
Recommended minimum for humanoid character:
- Walk forward, backward, left strafe, right strafe (4 clips)
- Run forward, backward, left strafe, right strafe (4 clips)
- Idle with natural weight shift (1 clip minimum, 3 preferred)
- Jump, Fall, Land (3 clips)
Total: 12 minimum, 18 for good quality
Source: Mixamo free library provides all of these
Download in FBX for Unity format, In Place for locomotion clipsStep 4: Set Up Cursor With Your Unity Project
# Setting up Cursor with Unity 6
# Cursor replaces VS Code as your Unity script editor
## Install Cursor
1. Download from cursor.sh
2. Install as you would VS Code
3. On first launch: import VS Code settings if prompted
Your Unity C# highlighting and extensions transfer automatically
## Connect Unity to Cursor
1. In Unity: Edit > Preferences > External Tools
2. External Script Editor: Browse to Cursor executable
Windows: C:\Users\[name]\AppData\Local\Programs\cursor\Cursor.exe
Mac: /Applications/Cursor.app
3. Click Regenerate project files
4. Now when you double-click a script in Unity it opens in Cursor
## Open your Unity project correctly in Cursor
CRITICAL: Do not open individual scripts in Cursor.
Open the ENTIRE Unity project folder as the workspace.
1. In Cursor: File > Open Folder
2. Select your Unity project root folder
(the folder containing Assets, Packages, ProjectSettings)
3. Cursor will index all scripts in the Assets folder
4. Indexing takes 1 to 5 minutes on first open depending on project size
## Create .cursorignore file
In your project root create a file named .cursorignore
Add these entries to prevent Cursor indexing irrelevant folders:
---
Library/
Temp/
obj/
Build/
Builds/
Logs/
UserSettings/
Packages/
---
This reduces indexing time and improves suggestion relevance
## Test Cursor is working
1. Open any existing script from the Unity project in Cursor
2. Type a comment describing a new method
3. Press Tab to see if Cursor's completion references classes
that exist in your other scripts
4. If it does, Cursor has indexed your project correctlyStep 5: The Claude Integration
- Claude does not install inside Unity. It runs in your browser at claude.ai or in the Claude desktop app. The integration is a workflow habit, not a technical setup.
- Create a persistent Claude conversation or Project for each game you are working on. Use it as your design session space. When you are about to build a new system, open Claude first, describe the system, get the architecture, then open Unity and Cursor.
- Keep a short context summary of your game that you paste at the start of each Claude session. Something like: I am building a 2D roguelike with permanent progression, top-down view, keyboard and gamepad support. The player has a run-based character and a persistent home base. This prevents Claude from giving generic advice that does not fit your game.
- Claude Pro at $20 per month provides the extended context window that is useful for pasting full system descriptions and multiple architecture options. The free tier works for shorter sessions but hits context limits on complex design discussions.
Mistakes I Made Installing These Tools
- Installing Sentis while Barracuda was still present: this caused a namespace conflict that produced confusing compile errors. The error messages did not mention Barracuda. I spent 90 minutes debugging what turned out to be a one-remove fix. Remove Barracuda before installing Sentis.
- Opening a single script in Cursor instead of the project folder: Cursor without the project folder indexed is just a code editor. The AI suggestions that know your architecture require the full project to be open as a workspace. This was the most common mistake I made in month one.
- Not creating the .cursorignore file: Cursor indexed the Library folder on a large project which contains thousands of compiled asset files. Indexing took 20 minutes and suggestions were slower and less relevant. The .cursorignore file takes two minutes to create and the difference in indexing speed is significant.
- Expecting Muse Chat to appear immediately after subscribing without signing in: Muse Chat requires you to be signed into the correct Unity account inside the Editor itself. I had the correct subscription but was signed into a different email in the Editor. Spent 30 minutes troubleshooting what was a sign-in issue.
Final Thoughts
The full Unity AI tool setup takes about an hour when done in the right order. The mistakes I documented cost me four hours total across my early installs. Following the sequence above, specifically removing Barracuda before Sentis, opening the project folder not individual files in Cursor, and signing into the correct Unity account for Muse, eliminates the problems that cause most of that lost time. Once the setup is complete the workflow described in the rest of my Unity posts runs without further configuration overhead.