Unity AI Assistant Ask Plan Agent Modes - First Safe Session 2026

You install Unity AI, open Chat, type “add a weapon system,” and watch Agent start rewriting the Hierarchy while your credit meter quietly drains. That is not a first session—that is a recovery ticket.

This tutorial is a beginner evening path for the Unity AI Assistant on Unity 6: pick Ask → Plan → Agent in the right order, use Lite vs Ultra without burning the budget, decide in-editor Agent vs MCP/Gateway, and file a short safe-session verification card. Official mode definitions live in Unity’s Assistant modes and model tiers docs; Open Beta context is in Unity’s Unity AI Open Beta Now Live for Unity 6 announcement thread (May 2026).

Evidence note: Primary keyword unity ai assistant. Demand signals used for qualification include high Unity-engine organic search volume (Semrush parent keyword snapshot, Jun 2026 US) and strong engagement on Unity’s Open Beta introduction video (YouTube, ~55K views as of July 18, 2026). SERP gap: official docs plus a third-party mode guide—this URL adds a safe first session, credit diligence, and MCP vs Agent decision table.

Non-repetition: Unity AI Toolkit explained for beginners covers ML-Agents / NavMesh / behavior-tree era tooling—not Assistant modes. Top AI tools for Unity developers 2026 is a stack listicle, not a mode walkthrough. Help cousins for classic toolkit breakage stay at Unity AI Toolkit not working.

Pair how to build a simple AI game in Unity after you can chat safely, and the Unity AI prototype course when you want a longer project loop.

Why this matters now (July 2026)

Unity AI Open Beta went live for Unity 6 in May 2026. Studios are adopting Ask / Plan / Agent while still confusing them with older “Unity AI” phrases (ML-Agents, Behavior Designer, Sentis). Credits, model tiers (Lite / Ultra), and write permissions make a reckless first Agent prompt expensive—and scene-damaging.

What changed for micro-studios:

1. Modes are product truth — Ask is read-only guidance; Plan writes a reviewable plan; Agent can modify the project with approvals (official comparison).
2. Ultra costs more — Docs note Ultra is for complex multi-step work and falls back to Lite if capacity is unavailable.
3. Community onboarding is video-heavy — Unity’s Open Beta intro already drew tens of thousands of views (video); written safe-session checklists still lag.
4. SERP is docs-first — GamineAI can win by teaching order of operations and studio diligence, not restating the mode table alone.

Direct answer: Tonight, install Assistant for Unity 6, run one Ask on a throwaway scene, run one Plan you can reject, only then try a tiny Agent action with permissions tight, log credits before/after, and save release-evidence/ai/unity_ai_safe_session_receipt_v1.json with unity_ai_safe_session_ok: true only if verification passes.

Who this session is for

Time: about 90–120 minutes for a first safe session.
Prerequisites: Unity 6 project (throwaway clone preferred); package access to Unity AI Assistant per current install docs; willingness to not start in Agent.

Who should skip tonight

• Teams still on Unity 2022 LTS without a Unity 6 evaluation project.
• Anyone hunting ML-Agents training recipes—use the toolkit beginner post instead.
• Production main branch with no VCS checkpoint (stop; branch first).

What Ask, Plan, and Agent actually do

From Unity’s documented mode model (modes manual):

Beginner mnemonic: Ask = textbook. Plan = blueprint. Agent = contractor with a clipboard.

Example prompts (copy-safe)

Ask (safe):
How should I structure a simple weapon pickup in Unity 6 URP without rewriting my Input System?

Plan (reviewable):
Create a step-by-step plan to add a weapon pickup prefab and a debug HUD ammo counter. Do not implement until I approve.

Agent (only after Plan approve, tiny scope):
Create an empty GameObject named WeaponPickup_DEBUG under the scene root. Do not edit other objects.

If your first Agent prompt is “rebuild my combat system,” you skipped the safe session.

Lite vs Ultra - credit diligence for companies and solos

Unity documents two tiers (same modes page):

Governance: Leads set a session credit budget before Agent is enabled. Solos write the budget on a sticky note. Nobody “just tries Ultra” on production.

