Bigdra50 Unity Cli
unity-cli is a Claude Code plugin for the Build phase that lets you control Unity Editor from the command line for play mode, tests, scenes, and logs.
by bigdra50 · github.com/bigdra50/unity-cli
Wire a command-line bridge so your agent or CI can drive Unity Editor—play mode, scenes, GameObjects, console logs, and tests—without clicking through the GUI.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install bigdra50-unity-cli@bigdra50/unity-cliBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:bigdra50/unity-cli") and the paste-ready config with skillselion.get_install_config("plugin:bigdra50/unity-cli").
What it does
bigdra50-unity-cli is a Claude Code plugin that exposes unity-cli—a command-line toolkit for steering the Unity Editor from scripts, terminals, or agent-driven workflows. Solo game builders and small studios use it when GUI-only iteration becomes a bottleneck: triggering Play Mode, reading console output, hopping scenes, manipulating GameObjects, and kicking off tests without manual editor babysitting. The plugin fits the Build journey when you are integrating tooling around your game project, but the same commands support Ship-phase test verification and Operate-phase investigation when reproducing player-reported bugs. Expect a developer-focused CLI rather than a hosted service; you run it where Unity is installed and let Claude Code or your CI invoke the verbs you need. For Skillselion readers shipping Unity titles, it is the glue between your coding agent and the editor state you normally only reach through clicks.
Highlights
- CLI control of Unity Editor: Play Mode, scenes, GameObjects, and console logs
- Run and inspect play-mode and edit-mode tests from the terminal
- Automation-friendly workflow for debug, verification, and build investigation
- Single-plugin bundle aimed at agent-driven or scripted Unity pipelines
- Toolkit keywords cover inspection, verification, and development automation
Why builders use it
Automating Unity Editor steps for agents or CI is painful when every check requires manual Play Mode clicks and console spelunking.
After install, you script editor actions and test runs from the CLI so agents and pipelines can verify game behavior reproducibly.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 35 stars, 0 votes.
FAQ
Who is unity-cli for?
It is for Unity developers and technical solo builders who automate editor tasks from the terminal or through Claude Code plugins.
When should I use unity-cli?
Use it during feature work, automated test runs before ship, or when diagnosing editor console errors during iteration.
How do I add unity-cli to my agent?
Install the bigdra50/unity-cli plugin from Skillselion, set up the unity-cli binary with your local Unity project, and expose the commands to Claude Code or your shell scripts.
Comments
Share how you use bigdra50-unity-cli, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.