Chat, builds & changes

Choose how Lulu thinks#

The composer lets you choose a thinking level. Auto chooses a route for the request; Standard is a useful starting point. More involved requests can use Advanced or Expert (Gemini), or Ultra when your account includes it. The available choices and estimate are shown in the app.

Give Lulu useful context#

• Work in the game you want to change.
• Select or mention the relevant feature rather than asking Lulu to rebuild everything.
• Attach a reference image when appearance matters.
• Explain the expected result, including important controls and how to test it.

Read the build card#

A completed build can be saved in LuluLabs before it has been added to Studio. Follow the card’s delivery state. A saved-only result must be sent to Studio before it can run there. If the card offers Put it in, use it when you are ready to add the result.

Use Stop while a request is running if you need to interrupt it. Check the resulting card and Studio afterward; work already delivered can still be present.

Undo and repair#

Use the build’s Undo control when available to revert that build. For a repair, describe the problem in the same game and include the relevant error or steps to reproduce it. If a repair changes a core mechanic, test that mechanic again.