hera-agent-unity

Give your AI coding agent hands, eyes, and a checklist inside Unity.

_{Codex, Claude, Cursor, Copilot, AntiGravity, and other shell-capable agents can inspect your live Unity Editor, change it, run it, test it, see the result, and keep fixing until the evidence says it is done.}

Start in 3 steps · What can it do? · Why Hera? · How good is it? · Examples · Commands

English · 한국어

Hera in one minute

An AI can write Unity C# without Hera, but it cannot reliably know what your live Editor looks like after the code is written.

Normally the loop looks like this:

text

You ask the AI
   ↓
AI writes code
   ↓
You open Unity and wait for compile
   ↓
You copy the error back to the AI
   ↓
AI fixes it
   ↓
You press Play and explain what happened
   ↓
repeat...

Hera closes that loop:

text

You ask the AI
   ↓
AI uses Hera
   ↓
Unity compiles, runs, tests, clicks UI, captures the result
   ↓
Hera gives the real result back to the AI
   ↓
AI fixes what failed and checks again
   ↓
verified result

A simple way to think about it:

The AI is the brain. Hera gives that brain hands to operate Unity, eyes to inspect the result, and a checklist so it does not stop while the project is still broken.

Hera does not replace Unity and it does not replace the coding agent. It connects the two so the agent can work with facts from your actual project instead of guessing from source code alone.

What problem does it solve?

Unity development has a feedback loop that lives outside the source files.

A change can look correct in code and still fail because:

Unity did not compile it;
the wrong Scene is open;
a GameObject or Component is missing;
the Inspector has a different serialized value;
a Unity API changed in your Editor version;
the Console contains an exception;
Play Mode behaves differently from Edit Mode;
a button is visually present but cannot receive input;
a UI layout is technically valid but looks wrong;
the AI says "done" before it has actually checked any of those things.

Hera lets the agent ask the real Editor instead.

bash

hera-agent-unity status
hera-agent-unity console --type error
hera-agent-unity scene info
hera-agent-unity editor play --wait
hera-agent-unity test --mode PlayMode

If the selected Editor is not running, Hera can bootstrap the exact project before Connector discovery:

bash

hera-agent-unity --project C:/Projects/Game editor launch
hera-agent-unity --project C:/Projects/Game editor restart

The project version comes from ProjectSettings/ProjectVersion.txt; the matching Unity Hub install comes from UNITY_HUB_EDITOR or the platform default (%ProgramFiles%\Unity\Hub\Editor on Windows). Pass --hub-root for a custom Hub location. Startup uses normal Package Manager behavior, not -noUpm, and returns when the new process publishes that exact project's heartbeat. On Windows, Hera also restores the standard common-profile environment for the Unity child when an agent shell omitted it, so UPM path resolution still starts with the same baseline as a normal desktop launch.

The important part is not the command names. The important part is that the agent can observe → change → run → verify → repair without making you act as the courier between the AI and Unity.

What can it actually do?

You can use Hera for tiny one-line checks or for a full AI-assisted Unity workflow.

What you want the AI to do	What Hera gives it
Check whether Unity is healthy	Live Editor status, version, project, compile state, Console errors
Start or restart the right Editor	Launch or restart the exact project from its recorded Unity version and wait for that project's heartbeat
Understand the current Scene	Scene info, GameObject search, Component and Inspector reads
Change the Scene	Create/save Scenes; create, duplicate, rename, parent, transform, tag, layer, or delete GameObjects
Edit Components	Add, remove, inspect, and change serialized Component values
Work with project assets	Find, create, copy, move, or delete assets under `Assets/`
Run project-specific C#	Execute C# inside the loaded Editor with access to Unity APIs and project assemblies
Make animations	Author AnimationClips, AnimatorController state machines, and Timeline tracks/clips
Test a feature	Run EditMode and PlayMode tests and keep the result across domain reloads
Play the game	Enter Play Mode, wait for the real state change, inspect, then stop
See what Unity rendered	Capture Scene/Game views or isolated objects, plus bounded uGUI identity/coordinate and Camera.main 3D physics evidence
Test Unity input	Inspect uGUI raycasts, or synthesize Input System keyboard/mouse sequences, record them, and replay them in Play Mode
Build UI	Author uGUI layouts and verify the generated result
Recreate a reference UI	Measure a reference, build the real Unity UI, capture it, compare, and iterate
Improve game feel	Give the agent recipes for shake, hit stop, feedback, camera, sound, rewards, and accessibility
Clean up generated-looking UI	Detect common spacing, hierarchy, typography, color, and decoration problems
Create your own studio commands	Add project-specific `[HeraTool]` actions that appear automatically
Work with several open Editors	Target the intended project and keep that project identity through port changes
Require approval for risky work	Preflight destructive operations and continue only with the matching approval token