Privacy / data: Treat prompts as potentially leaving the machine—do not paste unreleased NDAs, player PII, or partner keys into Chat. Prefer throwaway scenes for first sessions.

MCP / Gateway vs in-editor Agent

Many 2026 stacks mention MCP or a Gateway beside the in-editor Assistant. For a first safe session:

Decision: Complete tonight’s in-editor path first. Add MCP only after unity_ai_safe_session_ok is green and a lead owns the external tool allowlist. Do not treat MCP as a shortcut around Plan review.

Evening schedule (first safe session)

Step 1 - Project hygiene before Chat

1. Duplicate the project or create a git branch ai-assistant-safe-session.
2. Open a throwaway scene (SafeSessionLab.unity) with one Cube and one Light.
3. Snapshot Hierarchy (screenshot n0_hierarchy_before.png).
4. Record credits_before and Editor version in a text note.

If install fails, use Unity’s install docs from the package manual (install chat) and Unity’s manual overview (Unity AI)—do not debug on main.

Step 2 - Ask mode (read-only)

1. Set mode to Ask.
2. Prefer Lite.
3. Run one prompt about your throwaway scene.
4. Confirm Hierarchy and assets are unchanged.

Pass: You got an explanation; scene untouched.
Fail: Any write occurred—stop; check you were not in Agent.

Step 3 - Plan mode (blueprint only)

1. Switch to Plan.
2. Ask for a small plan (one prefab or one empty object)—not a full game feature.
3. Read every step. Delete or rewrite risky steps (mass deletes, package installs, Input System rewires).
4. Save the plan artifact Unity creates; export or screenshot n3_plan_review.png.
5. Do not approve implementation until Step 4.

Pass: Plan is saved and you can explain it in one sentence to a teammate.
Fail: You approved a 40-step combat rewrite on night one.

Step 4 - Agent mode (tiny write)

1. Tighten permission settings so destructive tools need confirmation.
2. Switch to Agent.
3. Run the single approved micro-action from the plan (or the empty GameObject example).
4. Screenshot Hierarchy after (n4_hierarchy_after.png).
5. Diff against before—only expected objects changed.

Pass: One intentional change; credits logged.
Fail: Surprise prefabs, materials, or script rewrites—revert branch; file unity_ai_safe_session_ok: false.

Step 5 - Verification card and receipt

Create release-evidence/ai/unity_ai_safe_session_receipt_v1.json:

{
  "schema": "unity_ai_safe_session_receipt_v1",
  "date_iso": "2026-07-18",
  "unity_version": "6000.x",
  "assistant_package": "com.unity.ai.assistant@noted",
  "modes_exercised": ["Ask", "Plan", "Agent"],
  "model_tier_default": "Lite",
  "ultra_used": false,
  "credits_before": 0,
  "credits_after": 0,
  "mcp_used": false,
  "hierarchy_unexpected_diff": false,
  "gates": {
    "S1_branch_or_backup": true,
    "S2_ask_no_writes": true,
    "S3_plan_reviewed": true,
    "S4_agent_tiny_scope": true,
    "S5_credits_logged": true,
    "S6_receipt_filed": true
  },
  "unity_ai_safe_session_ok": true,
  "notes": "First session; MCP deferred."
}

Latch: unity_ai_safe_session_ok is true only when S1–S6 pass.

Gate catalog S1–S6

Trend section - What studios argue after Open Beta

1. “Agent is just ChatGPT in Unity” — False; modes and write tools differ (docs).
2. “Start in Agent to save time” — Saves minutes, costs hours of undo.
3. “Ultra always” — Burns credits; docs push Lite for everyday work.
4. “This replaces ML-Agents” — Different problem class; keep toolkit explainer for training agents.

Common mistakes

1. First prompt in Agent on the vertical-slice scene.
2. Approving a Plan without reading delete steps.
3. Pasting partner secrets into Chat.
4. Enabling MCP before in-editor discipline exists.
5. Confusing Assistant modes with Behavior Trees / NavMesh “AI.”
6. No credit log—finance asks next week, nobody remembers.

Beginner vs developer path

