unity-agent-headless
Run Unity without opening the Editor window and prove the result from logs: batchmode -executeMethod passes, Unity Test Framework runs from the command line (-runTests, NUnit XML), an offline C# compile check that works even while the Editor is open (dotnet build on Unity's generated csproj using the .NET SDK bundled inside every Unity install), Editor and build log locations, exit-code traps, the project lockfile, and the deprecated Unity Hub headless CLI as a fallback. Use whenever the user asks to build, test, import, or run something in Unity headlessly, in batch mode, from a script or CI, wants to know if the code compiles without opening Unity, asks where the Editor log is, why a batchmode run returned 0 with errors, why 'dotnet test' says no SDK, or says 'refresh unity-agent-headless' / 'is unity-agent-headless stale'. Driving a running Editor through the official CLI is unity-agent-cli; choosing an MCP server is unity-agent-mcp.
Pinned to revision bc39433bca86, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/unity-agent-headless/SKILL.md
- skills/unity-agent-headless/CHANGELOG.md
- skills/unity-agent-headless/LEARNINGS.md
- skills/unity-agent-headless/MAINTENANCE.md
- skills/unity-agent-headless/RESEARCH.md
- skills/unity-agent-headless/TESTS.md
- skills/unity-agent-headless/evals/evals.json
- skills/unity-agent-headless/evergreen.json
- skills/unity-agent-headless/scripts/unity_headless.ps1
Every link opens the file at its source, pinned to the revision this page describes.