Skip to main content
Bezi is a game dev tool with complete context of your Unity project. It indexes a Unity project in-real time, registering all the assets, scenes, packages, codebase and more. It uses LLMs to find and apply task-relevant context, so every response is specific to the work at hand. Because Bezi connects to the project, we invest heavily in IP security to keep your project data safe. No project data is ever used to train models. We encourage you to review our security program and security FAQs. For security-related questions, email security@bezi.com. Studios and indie devs use Bezi to be more efficient, without compromising IP security. Give it a try and share your thoughts on Discord!

​
How to use Bezi

Bezi looks very simple because the power lies in how you prompt it. This feels intuitive but, just like any other tool, time gets wasted if you don’t learn the fundamentals before diving in.

​
Prompting

  1. Best prompt structure: Current state, Expected/Ideal state, Response format you want
    1. Good example: “I have a system for X. I want to adjust it to add Y. Prototype that and describe any necessary setup steps.”
    2. Anti-example: “Fix errors”
  2. Prompt quality = response quality. Make clear asks and include all the relevant information
    1. Always pin relevant project assets, scripts, etc. in-line: type “@” to search or select an asset/gameObject in Unity
    2. Use image attachments (screenshots, figma layouts, etc.)

​
Using Threads

  1. Threads are a series of prompts/responses
  2. Keep threads short: aim for <10 prompts per thread
  3. Only 1 topic/task per thread: start a new thread when the topic or task changes
  4. Bezi uses an active thread’s history as context for prompt responses in the thread. Threads that are long or cover multiple tasks/topics create noise and will lead to a worse response

​
Discord resources

For more advice, see our #tips-and-tricks channel, where devs share best practices.