Installation

Install Grabbit

1. Import from the Unity Asset Store. Open the Grabbit 2 page, click Add to My Assets, then open the Package Manager in Unity (Window > Package Manager), find Grabbit 2 under My Assets, and import it.

1. Let the Jungle framework install. The first time it imports, Grabbit asks to add the shared Jungle framework packages it is built on. Click Install: it adds the Jungle package registry to your project and pulls the packages in through Unity's Package Manager (details below). Wait for Unity to finish compiling and reloading scripts.

2. Open the welcome window. The Grabbit startup window appears the first time it loads, walking you through collider and collision precision choices, plus optional MCP support: install it and AI assistants connected to Unity, like Unity's AI Assistant, can bake colliders and place, arrange or scatter objects for you. You can revisit it any time from Tools > Jungle > Grabbit > Open Startup Menu.

1. You're ready. Activate the tool from the Scene View toolbar (see Quick Start).

What You Can Leave Out

Unity's import window lets you untick folders. Two of Grabbit's are safe to leave out, as long as you leave out the whole folder:

Folder	What you lose
Demo	The sample models and materials. Nothing else uses them.
Editor/Mcp	The bridges that let AI assistants drive Grabbit. Everything you do by hand still works.

Leave every other folder checked. Grabbit checks itself on load and tells you in the Console if something is missing or left over from an older version.

Unticking a folder on an update leaves the old files behind

Unity skips unchecked folders rather than deleting them, so updating with a folder unticked mixes the old version's files in with the new ones. The errors that follow point nowhere near the import. When you update, re-import with every folder checked, including the two above if you took them the first time.

The Jungle Packages

Grabbit is part of Jungle, the shared framework all Jungle plugins build on, so it doesn't reinvent common pieces like the weighted asset collections that power Create. That is why, on first import, Grabbit adds a scoped package registry to your project and installs a small set of packages through Unity's Package Manager:

Package	What it's for
jungle.core	The shared foundation Grabbit's editor tooling runs on
jungle.asset-collection	The weighted asset-collection model that Create spawns from

These appear under Packages in the Package Manager, not under Assets, which is why you'll see a registry and packages you didn't add by hand. They are editor-time only: nothing from them is compiled into your player build. If the install is ever skipped or interrupted, you can re-run it any time from Tools > Grabbit > Install Jungle Framework.

Verifying It Works

1. Open or create a scene with a floor (a stretched cube or plane) and a few objects.
2. In the Scene View toolbar, pick the Grabbit 2 tool.
3. The Grabbit overlay should appear in the Scene View with its row of mode buttons.

If the overlay does not appear, make sure the Scene View has focus and that the Grabbit tool is selected in the toolbar's tool list.

Troubleshooting

The Grabbit tool isn't in the toolbar : Grabbit registers as a Scene View EditorTool. Open the tool dropdown in the Scene View toolbar and look for Grabbit 2. If it's missing, confirm the package finished importing without compile errors (Window > General > Console).

The Jungle framework didn't install : If you skipped the install prompt or it failed (no connection, registry unreachable), run Tools > Grabbit > Install Jungle Framework to add the registry and packages again.

Scripts won't compile after a Unity upgrade : Delete the Library/ folder and reopen the project to force a clean reimport.

Collider baking seems stuck : Baking runs in the background and can take a moment on large meshes. The overlay shows ⚙ Baking colliders: N remaining... while it works. See Colliders & Baking for how to control it.