The ’60+ Structured Commands Across 8 Categories’

GameCatalyst provides over 60 commands in eight categories. This structure keeps things organized for both you and Vex.

The eight categories:

1. Management (15 commands): Project discovery, selection, session control, status, help, knowledge base. Always available. Examples: list_all_projects, select_project, what_is.
2. Query: Scene inspection, object search, asset listing, hierarchy traversal, file discovery. Read-only — looks without changing. Examples: scene.objects, object.find, workspace.find.
3. Create: GameObjects, primitives, prefabs, scripts, materials with shader support (color, metallic, smoothness, auto-assign). Examples: object.create, asset.create.
4. Modify: Transforms, components with initial properties, dot-path traversal for nested values, renaming, active state. Examples: transform.set, component.set.
5. Delete: Safe object removal, component cleanup with dry-run protection. Examples: object.delete, component.remove.
6. Control: Play mode, console, scenes, recompile freeze, batch operations. Examples: play_mode, scene.save, unity.batch_operation.
7. FileSystem (17 commands): File and folder read, create, edit, delete, copy, duplicate, move, rename — all with dry-run defaults. Examples: file.create, folder.read.
8. Workspace Intelligence: Planning, code indexing, path validation, file discovery. Examples: workspace.plan, workspace.index, workspace.diagnose, workspace.find.

Availability: Management commands work immediately. Engine commands require selecting a project first. You control which commands are enabled through Dashboard Settings Tool Permissions.

How categories help you:

Categories organize commands by purpose. If you want to create something, the Create category has the tools. If you want to find something, look in Query. If you want to control Unity’s editor, check Control. This makes the system easier to learn and remember — you do not need to know all 60+ commands. You just need to know the categories, and Vex handles the rest.

Command availability:

Not all commands are available at all times. Management commands work immediately when your AI connects. Engine commands (Query, Create, Modify, Delete, Control, FileSystem, Workspace Intelligence) only become available after you explicitly select a Unity project. This prevents accidental operations on the wrong project.

Customizing availability:

You control which commands are enabled through Dashboard Settings Tool Permissions. Want to prevent the AI from deleting objects? Disable the Delete category. Want read-only access? Enable only Management and Query categories. Permissions propagate to connected AI clients within 5 seconds — no restart required. You can also use the workspace.plan command on a per-project basis, enabling it for complex projects and disabling it for quick prototypes.