Conversation and discussion
Not every message is a build command. Sometimes you want to ask, consult, or understand an option before you decide. Conversation in codeyy is flexible to serve both cases.
Build request or discussion?
When you write a clear command to execute ("add a contact page"), the assistant builds. But when you ask a consultative question ("what's the best way to display products?", "do I need a database for this?"), it's best to get an opinion and discussion before any execution.
Consult before you build
Discussion before building is an excellent habit for large tasks. Ask the assistant about possible approaches, or the pros and cons of an option, or the best arrangement of sections. Once you agree on the vision, ask for execution. This saves time and credits and reduces iteration.
If you want just an opinion without the assistant starting to build, make your question explicit in asking for advice: "I'm consulting only — don't build yet: what's your take on…?"
The assistant knows your project
During discussion, the assistant draws on the actual context of your project — what you've built so far — not generic answers. So its advice is practical and tailored to your specific case. Learn more about this in How the assistant remembers your project.