In short, Hera is not just a "press Play" remote. It is a bridge for the whole edit-and-check loop around a running Unity project.

Why use Hera?

1. The AI can check its own work

Without Editor access, the agent often ends with:

"This should work."

With Hera, it can finish with evidence such as:

text

compile: passed
console errors: 0
EditMode tests: 18/18
PlayMode tests: 6/6
button click: verified through EventSystem
final Game View: captured

That difference is the main reason Hera exists.

2. You stop being the copy-and-paste bridge

You no longer need to repeatedly:

copy code from the AI;
switch to Unity;
wait for compile;
copy errors back;
explain the Scene hierarchy;
press Play;
describe what happened.

The AI can perform most of that loop itself.

3. It works with the tools you already use

The normal production path is a CLI. Any agent that can run shell commands can use it.

Codex
Claude Code
Cursor
GitHub Copilot
AntiGravity
scripts and CI jobs
your own automation

No Python server is required. MCP is optional, not mandatory.

4. It is designed for AI context, not just humans

A giant tool response becomes more input for the model to read. Hera therefore gives common commands compact views such as IDs-only GameObject searches and on-demand tool schemas.

The goal is simple: send the agent the smallest amount of Unity state that is enough to make the next decision.

5. It knows that "request sent" is not the same as "work finished"

Unity recompiles scripts, reloads domains, changes ports, enters Play Mode, runs tests, and sometimes drops a connection while doing it.

Hera tracks these workflows instead of treating a successful HTTP send as proof that Unity is finished.

6. It can grow with your project

Start with the built-in commands. Later you can add a [HeraTool] for the workflow your own project repeats every day: build a dungeon room, validate a quest graph, bake a table, spawn a test battle, or check your studio-specific asset rules.

How good is it?

Hera avoids vague "AI magic" claims. The repository keeps concrete measurements and compatibility evidence instead.

Small responses for common agent reads

Measured low-token baselines for list --compact are about 93 estimated tokens across the tested Unity versions. find_gameobjects --ids measured 49 to 55 estimated tokens in the retained cross-version fixtures.

Unity Editor	`list --compact`	`find_gameobjects --ids`
2022.3.62f2	93 T	54 T
2023.2.22f1	93 T	54 T
6000.3.5f2	93 T	49 T
6000.5.0f1	93 T	55 T

T is a simple ceil(UTF-8 bytes / 4) estimate for Hera's CLI payload only. It is not provider billing telemetry. Full methodology: token-reduction benchmark.

Compatibility is checked across Unity generations

Supported Unity versions are Unity 6+ (6000.0 minimum), split into three compatibility buckets by compiler/API boundary. The release compile gate runs the Connector's exact source in a representative Editor per bucket:

Bucket	Representative Editor	Last full-gate result
6000.0 - 6000.2	6000.0.35f1	PASS
6000.3 - 6000.4	6000.3.5f2	PASS
6000.5+	6000.5.6f1	PASS

CLI and Connector versions are intentionally separate.

v0.2.0 was exercised in a live Editor, not only compile-tested

The final release candidate was loaded as Connector 0.0.86 in Unity 6000.5.6f1 with Input System 1.20.0 and driven through real Play Mode before release. The retained smoke evidence recorded:

31 tools / 80 actions from the live catalog;
keyboard down/up and mouse position synthesis in Play Mode;
a bounded input sequence completing successfully;
an input recording with 5 events / 588 bytes, then two successful replays of the same file;
zero Hera-owned controls left held after replay;
Connector ReleaseGateTests: 18/18 PASS;
Unity Console errors after the run: 0;
graceful Editor shutdown with 0 new scene-recovery backups, while the disposable fixture manifest and lock file were restored.

