unity
Control the Unity Editor via Claude Code to run tests, compile scripts, manage play mode, and retrieve console logs using a file-based bridge.
Introduction
The Unity Bridge skill provides a reliable, file-based communication protocol for Claude Code to interact directly with a running Unity Editor instance. By installing the com.mxr.claude-bridge Unity package, developers can automate editor-side workflows without the complexity of networking, port configurations, or socket management. This skill enables seamless integration between AI-driven development workflows and the Unity Editor, making it an essential tool for game developers and XR engineers aiming to streamline their testing and build cycles.
The skill functions through a deterministic CLI (unity-bridge) that handles UUID command tracking, atomic file operations, and exponential backoff polling. It is designed to work effectively across macOS, Windows, and Linux environments. Because each project maintains its own .unity-bridge/ directory, it supports simultaneous development across multiple Unity projects without interference. It is ideally suited for teams practicing TDD (Test-Driven Development) in Unity or those needing to automate repetitive editor tasks like asset refreshing or console monitoring during debugging sessions.
-
Execute both EditMode and PlayMode tests with filter support to target specific namespaces or test classes.
-
Trigger script compilation and retrieve detailed error reporting directly from the Unity compiler output.
-
Manage Unity Play Mode state, including triggering play, pause, and single-frame step operations.
-
Access and filter Unity console logs to quickly diagnose runtime exceptions or warnings.
-
Refresh the Unity asset database programmatically to ensure changes made by external scripts or generators are indexed.
-
Check real-time editor status, such as whether the engine is busy compiling, currently in Play Mode, or in the middle of a background update.
-
Requires the com.mxr.claude-bridge package to be installed in the Unity project via Package Manager.
-
The Unity Editor must remain open and active for the bridge to process incoming commands.
-
Uses a Python-based CLI that expects Python 3.8+ to be available in the local shell environment.
-
Designed for Unity 2021.3+ versions and supports automated cleanup of command and response files to prevent filesystem clutter.
-
Supports verbose output and custom timeout configurations, useful for large test suites or slower build environments.
Repository Stats
- Stars
- 20
- Forks
- 1
- Open Issues
- 0
- Language
- Python
- Default Branch
- main
- Sync Status
- Idle
- Last Synced
- May 3, 2026, 11:49 PM