PUBLIC BETA Unity Editor package 0.18.0

Give an agent a durable way into Unity.

Alepou Unity Bridge exports compact Editor state into your project, applies explicit typed commands through Unity APIs, and keeps compile, test, build, and Play Mode workflows alive across domain reloads.

Install v0.18.0 View the package source

Free and open source. Manual writes are the default. The AI cannot create, widen, switch, or revoke its own grant.

A bridge-captured Unity scene view of a researched 1990s office desk, including a CRT monitor, tower, keyboard, mouse, telephone, lamp, and desk accessories.
REAL SCENE CAPTURE VR 1998 Office · Unity 6000.3 · Bridge 0.18.0
PACKAGE0.18.0
CLEAN UPM PROOF84 scripts · 0 errors
PROJECT STATEplan/unity/
LICENSEApache 2.0

Install the exact public release

One pinned Git URL. No copied package folder.

The package-root repository is public and the immutable tag has been resolved and compiled in a clean Unity 6000.3 project. Pin the version rather than following main.

UNITY PACKAGE MANAGER https://github.com/alepou-ai/alepou-unity-bridge.git#v0.18.0
  1. Open Window > Package Manager.
  2. Open the + menu and choose Install package from git URL.
  3. Paste the pinned URL above and let Unity resolve and compile it.
  4. Open Tools > Alepou > Unity Bridge > Open Bridge Window.
  5. Confirm the output path is your project's plan/unity/ folder.
  6. Verify a fresh bridge-health.json reports version 0.18.0 and processorActive: true.

Already using an old local checkout? Replace the file:<Alepou checkout>/unity-bridge/com.alepou.unity-bridge dependency with the pinned Git URL. Your existing project-local plan/unity/ evidence stays in place. Contributors can clone the bridge repository separately and use Add package from disk.

One working project · three evidence layers

The page is showing what the bridge actually captured.

This is not stock Unity imagery. These are bounded captures and structured results from the same mixed-reality office project whose researched Blender assets appear on the Blender Bridge page.

A complete Unity UI Builder window captured by the bridge, showing an Examine interaction panel, project style sheet, hierarchy, library, and inspector.
UI Builder, deliberately framed and capturedThe bridge opened the exact UXML document, waited for an Editor update, fitted the document, captured the complete window, then closed it without inventing arbitrary menu automation.
A bounded Unity Game view runtime capture of the 1990s office with a floating investigator narration panel.
Runtime, not just edit-time stateA workflow entered Play Mode, captured the Game view, retained the console delta, probed five named objects, and returned to Edit Mode through explicit transition barriers.

RECORDED BRIDGE EVIDENCE

Tests, build, image, and object state agree.

47focused tests passed27 EditMode + 20 PlayMode
172.4 MiBAndroid APKexact SHA-256 artifact manifest
0build errors3 warnings retained
5object probes26 bounded console entries

The runtime record also retained desktop XR errors when a headset runtime was unavailable. That is the point: evidence is not rewritten into a green badge.

The command pump stays awake

The window is a control surface. It is not the engine.

The processor runs whenever the Unity Editor and project are open. Closing the Alepou Bridge window does not stop command processing, workflow progress, health reporting, or terminal result delivery.

  • A two-second heartbeat distinguishes live Unity from stale files.
  • An independent watchdog distinguishes a stopped Editor from a blocked main loop.
  • Commands are atomically claimed so a domain reload cannot replay them.
  • Alepou wakes an idle owning session only for an exact requested terminal result.
UNITY EDITORlive project state
01

bridge-health.json

processor · waits · grant
02

scene-hierarchy.json

objects · components · prefabs
03

inspector-snapshot.json

typed fields · object references
04

compile-status.json

import · reload · errors
05

workflow-status.json

step · phase · barrier
06

command-results.md

applied · failed · rejected
YOUR PROJECT / PLAN / UNITYcompact, local, inspectable evidence

Observe, author, verify

One request can survive the real Unity loop.

Asset import, script compilation, focused tests, builds, Play Mode transitions, and runtime evidence become ordered barriers with bounded timeouts - not optimistic chat claims.

OBSERVE

See the Editor

Capture Scene, Game, or UI Builder views; inspect hierarchy, selection, serialized fields, assets, packages, Console, build settings, diagnostics, and processor health.

AUTHOR

Typed Unity changes

Create and edit GameObjects, components, prefabs, materials, animation clips, lights, ScriptableObjects, references, and bounded project settings through explicit schemas.

VERIFY

Structured test runs

Filter EditMode or PlayMode tests by assembly, namespace, category, fixture, or exact test. Results include counts, failure summaries, NUnit XML, and per-test JSONL.

BUILD

Artifact manifests

Validated BuildPipeline jobs write collision-free outputs with target, scenes, duration, warnings, errors, byte size, and SHA-256 evidence.

RUN

Bounded Play Mode

A durable Trusted Development workflow can enter Play Mode, capture one bounded runtime state with named probes, and return to Edit Mode without guessing transitions.

UI TOOLKIT

Document-level capture

Open one imported UXML document, frame it, capture the complete UI Builder window, and close it - while refusing unsaved document switches and blank captures.

1WRITE CODE
2REFRESH
3COMPILE CLEAN
4FOCUSED TESTS
5BUILD + EVIDENCE

Delegated authority

You choose how far one session can go.

The authoritative grant lives in Unity's Editor preferences, bound to the canonical project identity - never in the model-writable command folder. A matching command records the grant, session, exact action set, and frozen request hash.

DEFAULT

Manual writes

Bounded observation runs automatically. Every mutation waits for a human decision.

Best for first contact
BOUNDED

Reversible Workspace

Time-limited routine scene and asset work, deliberately excluding compilation.

Best for visual assembly
SESSION-BOUND

Trusted Development

Routine editing, refresh, compilation, focused tests, persisted assets, and workflow-owned Play Mode for one live Alepou session.

Durable until revoked or rebound
EXACT

Custom Expert Grant

Name precise actions, expiry, session, and command/action budgets for specialist operations such as builds.

No wildcard authority

Important: delegation is an operational safety and audit boundary, not an operating-system sandbox. Compiled Unity Editor code already runs with your user privileges. Use trusted projects, CLI/provider sandboxing, and version control as separate defences.

Mushroom March running as a mixed-reality diorama on a Meta Quest 3, surrounded by the real room seen through passthrough.
Mushroom March · on-device Quest 3 proof

Optional Meta Quest adapter

A verified APK does not silently become device authority.

Alepou can hand a successful Android artifact manifest to Meta's separately installed metavr toolchain for bounded device discovery, install, launch, logs, screenshots, and performance traces.

The device grant is separate from Unity's Editor grant. It can name one device, one application ID, exact actions, an expiry, a job budget, and the frozen APK hash.

See the Canvas-to-Quest project

Alepou Unity Bridge 0.18.0

Make the Editor observable. Keep the work reviewable.

Install the pinned package, run the smoke test, and decide exactly what one session may do.

Open the Unity Bridge repository Read the v0.18.0 release