This complements the five-version compile matrix with an end-to-end Editor regression on the released capability set.

A real game-creation run reached a verified playable result

The retained Crystal Forge scenario asked an AI to author code and tests, build UI, compile, drive Unity EventSystem input, run tests, capture the rendered result, and leave the Editor clean.

Final result: PASS after repair. First attempt: FAIL.

The measured execution window was 15 minutes 52 seconds. The run is useful because the failures were kept instead of being edited out. It showed why a closed verification loop matters: hidden state was correct before the UI was actually visible, and the agent had to observe, repair, and verify again.

This is not a claim that Hera makes every task succeed on the first try, and it is not an "X% smarter AI" benchmark. It demonstrates something more practical: Hera can give an agent enough real Editor feedback to find and repair integration failures instead of stopping at the first plausible answer.

Full evidence: Crystal Forge real-world benchmark.

How do I use it?

There are only two pieces:

text

your computer                 your Unity project
──────────────                ──────────────────
Hera CLI        <---------->  Hera Unity Connector

Step 1. Install the CLI

The simplest cross-platform option is npm:

Terminal

npm install --global hera-agent-unity

Or use the native installer.

Windows PowerShell

powershell

powershell -ExecutionPolicy ByPass -c "irm https://raw.githubusercontent.com/NotNull92/hera-agent-unity/main/install.ps1 | iex"

macOS / Linux

Terminal

curl -fsSL https://raw.githubusercontent.com/NotNull92/hera-agent-unity/main/install.sh | bash

Check it:

bash

hera-agent-unity version

Other CLI installation methods

Go install

bash

go install github.com/NotNull92/hera-agent-unity@latest

Manual

Download a binary from GitHub Releases, then run:

bash

hera-agent-unity install

Step 2. Add the Unity package

In Unity:

text

Window -> Package Manager -> Add package from git URL

Paste:

text

https://github.com/NotNull92/hera-agent-unity.git?path=AgentConnector

Or add it to Packages/manifest.json:

json

"com.notnull92.hera-agent-unity": "https://github.com/NotNull92/hera-agent-unity.git?path=AgentConnector"

The Connector starts automatically when the Editor opens.

To pin an existing Connector tag:

json

"com.notnull92.hera-agent-unity": "https://github.com/NotNull92/hera-agent-unity.git?path=AgentConnector#connector-<version>"

The current released Connector pin is:

text

https://github.com/NotNull92/hera-agent-unity.git?path=AgentConnector#connector-0.1.2

Step 3. Open Unity and check the connection

bash

hera-agent-unity doctor --json
hera-agent-unity status

You should see the real project path, Unity version, Editor state, and connection information.

Now you can simply tell your agent:

text

Use hera-agent-unity for this Unity project.
Check the current Editor state first.
Make the requested change.
Compile it, read the real Console errors, verify the changed object or UI,
and do not say it is finished until Unity is in a clean state.

That is the normal Hera workflow.

What can I do with it?

Fix a compiler or runtime error

text

Use Hera. Read the Unity Console, find the actual error, fix the code,
compile again, and keep repeating until the error Console is clean.

Typical commands behind the scenes:

bash

hera-agent-unity console --type error --lines 20
hera-agent-unity editor refresh --compile
hera-agent-unity console --type error --lines 20

Build a feature and prove it works

text

Implement the inventory filter.
Use Hera to compile it, run the relevant EditMode and PlayMode tests,
enter Play Mode if needed, and report the final evidence.

Reproduce a gameplay bug

text

Open the correct Scene, enter Play Mode, inspect the related objects,
reproduce the bug, fix it, then reproduce the same path again to prove the fix.

Build UI from a reference image

Hera can give the agent a measurement loop instead of an eyeballing loop:

text

reference image
   ↓ sample colors / measure layout
Unity UI
   ↓ capture
compare
   ↓ fix
capture again

Example commands:

bash

