Repository navigation
docs: drive Unity through the unity CLI instead of unity-mcp - #28
Merged
Merged
Conversation
Agent instructions, CONTRIBUTING and the two forward-looking plans now point at `unity command` / `unity mcp` (Pipeline package) for driving a live Editor, and `unity open` / `run` / `test` for headless work. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PaulAsjes
approved these changes
Oct 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Unity's
unityCLI now covers what we used the separate unity-mcp server for (live-Editor control via thecom.unity.pipelinepackage, plus a built-inunity mcpserver), and also handles headless open/run/test with automatic editor resolution.Merging this PR will:
.claude/CLAUDE.mdto drive Unity viaunity open/run/testandunity command/unity mcp, with the caveats we hit.unity testas an alternative Edit Mode runner inCONTRIBUTING.md.agent-component.mdandunity-coding-agent-skills.mdplans to the CLI, adding a design consequence: exposeElevenLabsAgentSetupas[CliCommand]s.Additional context intended for coding agents and bots
Scope
TestProject/run-tests.tsandTestProject/build-*.shstill invoke the Unity binary directly; switching them tounity test/unity buildis a possible follow-up (the runner's VS Code problem-matcher summary would need to be kept on top ofunity test's NUnit output).audio-generator-engine.md,audio-output-filter-engine.md,output-audio-source.md,v0.1-parity.md) and a comment inUnityGeneratorAudioOutputEngineCharacterizationTest.csstill mention unity-mcp on purpose: they record what was actually used at the time.com.unity.pipelineis not added toTestProjector the Getting Started project; the docs tell the agent tounity pipeline installit where needed.Observed CLI behaviour (unity 1.0.0-beta.8, com.unity.pipeline 0.8.0-exp.1, Unity 6000.3.6f1)
-quitserves Pipeline commands but is not listed byunity status;unity list --project-pathworks as a probe.unity command quitfails in batch mode (DontDestroyOnLoadcalled fromPipelineQuitScheduleroutside Play mode);unity close <project> --forcestops it.unity testrefuses to run while another editor holds the project open (exit 6).Test plan and verification
unity doctor: CLI on PATH, signed in, editor 6000.3.6f1 detected.unity test TestProject --mode EditMode -- -nographics: 460/460 passed.com.unity.pipelinetemporarily added toTestProject(reverted, not in this PR): resident batch editor answeredunity commandlisting,eval(resolvedElevenLabs.Agents.Core),log,console;unity mcpinitialize +tools/listreturned 160 tools.https://docs.unity.com/en-us/unity-cliresolves to the Unity CLI docs.🤖 Generated with Claude Code