Unity Code Agent v0.2 Release Notes

Unity Code Agent 0.2 release changes

TL;DR

• Vision-capable models can inspect Game View screenshots captured during an agent task.
• Separate Send and Stop controls make long responses easier to manage, while a persistent status area shows current progress without adding noise to the transcript.
• Sessions are scoped to the current Unity project and recover more reliably across domain reloads, navigation, aborts, and service reconnections.
• C# execution waits for a stable Editor state, with clearer assembly configuration and improved bundled skills for implementation and gameplay verification.

Unity Code Agent 0.2 makes multi-step work easier to follow and more dependable. The release focuses on the points that matter when an agent is actively changing a project: seeing visual output, keeping the correct session active, recovering from Unity lifecycle events, and avoiding tool calls while the Editor is compiling.

Learn more about the complete product on the Unity Code Agent page.

What changes for you

The agent can inspect captured Game View images

The Game View screenshot tool now saves captures as managed artifacts and attaches the image to the active agent turn. With a vision-capable model, the agent receives the pixels rather than image metadata alone.

This supports practical visual checks during a task: whether a UI element appears, a scene renders, a camera is pointed at the expected content, or a visible state changed after input. Screenshots are kept under .unityCodeAgent/screenshots/ and cleaned up by age, count, and total size.

Malformed or unavailable image results now return an explicit tool error, so the agent does not continue as if it had inspected an image that was never delivered.

Clearer control over active work

Send and Stop are separate controls in the chat window. Send submits a prompt; Stop cancels the active response and cannot accidentally submit another message.

Progress also has a fixed location outside the transcript. You can see when the agent is working or receiving events without filling session history with temporary status messages.

Sessions stay with the correct project

The sessions list now filters by the current Unity project identity. Sessions created for other projects no longer appear as candidates, reducing the risk of reopening unrelated context.

Busy-session state is also more stable across Unity domain reloads, session switches, list navigation, response cancellation, and event-stream recovery. Settings refreshes and navigation no longer reopen or discard an active session unexpectedly.

Safer Unity execution

C# calls are blocked during compilation

Generated Editor scripts now return a clear blocked result while Unity is compiling. This prevents execution against an unstable set of project assemblies and gives the agent a concrete reason to wait, inspect compiler errors, or retry.

UnityCodeAgent.Editor is included in the default execution assemblies. When a task needs another assembly, the settings workflow validates it before adding it to the script context.

More precise bundled skills

The included Unity Code Agent and game-playing skills now provide clearer tool contracts, assembly-recovery instructions, and verification workflows. They guide the agent to distinguish source editing from Editor scripting, check compilation state, use focused tests, and re-inspect runtime state after simulated input.

This guidance is installed with the package and can target GitHub, Claude, Agents, or a custom skills directory.

Reliability and developer improvements

• The Agent Service can run without Unity in a guarded nounity mode for external automation and evaluation.
• A reproducible DeepEval harness supports scenario filtering, reusable service lifecycle management, tool-sequence policies, and bounded tool calls.
• Routine service and tool operations use quieter Debug-level logging.
• Product documentation now covers built-in tools, skills installation, custom synchronous and asynchronous tools, and MCP server configuration.

These changes primarily support contributors and teams extending Unity Code Agent, while the same evaluation and lifecycle work improves confidence in normal Editor sessions.

Upgrade notes

Most users can upgrade directly to 0.2.10.

• If you configured a custom telemetry path, verify the new Telemetry File Path setting after upgrading. It replaces the previous CliTelemetryFilePath serialized name.
• Sessions without the current project-qualified Unity Code Agent ID are intentionally hidden. Existing project-qualified sessions remain available.

Install or update through Unity Package Manager with:

https://github.com/Signal-Loop/UnityCodeAgent.git?path=Packages/com.signal-loop.unitycodeagent

Review the source and packaged release notes in Unity Code Agent v0.2.10 on GitHub.