# Unity Pipeline

Control a Unity Editor or Player via the unity-pipeline package.

- Repository: https://github.com/Unity-Technologies/skills (1197 stars)
- Category: Testing
- License: see repository
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Unity-Technologies/skills --skill unity-pipeline -g -a claude-code -y`
Codex: `npx skills add Unity-Technologies/skills --skill unity-pipeline -g -a codex -y`
Cursor: `npx skills add Unity-Technologies/skills --skill unity-pipeline -g -a cursor -y`
Gemini CLI: `npx skills add Unity-Technologies/skills --skill unity-pipeline -g -a gemini-cli -y`

## Description

Control a Unity Editor or Player via the unity-pipeline package. Compile, run tests, eval, method-reload code, enter Play Mode, capture screenshots.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Unity Pipeline (agent control)

Invoke commands with `unity command <group> <name> [args]`. Run `unity command` with no
argument to list the command groups an instance exposes, and `unity command <group>` to list
the commands in one group. Two servers exist: **Editor** (`7800-7849`, auto-starts with
the editor) and **Runtime** (`7900-7949`, only in a dev Player build). `unity command --query <term>`
filters the listing by name, description or tag.

## Before you start

- Create a restore point you can roll back to if your changes fail, such as a commit or a stash of
  the project's working tree.
- Read the project's Editor version from `ProjectSettings/ProjectVersion.txt` (`m_EditorVersion`),
  because some commands and parameters below differ by Unity version. Use it to pick the matching
  steps wherever this skill names a version.
- Do only what's asked. Don't change unrelated assets or files. Avoid long explanations.
- Before you go forward with a workflow or diagnosis, open and read the [Topic map](#topic-map)
  page(s) that cover the commands you intend to run. Name the file(s) you read in your response. This
  is because your training knowledge about Unity might be out of date, incorrect, or for the wrong
  Unity version, and Pipeline command names and parameters change between package versions.
- When a change affects runtime behaviour, add `Debug.Log` lines that you will read back in Play Mode
  to verify the behaviour (see [Final checks](#final-checks)).

## 1. Install & verify

```bash
unity pipeline install            # install into current project (or --project-path)
unity pipeline list               # confirm the editor instance + server are reachable
unity status --until-ready        # wait until the editor server is ready
unity command editor status       # confirm the editor server answers
```

The rest: https://github.com/Unity-Technologies/skills/blob/HEAD/skills/unity-pipeline/SKILL.md