Beginner: Follow the evening table; stay on Lite; one Ask, one Plan, one tiny Agent.
Developer: Add CI note that production branches require unity_ai_safe_session_ok before Agent is allowed in shared projects; document permission presets; compare credit burn across two sessions.

Company diligence table

Cost/ROI: Ninety minutes of discipline beats a day of merge archaeology. Security: Prompt hygiene + throwaway scenes. Ops: Keep Assistant package version pinned in the receipt.

Scenarios A–E

After tonight

1. Retry Plan→Agent on a slightly larger still isolated task.
2. Browse top Unity AI tools 2026 only after modes feel boring.
3. Forward cluster rows: AI game-maker honesty listicle; UE 5.8 lock trend; AI 3D import checklist.

Ask vs Plan vs Agent - decision tree with examples

Use this tree before you touch the mode picker. Unity’s Assistant modes and model tiers manual is the source of truth; the tree below is an operational translation for a first session.

START: You have a task in mind
|
+-- Do you only need an explanation, doc lookup, or tradeoff comparison?
|   YES --> ASK (read-only; no project writes)
|   Examples:
|     - "What is the difference between OnTriggerEnter and OnCollisionEnter for pickups?"
|     - "List three ways to show ammo count in URP without a custom shader."
|     - "What packages does Unity 6 recommend for a simple inventory UI?"
|
+-- Do you need a written sequence of steps you can reject or edit before any file changes?
|   YES --> PLAN (saves a reviewable plan; implementation waits for approval)
|   Examples:
|     - "Plan adding a WeaponPickup prefab with a SphereCollider trigger and a debug TextMeshPro label."
|     - "Plan a one-scene test for Input System rebinding—no package installs."
|     - "Plan renaming PlayerController fields for clarity—list every file touched."
|
+-- Do you have an approved plan step that is ONE small, named write?
|   YES --> AGENT (modifies project with permissions / confirmations)
|   Examples:
|     - "Create empty GameObject WeaponPickup_DEBUG at scene root only."
|     - "Add a BoxCollider to WeaponPickup_DEBUG; do not edit other objects."
|     - "Create Scripts/Debug/PickupProbe.cs with a single Debug.Log stub—no other scripts."
|
+-- Otherwise --> go back to ASK or PLAN; do not force Agent

Worked example (pickup feature):

Anti-patterns the tree rejects:

• Jumping to Agent because Ask “felt slow”—Ask is supposed to be read-only; slowness is not a signal to escalate writes.
• Using Plan as a magic “safe Agent”—Plan still costs credits and can propose destructive steps; you must read every line.
• Running Agent without a named object or file scope—“improve my project” is not a tree leaf.

If you cannot state the next action in one sentence (“create empty object X,” “add collider to X only”), you are not ready for Agent.

Credit and cost governance for small teams

Solo devs and two-to-five person studios share the same failure mode: Agent enabled, Ultra selected, no budget, surprise invoice. Unity documents Lite as the default tier and Ultra as higher capability with higher credit cost and possible fallback to Lite (modes manual). Governance turns that doc line into a weekly habit.

Session budget template (copy into your run note)

Three checkpoint moments (non-negotiable)

1. T+0 min — Record credits_before before opening Chat.
2. After Plan, before Agent — If credits_after_plan - credits_before exceeds half the session budget, defer Agent to tomorrow.
3. T+end — Record credits_after; attach to receipt S5.

Role split for micro-studios

Cost/ROI framing for companies

Ninety minutes of Ask→Plan→tiny Agent on a branch costs less than one afternoon reverting an unreviewed Plan that installed packages or rewired Input System assets. Finance does not need a slide deck— they need credits_before, credits_after, and ultra_used in unity_ai_safe_session_receipt_v1.json every time Agent runs on a shared project.

Weekly review (15 minutes): Sum receipts; flag any session where hierarchy_unexpected_diff was true; pin assistant_package version if credit burn spiked after a package bump.

MCP vs in-editor Agent - clarity and safe boundaries

In-editor Agent is Unity’s Assistant running inside the Editor with Unity-native tools, mode picker (Ask / Plan / Agent), and permission prompts documented in the Assistant modes package.

