Local-first by default  ·  Cloud workspaces only when you enable them  ·  Your work is not used for training

Deep Dive

Start where your game is today

Build a bounded first playable inside Aura, begin a new project in an installed Unity, Godot, or Unreal editor, or connect the game you already have. Describe the result in ordinary language and review the design or supported work before it runs.

Three ways to begin

Choose the path that matches your game

No engine required

Build inside Aura

Start from an idea, review a small first-playable design, and play the first version inside Aura.

See the tutorial
Engine installed separately

Start a new game in an engine

Choose Unity, Godot, or Unreal, review the scope and location, then approve project creation.

Choose an engine tutorial
Bring your current work

Connect an existing project

Select your current game, confirm context and action readiness, and ask a safe first question.

Choose a connection tutorial
🧠

GDD Synchronization

Attach a supported design document so Aura can retrieve relevant passages when a request needs design context.

  • Open a project and use the top-bar GDD control to attach PDF, DOCX, Markdown, or text design documents.
  • Use retrieved lore, mechanics, and tuning constraints when they are relevant to the request.
  • Turn ordinary art requests and optional quality references into an original project-wide direction for characters, environments, animation, effects, interface, camera, and engine import.
  • Reuse suitable approved assets and review any material restyle or replacement before it changes the project.
  • Review proposed GDD updates; Aura does not silently rewrite the design.
⚡

Available Editor Context

Aura can use the current file, selection, object, project structure, or host focus when the connected engine or editor provides it.

  • Attach a file or folder when the next request needs explicit context.
  • Review supported file or project actions before approval.
  • Unity, Godot, Unreal, VS Code, Visual Studio, and Rider integration files are included.
  • Engine and IDE support is qualified independently; context differs by workflow.
🏗️

Uses the Structure It Can See

Project structure, discovered symbols, rules, and selected files can help Aura propose work that fits the current game instead of answering from a blank prompt.

  • Project discovery and symbol extraction vary by engine and language.
  • Project rules give explicit guidance that you can review and change.
  • Generated work still requires normal review, testing, and source control.
🏠

Secure Local Execution

Aura AI is built for real projects that need trust. Project indexing and editor integration stay local by default. Pro cloud continuity and Cloud Loops use isolated cloud workspaces only when you explicitly enable them.

  • Core project context stays local; enabled cloud features disclose what they process and retain.
  • Necessary request context goes to the model provider and funding route you select.
  • Your content is not used to train models or improve other customers’ results.
📋

Project Context

Keep each conversation grounded in the active project, its GDD, indexed files, and connected editor state.

  • The left sidebar keeps projects and conversations separated.
  • Attach a file or folder when the next request needs explicit extra context.
  • Review proposed project changes before Aura applies them.
🎬

Reviewed Actions and Local Loops

Aura can propose supported project or engine actions in chat. You review the scope before approval and watch longer work move through its available lifecycle controls.

  • Aura proposes reviewed actions in chat before anything runs; approve, reject, or keep chatting.
  • Use a Local Loop for longer goals with visible progress, pause, resume, and stop controls.
  • Supported actions and recovery differ across Unity, Godot, Unreal, and IDE workflows.
  • Use native undo or Aura recovery where supported, plus normal version-control discipline.
📷

Checks and Visible Evidence

Supported workflows can show action results, checks, screenshots, or recovery information so you can decide whether the requested result is actually present.

  • Configured checks prove only the behavior they measure, not the quality of the whole game.
  • Attach a screenshot when you want a selected model to examine visible output.
  • Model usage applies to visual review and does not guarantee a correct repair.
🔄

Living GDD

Compare recorded design context with current work and review any proposed update before it becomes part of the project’s working knowledge.

  • Attach supported documents and retrieve relevant passages for the current request.
  • Review, apply, or reject proposed design-context changes where the workflow supports it.
  • Aura does not claim perfect reading, automatic truth, or silent synchronization.

Start building smarter today

Your game stays yours. Aura handles the tedious parts.

View Plans & Pricing