hera-agent-unity manage_ui create --element panel --name HUD
hera-agent-unity manage_ui set_anchor --path /Canvas/HUD --preset stretch --snap true
hera-agent-unity manage_components set --path /Canvas/HUD --property m_Color --value '#1A1A2E'
hera-agent-unity screenshot --overlay --output_path hud_built.png

Use manage_ui, manage_components, and screenshot --overlay in small verified batches.

Verify buttons without guessing screen coordinates

bash

hera-agent-unity input state
hera-agent-unity input inspect --path /Canvas/StartButton --details true
hera-agent-unity input click --path /Canvas/StartButton --settle_frames 2

This verifies Unity's EventSystem path. It is not a physical Windows/macOS mouse click, so Hera reports those two kinds of evidence separately.

Projects that already use the optional Input System package can also verify gameplay input without adding a Hera dependency:

bash

hera-agent-unity input state --backend inputsystem
hera-agent-unity input keyboard --key space --mode press
hera-agent-unity input mouse --mode click --button left --position 640,360
hera-agent-unity call input --json '{"action":"sequence","steps":[{"action":"keyboard","key":"space","mode":"down"},{"action":"keyboard","key":"space","mode":"up"}]}'
hera-agent-unity call input --json '{"action":"record","mode":"start"}'
hera-agent-unity call input --json '{"action":"record","mode":"stop"}'
hera-agent-unity call input --json '{"action":"replay","path":"Library/HeraAgent/Recordings/input.json"}'

Keyboard, mouse, bounded sequence, recording capture, and replay require Play Mode. Recordings use the bounded hera.input-recording/1 JSON format under the project or system temp directory; replay validates the complete file before mutation and reuses sequence-owned cleanup. Hera resolves the package at runtime, never creates devices, and releases any held controls when Play Mode exits.

Automate repetitive Scene work

You can ask an agent to:

create a test arena;
place prefabs under a new root;
add and configure Components;
create ScriptableObject assets;
wire Animator states;
save the Scene;
run validation afterwards.

Create studio-specific tools

If your project has a repeated workflow, expose it as a custom [HeraTool]. The tool appears in Hera's live catalog automatically.

Examples:

build_test_battle
validate_item_database
spawn_quest_fixture
bake_localization_table
check_prefab_rules

Hera can therefore start as a generic Unity bridge and gradually become a CLI for your own game production pipeline.

Ultra Hera: make "done" mean checked

Do the work. Check the work. Only then report the result.

Ultra Hera is a verification rule for AI-assisted Unity work. It does not write the feature by itself. It tells the agent how carefully to check the work it just did through Hera.

Find it in:

text

HeraAgent -> Hera Settings -> Ultra Hera

Mode	Easy meaning
`Off`	No extra verification rule.
`Light`	Default. Compile/check state, read errors, and re-read the changed target before finishing.
`Ultra`	For important work. Add stronger evidence such as tests, Play Mode, Inspector reads, and screenshots.

Think of Light as a seatbelt check and Ultra as a pre-flight inspection.

Use Ultra when the request sounds like:

"verify it exactly";
"play it and confirm";
"match this UI";
"check the Inspector too";
"do not finish until all tests pass".

The goal is simple: the agent should not close the task while Unity is still broken.

More than Editor control

Hera includes optional guidance and authoring systems that help the agent do more than change raw objects.

Game Feel Mode (Beta)

Helps the agent think about how gameplay feels, not only whether it functions: control feel and input forgiveness, the Update / FixedUpdate / LateUpdate split, screen shake, hit stop, knockback, camera, sound, reward presentation, haptics, session pacing, and accessibility constraints.

bash

hera-agent-unity asset-config gamefeel on
hera-agent-unity game_feel hit_stop
hera-agent-unity game_feel unity_frame_loops

The knowledge is guidance. Hera does not secretly add heavy runtime systems to your game.

Game Feel UI Mode (Beta)

Adds practical UI feedback recipes such as hover scale, press squash, popup entrance, count-up text, health-bar response, cooldown feedback, and accessibility baselines.

bash

hera-agent-unity asset-config gamefeel-ui on

Unity De-slop Mode (Beta)

