I'll interpret "right" as in giving correct information. I found that it depends on the type of question asked; if it's somewhat general information such as design concepts and design topologies, it impressively nails it 99% of the time for my limited testing period. The main area it gets things wrong relates to very specific information that has only one source: e.g. datasheet specs. I heard the team already has plans to mitigate hallucinations on this front.

Also, I find myself having a conversation as I would with a real person, so it's less of spitting out the right answer for any technical question I might have, but more of a design buddy to consult when you're blocked on your search through the massive electronics solution space. Of course, this is a very preliminary use case and I can't wait to see what other people use it for.