MCP (Model Context Protocol) / Gateway paths expose Assistant or compatible models to external tool servers—filesystem outside the project, CI hooks, issue trackers, custom scripts. They are valuable when a studio already has tool allowlists, audit logs, and an owner for what the model may call.

Safe boundaries:

1. Week one: In-editor only; mcp_used: false in every receipt.
2. Week two+: MCP read-only tools (docs search, issue lookup) before any MCP write tool.
3. Never: MCP write path on the same machine/session as production signing keys or unreleased build artifacts.
4. Do not use MCP to bypass Plan review—“run this shell on the repo” is still a write.

Decision rule: If you cannot explain your MCP allowlist in one paragraph, you are not ready to add it. Finish the in-editor path in Unity’s install chat flow first, then evaluate Gateway docs with your lead.

Safe session script - minute by minute

This script expands the evening table into a runnable clock. Adjust totals if install takes longer; do not skip verification blocks.

If you stall: At 0:35 with no Ask answer, check network and package version—do not switch to Agent. At 1:05 with a 40-step plan, reject and re-prompt with smaller scope. At 1:30 with surprise prefabs, revert branch immediately; do not “fix forward” on night one.

What never to paste into the Assistant

Unity’s Assistant sends prompts to cloud-backed models (Unity AI manual overview). Treat Chat like a shared Slack channel with an external vendor—not a private scratchpad on an air-gapped machine.

Never paste:

Safe substitutes:

• Use YOUR_API_KEY_HERE and configure real values in User Secrets or Editor-only ScriptableObjects excluded from VCS.
• Redact logs: replace player emails with [email protected].
• For architecture questions, describe patterns (“URP project with new Input System”) without pasting ProjectSettings/.
• Run first sessions on throwaway scenes with no proprietary art.

If a teammate already pasted a secret: rotate the credential, scrub local chat history if the product allows, and file an incident note—do not continue Agent on that thread.

Verifying S1–S6 - sample receipt expansion

The minimal receipt in Step 5 is the latch skeleton. Below is an expanded sample showing what “verified” looks like in practice. Replace values with your run; keep schema unchanged.

{
  "schema": "unity_ai_safe_session_receipt_v1",
  "date_iso": "2026-07-18",
  "unity_version": "6000.2.1f1",
  "assistant_package": "[email protected]",
  "modes_exercised": ["Ask", "Plan", "Agent"],
  "model_tier_default": "Lite",
  "ultra_used": false,
  "credits_before": 120,
  "credits_after": 107,
  "credit_delta": 13,
  "mcp_used": false,
  "hierarchy_unexpected_diff": false,
  "artifacts": {
    "hierarchy_before": "release-evidence/ai/n0_hierarchy_before.png",
    "plan_review": "release-evidence/ai/n3_plan_review.png",
    "hierarchy_after": "release-evidence/ai/n4_hierarchy_after.png"
  },
  "gates": {
    "S1_branch_or_backup": {
      "pass": true,
      "evidence": "git branch ai-assistant-safe-session; scene SafeSessionLab.unity"
    },
    "S2_ask_no_writes": {
      "pass": true,
      "evidence": "Ask prompt on Lite; Hierarchy hash unchanged vs n0 screenshot"
    },
    "S3_plan_reviewed": {
      "pass": true,
      "evidence": "Plan 4 steps; removed package install step; n3_plan_review.png"
    },
    "S4_agent_tiny_scope": {
      "pass": true,
      "evidence": "Only WeaponPickup_DEBUG added; matches approved step 1"
    },
    "S5_credits_logged": {
      "pass": true,
      "evidence": "120 -> 107 (delta 13); Ultra not used; within session budget 40"
    },
    "S6_receipt_filed": {
      "pass": true,
      "evidence": "This file committed on branch before merge request"
    }
  },
  "unity_ai_safe_session_ok": true,
  "notes": "First session; MCP deferred. Lead: [email protected]."
}

Per-gate verification commands (developer path):

Fail-closed: If any gate is false, set unity_ai_safe_session_ok: false and list the failing gate in notes. Do not merge to main until a green rerun exists.

Common failure modes when Agent edits break compiles

Agent can leave the project in a compiling or broken play mode state even when Hierarchy looks fine. These are the patterns teams hit in the first week of Open Beta (Unity discussions thread).

