unity-control-protocol

You can automate Unity Editor tasks programmatically using a CLI and bridge package that communicates via WebSocket and JSON-RPC 2.0. This allows you to control scenes, GameObjects, and assets without direct UI interaction.

Yes, you can automate Unity build pipelines and run tests remotely in CI/CD environments. The protocol supports triggering builds and executing test suites through command-line interfaces and WebSocket connections.

Programmatic Unity scene manipulation works by sending JSON-RPC 2.0 commands over a WebSocket connection to a bridge package inside the editor. This enables automated inspection, creation, and modification of GameObjects and components.

The best way to capture Unity scene screenshots for documentation is by automating the process through CLI commands. This allows you to programmatically load scenes and capture viewport screenshots without manual UI interaction.

Yes, Unity automation supports modifying materials and prefabs remotely. The protocol manages assets, components, and prefabs via JSON-RPC 2.0 commands, enabling programmatic creation and inspection of project elements.

The protocol relies on a WebSocket and JSON-RPC 2.0 bridge package inside the Unity Editor, meaning the editor must be running to receive commands. It does not support direct UI interaction but handles scenes, assets, and builds programmatically.