Tools & CLI Reference
Every AI Forge tool ships with a capability manifest and runs in two modes – headless via the CLI or, with the editor open, through request/response files. Here are the individual tools and what they can do.
Project Lens
Gives the agent a structured understanding of the project instead of scanning everything: an AI-readable catalog of
scripts, prefabs, materials, scenes and ScriptableObjects along with their relationships. A build produces
Temp/AI/project-index.json.
| Capability | Purpose | Mode |
|---|---|---|
projectlens.index | Build/update the catalog | both |
projectlens.query | Structured search (“prefabs with a Rigidbody”, “types that implement IX”) | closed |
projectlens.usages | Find references to an asset/type | closed |
projectlens.summary | Summarize a prefab/scene/script | closed |
Read-only – no destructive capabilities, safe to run. The index build runs headless; in the editor it
updates incrementally via an AssetPostprocessor.
Scene Smith
Builds and populates scenes from a declarative SceneSpec. The agent thinks in data, not in editor clicks:
{
"scene": "Assets/Scenes/Arena.unity",
"environment": "skybox-day",
"objects": [
{ "prefab": "Assets/Prefabs/Crate.prefab", "at": [0,0,0], "name": "Crate_A" },
{ "primitive": "Plane", "scale": [10,1,10], "name": "Ground" },
{ "prefab": "Assets/Prefabs/Torch.prefab",
"arrange": { "pattern": "circle", "count": 8, "radius": 5 } }
],
"camera": { "at": [0,6,-10], "look": [0,0,0], "fov": 60 },
"lighting": "three-point"
}| Capability | Purpose | Destructive |
|---|---|---|
scenesmith.build | Build/populate a scene from a SceneSpec | no (new scene) |
scenesmith.place | Place objects/prefabs into the scene | no |
scenesmith.arrange | Grid/circle/scatter/line placement | no |
scenesmith.modify | Move/rotate/scale/rename by name | yes |
scenesmith.camera-light | Apply a camera + light preset | no |
scenesmith.snapshot | Render the camera/scene view to PNG | no |
Unity -batchmode -executeMethod SceneSmith.Editor.BuildCLI.Run \
-spec Assets/Scenes/arena.spec.json \
-out Assets/Scenes/Arena.unitymodify/reparent are destructive and require confirmation; a dry-run only reports the
planned operations. Prefers additive scenes – never overwrite a scene without an explicit target + confirmation.
Scene Verify Pro
Renders a built scene to a PNG so the agent can see its own result and correct itself.
Technically: a Camera with a targetTexture → Render() → ReadPixels → PNG, headless.
This closes the loop build → look → correct – the most important building block for reliable autonomous changes.
Store Advisor Pro
Factors the Asset Store packages you own into planning and implementation – even ones you haven't imported yet. So the agent says “you already own X, which can do that” instead of building it from scratch.
| Capability | Purpose | Mode |
|---|---|---|
storeadvisor.catalog | List owned/downloaded Store assets (local cache) | closed |
storeadvisor.inspect | Inspect the contents of a .unitypackage without importing it | closed |
storeadvisor.suggest | Suggest owned assets that match a given need | closed |
Privacy: purchase data is personal data. Store Advisor reads it only locally (on Windows
%APPDATA%/Unity/Asset Store-5.x/), makes it available only to the agent within the project and transmits nothing.
More Pro extensions
- Scene Smith Pro – lighting/environment presets (day, sunset, overcast, night), a frame-everything camera, save-as-prefab and batch generation from a spec.
- Project Lens Pro – deeper audits: likely unused assets, a size report, prefabs with missing scripts and full dependency trees.