Compile verification loop (add after 1:30 in the minute script):

1. Wait for Editor compile bar to finish.
2. Open Console; filter errors only.
3. Enter Play Mode on SafeSessionLab.unity for 10 seconds.
4. If errors exist, do not ask Agent to “fix everything”—revert, tighten scope, rerun one micro-action.

Document compile status in receipt notes: compile_clean: true/false. A green Hierarchy with red Console is still unity_ai_safe_session_ok: false for production branches.

Extra FAQ

When should I use Ask instead of Plan for a “how do I implement X” question?

If you want explanation, comparisons, or doc pointers with no saved implementation steps, use Ask (modes manual). Switch to Plan when you need a step list you can edit before any write.

Can I run multiple Agent actions in one safe session?

Night one: one micro-action only. After unity_ai_safe_session_ok is true on a throwaway project, session two may add two actions if each maps to an approved Plan step and credit budget allows.

How do I know if Unity fell back from Ultra to Lite?

Unity documents that Ultra may fall back to Lite when capacity is unavailable (modes page). Log the tier shown in Chat for each Plan; if results feel shallow after selecting Ultra, assume fallback and retry later—do not stack Ultra calls to “force” quality.

What permission settings should I tighten before first Agent?

Enable confirmations for destructive operations (delete, mass rename, package changes). Exact UI labels vary by package version—check current install chat docs for your pin.

Is a safe-session receipt required on solo projects?

Not legally—operationally yes if you ever merge to a team repo or show diligence to a publisher. Solos benefit the same way: future-you inherits proof instead of guessing what Agent changed.

What if Ask accidentally wrote to the project?

You were not in Ask mode, or an experimental setting overrode read-only behavior. Stop, revert branch, re-read Assistant modes, and file S2 as failed.

Key takeaways

• Unity AI Assistant on Unity 6 uses Ask / Plan / Agent—start Ask, review Plan, then tiny Agent.
• Lite is the default credit-safe tier; Ultra is for hard Plans and costs more (Unity docs).
• Open Beta momentum is real (Unity discussions; intro video)—discipline still missing from SERP.
• Defer MCP/Gateway until in-editor safe session is green.
• Latch unity_ai_safe_session_ok with gates S1–S6 and a receipt JSON.
• This is not the ML-Agents toolkit tutorial—link out when training is the real job.

FAQ

What is Unity AI Assistant Ask vs Plan vs Agent?

Ask answers with read-only tools. Plan builds a reviewable implementation plan. Agent can modify the project with approvals. Official comparison: Assistant modes.

How do I run a first safe Unity AI Assistant session?

Branch, use a throwaway scene, Ask once, Plan once without implementing, then one tiny Agent action, log credits, and file a verification receipt.

Does Unity Ultra always give better results?

Ultra is for complex or ambiguous tasks and costs more credits; Unity may fall back to Lite. Prefer Lite for everyday Ask/Plan.

Is Unity AI Assistant the same as ML-Agents?

No. Assistant is chat/modes tooling in the Editor. ML-Agents and classic “AI toolkit” topics are covered separately in Unity AI Toolkit explained.

Should I enable MCP on night one?

No. Finish the in-editor Ask→Plan→Agent path and latch the safe-session receipt first.

What does unity_ai_safe_session_ok mean?

All gates S1–S6 passed and unity_ai_safe_session_receipt_v1.json matches what you actually ran.

Conclusion

Unity AI Assistant is useful when modes stay in order and credits stay visible. Run one safe session, keep Agent tiny, leave MCP for later, and treat the receipt as studio hygiene—not theater. Then scale the same discipline to real features.

Related reads

• Unity MCP with Cursor - First Safe Editor Bridge Session 2026
• 12 AI Game Maker Tools Indies Should Test Before Betting Steam - 2026
• Unity AI Toolkit Explained for Beginners
• Top AI Tools for Unity Developers 2026
• How to Build a Simple AI Game in Unity
• Unity AI Toolkit Not Working - Help
• Unity AI Prototype Course
• Assistant modes and model tiers - Unity Docs
• Unity AI Open Beta Now Live for Unity 6