Welcome to Aura. This page introduces important concepts to use Aura on a daily basis. For deep dives on concepts check the documentation menu. For a high level crash course on Aura, you can also check out the tutorial below.
Aura supports both Unreal Engine and Unity. Choose the installation path that matches your engine.




Aura can run as a standalone app, docked in the editor, in headless mode, or from your IDE with Claude Code — see the different ways to run Aura.
Aura is now available for Unity, powered by Coplay tech. It ships as a standalone desktop app that bridges into the Unity Editor — no separate Python or MCP setup is required.
⚠️ 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 and wait for the plugin to finish installing.
Start the MCP session so Aura's tools can connect to the editor. In Unity, open Window → MCP For Unity → Toggle MCP Window (or press Ctrl+Shift+M), set Transport to Stdio, then click Start Session — the status dot turns from red to connected. You can reopen these steps anytime in Unity from Help → MCP for Unity Setup.

Test Aura can see your project: “Tell me about this project”
Learn more about what Aura for Unity can do here.
💡 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. See the AuraForUnity Setup page for full details.
Aura has three distinct modes that’s good to be aware of: Plan, Ask and Agent mode.

Aura analyzes your project and provides answers uniquely tailored to your project. For example you can ask Aura:
You can also search the FAB store directly from Aura to quickly find assets for your project.
Learn more about Project Understanding. Aura cannot make changes to your project while in Ask mode.

Plan mode is ideal when you need to design and structure complex implementations before execution. Aura breaks down your request into detailed, step-by-step implementation plans that you can review, refine, and approve before any changes are made.
Use Plan mode when you want to:
Example requests for Plan mode:

When you are done iterating on the plan with Aura, press the 'Start' button and Aura will begin implementing it (Agent mode).
Note: Plans are stored inside your project directory: "/Saved/.Aura/plans" as editable markdown (.md) files.

While in Agent mode Aura has ability to create files and edit parts of your project.
Aura can handle various tasks such as:
S_RingConfig struct, which has int values for Str, Dex, Int, Faith, Luck, and Stamina, a model parameter, and an icon texture. Then, create a DT_RingConfigs data table that has 8 different rings in it.”At the top right of the Aura chat you’ll find the New Chat, Thread History, and Settings buttons.

Conversations with Aura are organized into threads. You can switch threads by clicking the tabs at the top. Closed threads are kept in the Thread History.

💡 You can run multiple prompts in parallel (up to ~4) allowing you to move onto other things. For example while Aura is creating a 3D model of jump pad in one thread, you can chat about a blueprint plan for the jump pad in another thread.
Learn more about Advanced Settings.
Context is extra information provided to Aura such as files and assets. When Aura has specific files to reference it can construct better answers.
There are many ways to give Aura context which you can learn more about in Giving Aura Context, but the following are most important for getting started:
Type ‘@’ to bring up the search menu. You can search by clicking the ‘@’ icon too.

You can give Aura image references by:
Supported image types: jpg, png, and bmp.
Aura can also read documents, useful for bringing design docs, GDDs, spreadsheets, PDFs, and other references directly into Aura.
Supported document types: PDF, DOCX, PPTX, XLSX, HTML, Markdown, and more.

When debugging issues with the Aura team, chat exports help the team investigate issues and where Aura may have messed up. You can export your chat by clicking the Tools button at the bottom > Export Chat and then send it to the Aura team.

Aura is usage based where responses and tasks can vary in cost depending on the model you've selected and complexity of the task. For example if you ask Aura the same question, once with Sonnet 4.6 and once with Opus 4.7 selected, the Opus conversation will cost more because it's a much more advanced and expensive LLM to run.
Relative cost estimates are displayed in the model selector panel.

For tips on reducing spend, check out Prompting Tips.
You can keep track of usage events in your account at https://app.tryaura.dev/auth?redirectTo=%2Faccount.
To learn how to get the most out of Aura, we suggest checking out Prompting Tips and then explore the core features:
For power user tips check out Giving Aura Context and Advanced Settings.