Helps agents catch common generated-looking UI habits: unnecessary decoration, weak spacing systems, box-in-box layouts, decorative italics, inconsistent colors, and other visual tells.

bash

hera-agent-unity asset-config uislop on
hera-agent-unity ui_slop box-in-box

The rules include exceptions so functional game UI such as inventory cells is not flattened just because it is repetitive.

Asset preferences and compiler defaults

Known assets such as Odin and DOTween can be enabled as preferences. Enabling one does not install it; it tells generated agent rules and AI JSON to prefer that API when the project actually contains it.

bash

hera-agent-unity asset-config enable odin_inspector
hera-agent-unity asset-config --json
hera-agent-unity asset-config set-csc <path-to-csc>
hera-agent-unity asset-config set-dotnet <path-to-dotnet>

The compiler defaults are read by the next exec call, without restarting the Editor. You can configure the same values from HeraAgent -> Hera Settings.

Command overview

You do not need to memorize these. They are here so you can understand the surface Hera gives an agent.

Command	Plain-language purpose
`doctor --json`	"Is Hera installed and can it reach Unity?"
`status` / `ping`	Check Editor state and liveness.
`list --compact`	Discover available built-in and project-specific tools cheaply.
`call <tool>`	Validate a strict live tool contract, then call it.
`console`	Read or clear the real Unity Console.
`scene`	Inspect, create, load, save, activate, list, or close Scenes; dump the GameObject tree.
`find_gameobjects`	Search the loaded Scene hierarchy.
`manage_gameobject`	Create and edit GameObjects.
`manage_components`	Read, add, remove, or modify Components.
`manage_assets`	Work with project assets under `Assets/`, bring in a file from outside the project, and trace what an asset uses or what still uses it.
`manage_prefab`	Create, instantiate, and edit prefab assets, and apply, revert, or unpack an instance's overrides.
`manage_animation`	Author AnimationClips and AnimatorController state machines, and read them back.
`manage_timeline`	Create and inspect optional Timeline assets, tracks, and clips without taking a package dependency.
`manage_settings`	Read and change physics, time, quality, player, audio, graphics, legacy input, lighting, and legacy NavMesh settings with previews and approval.
`bake`	Trigger, poll, cancel, or clear lighting / NavMesh / occlusion bakes.
`build`	Queue a Player build for the active target and read the compact report.
`exec`	Run arbitrary project-aware C# inside the Editor.
`editor`	Launch/restart the exact project, or play, stop, pause, refresh, and compile.
`test`	Run, list, resume, or cancel Unity tests, selecting by name, category, or assembly.
`task`	Inspect durable test/package work without contacting Unity.
`screenshot`	Capture Scene/Game views, ScreenSpaceOverlay canvases, or isolated objects; optionally return bounded uGUI, 3D collider, or UI Toolkit Editor-window metadata.
`input`	Test uGUI, or synthesize optional Input System keyboard/mouse/sequence input and record/replay it in Play Mode.
`profiler`	Read profiler hierarchy snapshots and one-call performance stats.
`game_feel`	Query game-feel guidance.
`ui_slop`	Query UI cleanup guidance.
`batch`	Run several operations in one request.
custom `[HeraTool]`	Call tools defined by your own Unity project.

Full reference: docs/COMMANDS.md.

Teach your AI agent to use Hera automatically

You can put Hera's operating rules in the project so the agent knows to inspect Unity before guessing.

Codex plugin

bash

codex plugin marketplace add NotNull92/hera-agent-unity --ref main

Then open /plugins, choose Hera Agent Unity, and enable Hera Unity.

Standalone Agent Skill

Terminal

npx skills add NotNull92/hera-agent-unity --skill hera-agent-unity --agent codex

Shared `AGENTS.md`

bash

hera-agent-unity doctor --agent-rules --compact >> AGENTS.md

The compact default guidance is intentionally small. Its reviewed baseline is 2,277 UTF-8 bytes and contains the important rules for bootstrap, targeting, approvals, safety, and verification. The full guide is available on demand.

This repository also ships templates for Cursor, Copilot, AntiGravity, Continue, and other agent environments under examples/rules.

