Bezi understands the contents of a project, the objects in a scene, and the properties on the assets, so it’s well-equipped to parse through it all and deliver the exact information you need. Ask Bezi to navigate the depths of your project to find the little details that take endless time to recover. And breathe easy knowing project documentation is covered, without spending time on it.
Currently, Bezi’s context does NOT dive into node graphs, state machines, or visual scripting. Bezi is aware they exist, but cannot see or explain how objects like animators and shader graphs are set up.

​
Example prompts

Onboarding:
  • “Tell me about this project”
  • “Walk me through @PlayerInteraction.cs”
  • “Explain the key features of the PortalsForVR package.”
  • “How does the multiplayer system in this game work?””
  • “What are the controls for this game? List what mechanics there are, and explain how to use each to test.”
Property/Type:
  • “Find all objects set to Static”
  • “Which colliders are set to isTrigger?”
  • “Do I have multiple cameras tagged MainCam?”
  • “List all food prefabs”
Dependencies:
  • “What tile palettes were used to build this level?”
  • “Return all scripts that instantiate Prey prefabs”
  • “Which animation clips does my character movement system actually use?”
  • “What script controls the pickup/drop behavior?”
Optimization:
  • “List all 4K textures”
  • “What models do I actually use across my scenes?”
  • “Which models are too high poly to run on mobile?”