| name | hera-agent-unity |
| description | Control the running Unity Editor via the hera-agent-unity CLI — execute C#, read the console, drive Play Mode, run tests, inspect live types |
hera-agent-unity skill
Drive a running Unity Editor from the terminal over localhost HTTP. Use this instead of guessing Unity APIs from training data — measure against the real Editor.
When to use
- Manipulating the Editor: scenes, GameObjects, components, prefabs, materials, UI (
scene, manage_gameobject, manage_components, manage_prefab, manage_material, manage_ui).
- Building UI from an HTML design:
ui_doc export (live UI → compact JSON to ground on), ui_doc apply --file <doc.json> (JSON → UI; --mode create default or upsert to edit existing in place), ui_doc gen_sprite (procedural sprite — no external dep), ui_doc capture (render the live UI → PNG to verify against a reference). Design in HTML, export to ground, apply the ui_doc/2 IR.
- QAing Unity UI input without Computer Use coordinates:
input state, input inspect --path ..., then input click / submit / scroll / drag. This sends uGUI EventSystem events inside Unity; it is not a physical OS click.
- Reading the real console: errors, warnings, stack traces (
console).
- Running EditMode / PlayMode tests (
test).
- Driving Play Mode (
editor play / stop).
- Executing arbitrary C# inside the Editor when no dedicated command fits (
exec).
- Inspecting live types / methods (
describe_type, find_method, list --compact).
Pre-flight
Before any real work, confirm the Editor is reachable:
hera-agent-unity status
hera-agent-unity doctor --json
hera-agent-unity list --compact
If status returns no instances, tell the user to open Unity with the UPM connector package and stop — don't retry blindly.
Ultra Hera
Ultra Hera is the verification mode for AI-assisted Unity work. Hera does not do the AI work by itself; it tells the agent how carefully to check Unity after using Hera.
Modes are saved in asset-config.json as loopEngineeringMode:
off: no extra checking rule.light (default): use the Light loop for every Unity coding, Editor, and Inspector task.ultra: use the Light loop for every task, then upgrade strict or important work to the Ultra loop.
Light loop: confirm the goal, observe only needed state, change code/scene/Inspector, verify compile or state, check console errors, re-read only the changed target, retry 1-2 times if needed, and report short final evidence.
Ultra loop: split the goal into success criteria, take a before-change snapshot, apply the change, compile, confirm console errors are 0, re-read Inspector/GameObject/asset state, run PlayMode or Unity tests, capture screenshot or ui_doc output if needed, classify failures, and report evidence plus remaining risk.
Use Ultra when the user asks for strict verification, for example 정확히 검증해줘, 플레이해서 확인해줘, UI 맞춰줘, or 인스펙터까지 확실히 봐줘.
Command rules
- Keep CLI and UPM versions separate.
hera-agent-unity version is the Go CLI release tag (vX.Y.Z); Unity Package Manager shows the connector package version from AgentConnector/package.json (0.0.N). Do not call the UPM package vX.Y.Z, do not assume the numbers match, and do not treat a git lock hash as the package version.
- Call sequentially, never in parallel. The connector serializes every command on the Unity main thread; concurrent calls just queue.
- Pass
--compact-json on every tool call — AntiGravity consumes the JSON, so keep it small.
- Use compact discovery. Prefer
list --compact; use list --tool <name> only when one full schema is required.
- Separate input evidence.
input can prove Unity EventSystem UI behavior in Play Mode, but physical OS click QA is still BLOCKED when Computer Use cannot capture Unity screenshot state.
- Use IDs for object handoff. Prefer
find_gameobjects --ids; add --fields instance_id,name,path only when duplicate names need context.
exec: default to return null; (or omit the return). A verbose status string is wasted tokens; the OK response is 3 bytes.exec: never return a UnityEngine.Object (Transform, GameObject, Material, …). They expand to thousands of bytes. Return new { name = go.name, instanceID = go.GetInstanceID() }.- Branch on the
code field, not the message: EXEC_COMPILE_ERROR, EXEC_RUNTIME_ERROR, UNKNOWN_COMMAND (has data.did_you_mean), EXEC_CSC_NOT_FOUND, etc.
- Domain reloads (recompiles/imports) drop the HTTP connection — the CLI auto-retries ~5s. For big projects raise
--timeout 120000. Use editor refresh --compile to force compile before continuing.
- Prefer dedicated commands over
exec — scene info, console, describe_type skip csc compile (5–15s cold).
PowerShell / multi-line C#
PowerShell quoting mangles C#. Always pipe a here-string to stdin:
@'
var mats = AssetDatabase.FindAssets("t:Material").Length;
return mats;
'@ | hera-agent-unity exec --compact-json
bash equivalent: a <<'EOF' heredoc, or --file scripts/probe.cs for anything long or reusable.
Examples
hera-agent-unity scene info --compact-json
hera-agent-unity exec "return EditorSceneManager.GetActiveScene().name;" --compact-json
hera-agent-unity console --type error --lines 5 --compact-json
echo 'var root = new GameObject("MyRoot");
for (int i = 0; i < 10; i++) new GameObject("Item_" + i).transform.SetParent(root.transform, false);
return null;' | hera-agent-unity exec --compact-json
hera-agent-unity test --mode PlayMode --filter MyGame.Tests --compact-json
hera-agent-unity describe_type UnityEditor.AssetDatabase --members methods --limit 30 --compact-json
hera-agent-unity find_gameobjects --ids --compact-json
hera-agent-unity editor play --wait && hera-agent-unity console --type error --compact-json
When this skill is wrong
If anything here contradicts hera-agent-unity <cmd> --help, trust --help. The full guide (Tool Selection, Cookbook, Pitfalls, Reference) is at https://github.com/NotNull92/hera-agent-unity/blob/main/AGENTS.md.