Safety and reliability in plain language

Hera can make real changes to a Unity project, so "fast" is not enough. It also needs to know when to stop.

It identifies the project, not just a port number

Unity can change its local port after a domain reload or restart. Hera prefers the normalized full project path as the Editor identity and treats the port as a temporary endpoint.

If several Editors are open, use:

bash

hera-agent-unity --project /full/path/to/project status

Ambiguous targeting fails instead of guessing.

Risky operations can require approval

Approval-gated work is preflighted first. The returned token is tied to that exact request and is single-use. Changing the target or arguments invalidates the approval. In a shell or CI job you already trust, --yes (env: HERA_AGENT_APPROVE=1) answers the preflight in the same invocation instead of returning APPROVAL_REQUIRED — the preflight and the operation ledger still run.

It does not blindly repeat an uncertain mutation

If a response disappears during a reload or timeout, Hera checks fresh Editor ownership/state before an eligible retry. A mutation is not resent merely because the network response was unclear.

Slow tests can be resumed instead of started again

A long Test Runner job can outlive a normal request window. Hera stores durable run state so an agent can resume waiting for the same run instead of accidentally starting another test execution.

Unity versions

Unity version	Status	Representative verification
6000.0 - 6000.2	Supported	`6000.0.35f1`
6000.3 - 6000.4	Supported	`6000.3.5f2`
6000.5+	Supported	`6000.5.6f1` release gate
Older than 6000.0	Not supported	Minimum is Unity 6 (6000.0)

Version-specific behavior is checked against live Editors rather than assumed from one Unity version.

CLI first, MCP optional

The production default is the normal CLI.

text

AI / terminal -> Hera CLI -> localhost Connector -> Unity Editor

That means any shell-capable coding agent can use Hera without configuring MCP.

CLI v0.1.0+ also ships an experimental, default-off, stdio-only MCP adapter for hosts that intentionally want MCP discovery and invocation. It uses the same Hera execution core instead of creating a second Unity backend.

text

AI with MCP -> optional Hera MCP adapter -> same Hera execution core -> Unity

MCP does not magically make the model smarter. It is another way to expose the same Unity capabilities. Hera keeps the CLI path as the default because it remains simple, explicit, and broadly compatible.

When MCP is explicitly enabled, Hera exposes the three-tool Compact surface by default. Select an action through tool_search and tool_describe, then use tool_call; opt into Profile or Full only when the larger static schema payload is worth it.

MCP setup and compatibility boundaries: docs/MCP.md.

Current release

CLI / GitHub Release: v0.2.17 with five native binaries
npm: 0.2.17 (latest)
Unity Connector / OpenUPM: 0.1.3 (latest)
Official MCP Registry: 0.2.17 (active)
License: Apache-2.0

All four channels ship the same release: the npm and MCP Registry publishes are chained to the GitHub Release, so npm install -g hera-agent-unity and the GitHub binaries stay in step.

The two version numbers are separate on purpose. The CLI and the Unity package can evolve independently while keeping their compatibility contract explicit.

v0.2.17 clears two races that reported a healthy Editor as broken: the first typed call after a recompile no longer fails on a domain epoch the reload had already replaced, and editor restart no longer warns about a project lock the exiting Editor was still holding. Connector 0.1.3 adds the one ingress the asset tools lacked — manage_assets import brings a file from outside the project into Assets/, which a client on the compact MCP default cannot otherwise do — and lets screenshot name the camera it renders and cap its longest edge. The live catalog exposes 34 tools / 133 actions.

For release-by-release engineering detail, read CHANGELOG.md instead of treating the main README as a migration log.

How does Hera work internally?

text

Terminal / AI agent
        |
        | hera-agent-unity command
        v
Go CLI
        |
        | localhost HTTP
        v
Unity Editor package
        |
        | serialized Unity main-thread work
        v
Scene, Console, Play Mode, Assets, Tests, UI

The Unity package opens a local HTTP listener. The CLI selects the intended Editor from local heartbeat state and sends the command. Unity work is marshaled to the Editor main thread.

Domain reloads and long-running operations use filesystem-backed state so compilation, tests, and recovery can survive the HTTP listener being recreated.

