In a conversation with Emma
If the problem happened in Agent Mode, report it right there in the same conversation. Type report bug, followed by what you wanted and what you got instead. “Report bug — I asked for three LinkedIn posts under 150 words and got two posts over 300 words. I expected three short posts in my founder voice.” There’s no command syntax to memorize. Emma recognizes the intent, so “file a bug”, “this is broken”, or simply describing what went wrong all work the same way. Reporting in the same thread matters: Emma files the conversation context along with your description — what you asked for, what she did, and any errors she hit along the way. Starting a fresh chat to report a problem strips that away.From the portal
Click the + in a conversation bubble button in the top right corner of the portal. Use this when the issue isn’t tied to a specific conversation — a page that won’t load, a button that does nothing, a setting that won’t save — or when you’d rather describe the problem in your own words outside of chat. Describe what went wrong, and what the ideal outcome would look like. That second part is worth writing even when it feels obvious: it’s often the difference between a report that gets fixed and one that gets misread.What makes a report actionable
The single most valuable thing you can include is what you expected versus what actually happened. Everything else is secondary.1
Lead with expected vs. actual
“I expected X, I got Y.” One sentence. This is what lets someone reproduce the problem without guessing at your intent.
2
Add steps to reproduce, if you can retrace them
What you clicked or asked, in order. Even a rough sequence helps.
3
Name the page, for portal issues
Which screen you were on when it broke.
4
Attach a screenshot, if it's visual
Emma can attach screenshots you provide, but she can’t take them.