Aura is now available for Unity, powered by Coplay tech. It ships as a standalone desktop app that bridges into the Unity Editor — the same chat UI, backend, and AI engine that powers Aura for Unreal Engine, adapted for Unity workflows (C#, MonoBehaviour, ScriptableObject, prefabs, scenes, and the rest of the Unity toolbox).
⚠️ Git is required for installing Unity packages. If you don't have it already, install it from git-scm.com/install/windows before continuing.
Login at tryaura.dev, then go to Download Aura > Unity to grab the AuraForUnity installer. Note only Windows .exe is available at launch, macOS is coming soon.
Run the installer, then launch AuraForUnity.
Sign in to your Aura account.
Open the project selector in the top-left of the AuraForUnity window and pick the Unity project you want to work on.
If that project doesn't have the Aura Unity plugin installed yet, AuraForUnity shows an Install Aura plugin confirmation. Click Install — AuraForUnity adds the Aura package to the project's Packages/manifest.json, and Unity picks it up and installs it automatically the next time you open the project.

Open (or reopen) the Unity project. Once the plugin finishes installing, AuraForUnity connects to the running editor.
Confirm Aura can see your project — in the chat, ask: "Tell me about this project."
💡 AuraForUnity runs as a single desktop window. If you have several Unity projects open, each one registers with AuraForUnity as "Aura-ready" and you switch between them using the project selector in the top-left of the window. The currently connected project is shown next to the green dot; click the chevron to pick a different one.

See Unity Troubleshooting for details on working across multiple Unity projects.
Aura has three modes — the same three you get on Unreal — and it's worth knowing when to reach for each. You can learn more about modes in the Quick Start.
Aura answers questions about your project without making changes. Great for exploration and debugging. Example prompts:
@PlayerController.cs and explain why Jump() sometimes double-fires."Aura cannot modify your project while in Ask mode.
Plan mode produces a step-by-step implementation plan you can review before anything is touched. Best for larger or unfamiliar systems. Example prompts:
Plans are stored in your project under Assets/.Aura/plans/ as editable markdown files. When you're happy, press Start and Aura implements the plan in Agent mode.
While in Agent mode Aura can create and edit files, modify your scene, install packages, and run shell commands. Typical prompts:
MonoBehaviour called HealthComponent with a CurrentHealth / MaxHealth pair, a TakeDamage(int) method, and a Died UnityEvent."Assets/Enemies/."(0, 1, 0)."See the Scene & Prefab Agent, Coding Agent (C#), and Editor Agent (Unity) pages for the full capabilities reference.

Context is extra information Aura uses to build better answers — selected files, open scenes, reference images. The same context mechanisms work on Unity as on Unreal:
@ mentions — type @ in the chat to search your project's asset files — scripts, scenes (.unity), prefabs, materials, animation clips, and other assets under your project root. Scene Hierarchy objects aren't searchable via @; reference them by name in the prompt, select them in the Hierarchy before prompting, or drag them into the chat.For the full breakdown see Giving Aura Context — the mechanisms are the same across both editions, only the source locations (Project window vs. Content Browser) differ.
Once you're signed in and connected, these are a quick way to confirm everything is wired up:
Assets/ that has a Rigidbody." — exercises asset queries.(0, 1, 0) named TestCube." — exercises scene edits (Agent mode).AuraForUnity v1 focuses on the capabilities that move the needle for Unity day-to-day.
Available in v1:
Not in v1:
See Scene & Prefab Agent, Coding Agent (C#), and Editor Agent (Unity) for deep dives on each area.
For Unity-specific issues (installer won't open, plugin not detected, project picker, log locations), see Unity Troubleshooting.
General troubleshooting (connection issues, chat thread issues, account setup) applies across both editions — see the Troubleshooting section.