Architecture details: docs/ARCHITECTURE.md.

Advanced exec, token, and async notes

Prefer dedicated commands over arbitrary exec when one exists.
Use small projections such as find_gameobjects --ids when IDs are enough.
Side-effecting exec snippets should normally return null or nothing rather than a large status object.
Do not return a full UnityEngine.Object unless you truly need its reflected graph.
Use --strict or throw an exception when a logged error must fail the CLI operation.
Use --security-mode restricted when a snippet only needs platform APIs and should be denied file, network, process, reflection, native, threading, UnityEditor, and project-assembly access. Full Access remains the default.
Use exec --check when you want to compile-check a snippet without executing it.
Long asynchronous workflows are better represented as tracked [HeraTool] actions or durable task/test operations than as detached work inside a one-shot exec.

The complete agent operating guide is AGENTS.md.

FAQ

Does Hera make the AI smarter?

No. Hera gives the AI better access to your real Unity state and better ways to verify the result. The coding model still makes the design and implementation decisions.

Does it need Python?

No. The normal install is one native CLI plus one Unity package.

Do I need MCP?

No. The CLI is the production default. MCP is optional and default-off.

Can it control more than one open Unity Editor?

Each command targets one Editor. If several are open, use the full --project path for the clearest selection. Hera tracks the selected project identity even if the local port changes.

Can it physically click the Unity window?

The input command sends Unity EventSystem events for uGUI QA and can synthesize optional Input System keyboard/mouse state in Play Mode. Both prove Unity-level behavior, not a physical operating-system click. Physical click evidence must be reported separately.

What should I do if it cannot connect?

bash

hera-agent-unity doctor --json

Also check that the Unity package is installed and the Editor has finished compiling.

Where are the detailed docs?

Projects using Hera

Project	Notes
NoMoreRolls	Solo-developed Unity game. Built with AI driving the Editor through Hera.

https://github.com/user-attachments/assets/15d353e4-b7bb-4534-bbca-c27de0792147

_{NoMoreRolls - full Play Mode video from a Unity game built with Hera-assisted Editor work.}

Author

Victor - Unity/C# developer with 6+ years of live-service MMORPG production experience.

GitHub: @NotNull92

Discord: Join the Hera community

Support

Hera is free and licensed under Apache-2.0. If it saves you time, you can support development:

License

Apache License 2.0. See LICENSE and NOTICE.

hera-agent-unity

Hera in one minute

What problem does it solve?

What can it actually do?

Why use Hera?

1. The AI can check its own work

2. You stop being the copy-and-paste bridge

3. It works with the tools you already use

4. It is designed for AI context, not just humans

5. It knows that "request sent" is not the same as "work finished"

6. It can grow with your project

How good is it?

Small responses for common agent reads

Compatibility is checked across Unity generations

v0.2.0 was exercised in a live Editor, not only compile-tested

A real game-creation run reached a verified playable result

How do I use it?

Step 1. Install the CLI

Step 2. Add the Unity package

Step 3. Open Unity and check the connection

What can I do with it?

Fix a compiler or runtime error

Build a feature and prove it works

Reproduce a gameplay bug

Build UI from a reference image

Verify buttons without guessing screen coordinates

Automate repetitive Scene work

Create studio-specific tools

Ultra Hera: make "done" mean checked

More than Editor control

Game Feel Mode (Beta)

Game Feel UI Mode (Beta)

Unity De-slop Mode (Beta)

Asset preferences and compiler defaults

Command overview

Teach your AI agent to use Hera automatically

Codex plugin

Standalone Agent Skill

Shared AGENTS.md

Safety and reliability in plain language

It identifies the project, not just a port number

Risky operations can require approval

It does not blindly repeat an uncertain mutation

Slow tests can be resumed instead of started again

Unity versions

CLI first, MCP optional

Current release

FAQ

Does Hera make the AI smarter?

Does it need Python?

Do I need MCP?

Can it control more than one open Unity Editor?

Can it physically click the Unity window?

What should I do if it cannot connect?

Where are the detailed docs?

Projects using Hera

Author

Support

License

Shared `AGENTS.md`