v0.2.10

Unity Code Agent 0.2.10 Release Changes

TL;DR

• Game View screenshots are now available to vision-capable models as image attachments, enabling pixel-grounded descriptions.
• Chat now has separate Send and Stop controls, plus a persistent progress display that makes active work easier to follow.
• Sessions stay scoped to the current Unity project and retain their busy state more reliably across reloads, navigation, and reconnects.

✨ What's New for You?

The 0.2.10 release makes Game View screenshots genuinely useful in agent conversations: vision-capable models receive the captured pixels as image attachments and can describe what they see. It also makes long-running work easier to control through clearer chat state and safer session handling.

• Screenshots the agent can inspect: Game View captures are saved as managed artifacts and injected into the active Copilot turn, allowing a vision-capable model to describe the captured image instead of only receiving image metadata.
• Clearer response controls: Send and Stop are now separate actions. Stop aborts the active response; it cannot submit another prompt by mistake.
• Progress you can see without losing your place: The chat window keeps progress in a fixed status area rather than mixing it into the transcript. Its always-visible indicator changes while the agent is busy or events arrive.
• Sessions that belong to this project: The sessions list now filters by the project identity in Unity Code Agent session IDs, so sessions from another Unity project no longer appear as candidates.
• More capable bundled guidance: Updated Unity Code Agent and game-playing skills give agents clearer tool contracts, assembly-recovery steps, and verification workflows.

---

⚠️ Breaking Changes & Migration

Most users can upgrade directly. Review these changes if they apply to your project.

• Custom telemetry paths: The serialized setting is now named Telemetry File Path (previously CliTelemetryFilePath). If you set a custom path, verify it in Unity Code Agent settings after upgrading.
• Project-scoped session lists: Sessions without the current project-qualified Unity Code Agent ID are intentionally hidden from the sessions list. Existing sessions with the project-qualified format remain available.

---

🚀 Key Improvements

💬 Chat and session reliability

• Stable busy-state handling: Active response state survives Unity domain reloads, session switches, sessions-list navigation, prompt aborts, and service event-stream recovery more consistently.
• Predictable session changes: Settings refreshes and sessions-list navigation no longer reopen or discard an active busy session unexpectedly.
• Clear unfinished-session signals: Session-list markers and composer controls now stay aligned with the active session state.

🖼️ Unity tools and automation

• Managed screenshot artifacts: Game View screenshots are persisted under .unityCodeAgent/screenshots/, with age, count, and total-size cleanup while retaining PNG tool-result compatibility.
• Safer screenshot delivery: Malformed or unforwardable screenshot results now fail with an explicit tool error instead of silently producing an unusable response.
• Safer C# execution: Script execution reports a clear blocked result while Unity is compiling, avoiding runs against an unstable Editor state.
• Simpler assembly access: UnityCodeAgent.Editor is included in the default C# script execution assemblies, and the settings workflow validates additional assemblies before adding them.

⚙️ Service and developer workflows

• Standalone service mode: The Agent Service can now run with nounity for external automation and evaluation. Its guarded POST /api/service/stop endpoint is available only in that mode; Unity-managed startup is unchanged.
• Reproducible agent evaluation: A new evals/ DeepEval harness adds uv project metadata, reusable service lifecycle support, scenario filtering, tool-sequence policies, and a bounded tool-call guard.
• More useful project documentation: The README now covers built-in tools, bundled skill installation, custom synchronous and asynchronous tools, and MCP server configuration.
• Quieter routine logs: Routine service and tool operations now log at Debug rather than Info level.