Hera live Godot workflow
Use Hera only with a running Godot editor that has the Hera Agent Godot addon
enabled (verified on Godot 4.2–4.7; 4.7 recommended). CLI output is the source
of truth for live editor and runtime state.
Start with the live editor
- Run
hera status. If no live editor is found, ask the user to enable the
addon under Project Settings → Plugins; do not infer editor state from
files.
- If multiple editors are found, run
hera instances. Pass
hera --instance <pid> for any mutation.
- Before UI work, run
hera guidance ui and follow its returned mode.
Keep reads small and writes safe
- Default output is compact. Prefer
hera --ids scene tree, selected
node get --prop/--props, scoped game ui tree, and game qa discover
before full dumps.
- Use
node add/set/remove and signal connect/disconnect for normal editor
changes; Godot records those as undoable steps. Prefer them to eval, whose
expression can have side effects and is not undoable.
- Scene, resource, script, import, and project-setting commands persist to
disk.
game node set/call, game click, and game input affect only the
running game and disappear when it stops.
- Keep one editor per project. After direct
.tscn edits, stop the game,
hera scene reload, then save through the editor.
Prove the result
- After a change, read the changed property or node tree. After a run, check
hera output --type error or hera diagnostics.
- For visual/UI work, use
game ui tree, semantic game click, and
hera screenshot --runtime --analyze. For prompt requirements, prefer a
game qa --file scenario with requirements and per-step covers.
- After editing GDScript, run that project's headless
--check-only gate when
available, then re-check diagnostics.
Hera sends any configured HERA_AGENT_GODOT_TOKEN automatically. Never print
or place that token in project files. For the complete command reference, see
the Hera repository's docs/COMMANDS.md.
Source: hashgraph-online/awesome-codex-plugins → plugins/NotNull92/hera-agent-godot/skills/live-editor/SKILL.md
1---
2name: live-editor
3description: "Use this skill whenever a request involves a Godot project's live editor or running game: inspect scene, node, or UI state; change scenes, nodes, properties, or signals; run a scene; or prove gameplay or UI behavior. Prefer the `hera` CLI over guessing from project files or stale editor state."
4category: ai-agents-and-harness
5source_repo: hashgraph-online/awesome-codex-plugins
6source_path: "plugins/NotNull92/hera-agent-godot/skills/live-editor/SKILL.md"
7source_url: https://github.com/hashgraph-online/awesome-codex-plugins/blob/HEAD/plugins/NotNull92/hera-agent-godot/skills/live-editor/SKILL.md
8metadata:
9 source: https://skillmd.com/skills/hashgraph-online/live-editor
10---
11
12
13# Hera live Godot workflow
14
15Use Hera only with a running Godot editor that has the Hera Agent Godot addon
16enabled (verified on Godot 4.2–4.7; 4.7 recommended). CLI output is the source
17of truth for live editor and runtime state.
18
19## Start with the live editor
20
211. Run `hera status`. If no live editor is found, ask the user to enable the
22 addon under **Project Settings → Plugins**; do not infer editor state from
23 files.
242. If multiple editors are found, run `hera instances`. Pass
25 `hera --instance <pid>` for any mutation.
263. Before UI work, run `hera guidance ui` and follow its returned mode.
27
28## Keep reads small and writes safe
29
30- Default output is compact. Prefer `hera --ids scene tree`, selected
31 `node get --prop/--props`, scoped `game ui tree`, and `game qa discover`
32 before full dumps.
33- Use `node add/set/remove` and `signal connect/disconnect` for normal editor
34 changes; Godot records those as undoable steps. Prefer them to `eval`, whose
35 expression can have side effects and is not undoable.
36- Scene, resource, script, import, and project-setting commands persist to
37 disk. `game node set/call`, `game click`, and `game input` affect only the
38 running game and disappear when it stops.
39- Keep one editor per project. After direct `.tscn` edits, stop the game,
40 `hera scene reload`, then save through the editor.
41
42## Prove the result
43
44- After a change, read the changed property or node tree. After a run, check
45 `hera output --type error` or `hera diagnostics`.
46- For visual/UI work, use `game ui tree`, semantic `game click`, and
47 `hera screenshot --runtime --analyze`. For prompt requirements, prefer a
48 `game qa --file` scenario with `requirements` and per-step `covers`.
49- After editing GDScript, run that project's headless `--check-only` gate when
50 available, then re-check diagnostics.
51
52Hera sends any configured `HERA_AGENT_GODOT_TOKEN` automatically. Never print
53or place that token in project files. For the complete command reference, see
54the Hera repository's `docs/COMMANDS.md`.
55
56---
57
58**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/NotNull92/hera-agent-godot/skills/live-editor/SKILL.md`