Agents
Two agents work on an Unreal project. The Unreal coder writes the change. Unreal QA checks it independently. Neither changes a task’s status directly: the board moves the card from what they report.
Unreal coder
The Unreal coder implements a task in C++.
- It writes source files on disk, inside the project’s modules and plugins. It does not create or edit Blueprint assets.
- It builds with the engine’s build tool. When the editor is open and only function bodies changed, it can use Live Coding instead.
- It runs the automation tests that cover the change.
- It checks the running editor through the editor connection, when the editor answers.
- It commits the change to git and hands the task to QA.
The coder never edits Binaries/, Intermediate/, Saved/, DerivedDataCache/ or the engine install. When it needs you, for example to close the editor for a change to reflected types, it leaves a comment on the task.
Unreal QA
Unreal QA picks up a task when it reaches Review. It applies to a project that has a .uproject file at its root.
- It reads the task, the coder’s comments and the change.
- It builds the work itself, clean, so the build proves the binaries come from this change.
- It runs the covering automation tests itself.
- It starts its own Unreal Editor on the working copy and checks the change there.
- It never edits source, never commits, and never saves a level or an asset.
QA does not trust the coder’s report. It judges from what it observes in its own run.
The verdict
| Verdict | Requires | Result on the board |
|---|---|---|
| Pass | A build that ran, compiled the project’s own code and succeeded. Passing tests, when any cover the change. At least one passing editor check. | The task moves to Done. |
| Fail | A failed build, a failed test or a failed editor check. | The task returns to the coder with QA’s findings. |
| Retry | An environment problem: the editor or its connection could not be reached, or nothing was built. | QA runs again. The task stays in Review. |
A check QA could not finish is reported as not checked. It does not send the task back.
QA’s editor checks need the editor connection. If another Unreal Editor holds the Remote Control port, QA reports an environment problem and asks for that editor to be closed. See Editor connection.
Where runs appear
| Place | What it lists |
|---|---|
| Unreal view, Unreal agent runs | The latest Unreal coder and Unreal QA runs, newest first, each marked Running, Succeeded, Failed or Cancelled. |
| Awaken (NPCs & QA) view, QA tab | The QA runs. When there are none it reads “No QA runs yet. QA runs start when a task reaches Review.” |
| Agents view | Every agent, and the detail of a run. |
| Tasks view | The card the run belongs to. |
Each run row has two links. Open run opens the run’s detail in the Agents view. Open task opens its card on the board.
For the Awaken view, see the Awaken docs and QA runs.