Aura AI Tutorials: Build, Connect, Loop, Sync, and Studio

1

Run the Aura Hub installer

Open the AuraHub_Setup.exe file you just downloaded and follow the installer prompts. The Windows installer is available now; the macOS installer is coming soon. The Hub installs as a lightweight background service — once installed, you'll see the Aura icon appear in your system tray. It runs silently and starts automatically on login.

Reinstalling on a new PC is fine: download the Windows installer again, sign in with the same Aura account, then use Aura Settings - Transfer Aura Data if you want to move local chats, GDDs, rules, and project context from the old computer.

2

Open Aura and choose how to begin

Open Aura from the Start menu or system tray and sign in with the same account you used here. Choose Build inside Aura for an engine-free first playable, Start a new game in an engine for a new Unity, Godot, or Unreal project, or Connect an existing project for work already in progress.

You do not need to install or open a game engine to use Build inside Aura. For an engine path, install Unity, Godot, or Unreal separately before asking Aura to start there.

3

Follow only the path you chose

For Build inside Aura, describe the game in the same chat and review Aura's game plan before it builds. For Start a new game in an engine, choose an editor already installed on your computer and the new project location. For Connect an existing project, choose that project's root folder; Aura detects the engine from the project and connects the matching integration.

Aura Describe → Review game plan → Approve → Play and verify

New Choose installed editor → Review location and plan → Approve

Existing Choose project folder → Confirm the detected engine → Connect

4

Wait for the right ready state

An Aura-built playable is ready only after its behavior checks pass and you can play the result. An engine project shows Context live when Aura can read the current scripts, scenes, assets, and structure; Actions ready separately means the connected editor can apply changes you approve. Aura does not call an engine project ready merely because its folder exists.

Core project context stays local. Pro cloud continuity and Cloud Loops use cloud storage or processing only when you explicitly enable them, and your content is not used for training.

5

Tell Aura what should stay true (recommended)

Say lasting game and project decisions in ordinary language, then keep them in the GDD or project rules so Aura can reuse them. Put one-request instructions directly in chat. Experienced developers can still name exact files, systems, or architecture when that precision is useful.

Examples: "Keep movement quick and responsive" · "Ask before changing saved games" · "Reuse the inventory screen that is already here"

6

Load your Game Design Document (optional but powerful)

If you have a GDD, choose your project and click GDD in Aura's top bar. Follow the prompt to attach an existing document or create one with Aura. Aura references it for future suggestions so generated systems, scripts, and mechanics can stay aligned with your game's design intent. Supported formats: PDF, Word (.docx), plain text, and Markdown.

No GDD yet? Even a rough outline helps. A single paragraph describing your game's core loop gives Aura enough context to make significantly more relevant suggestions.

7

Start prompting

You're ready. Type questions and requests in the same Aura chat box. Aura answers normal questions in chat; when work would change your project, it shows the proposed actions for review before anything is applied. For a bounded, multi-step goal, Aura can suggest a Loop, or you can start one yourself with /loop.

First prompt examples: "Make a small space platformer with a fox hero and a blaster" · "Add a dash that feels quick, but do not change the jump" · "Explain why the enemy keeps getting stuck without changing anything yet"

How do you want to use models?

Try Aura with 100 requests

Use my own API keys

You're ready.

Choose how you want to
build with Aura.

Ready to build?