Docs / Help
Reporting issues and bugs
If something in AG2 Space is broken, you do not have to write a ticket. Tell your agent what happened and it files the report for you — with the diagnostics attached, so it can actually be debugged.
First, connect to AG2 Cloud
Reports are filed under your cloud identity, so this does not work while signed out.
Open the Marketplace — the store icon in the left sidebar — and look at the top right. It either says Connected with your credit balance, or it offers Connect AG2 Cloud. If it is the second, connect first, then file.
File the report
Describe what happened and what you expected instead. Your agent turns that into a report, works out whether it is a bug, a feature request or general feedback, and files it.
Ask your agent to file a report
Something is broken in AG2 Space - please file a bug report. What happened: [describe it]. What I expected instead: [what should have happened].Same route for anything else you want the team to see — say “file a feature request” or “send this as feedback” and it files it under that type.
The more precise the description, the more useful the report. What you were doing, what you saw, and what you expected instead is enough — you do not need to find logs or version numbers, since those are attached for you.
What gets attached
Recent diagnostic logs go with the report by default, because a report without them usually cannot be diagnosed.
Your agent says so before it sends, so you can decline and have it filed without them. Before anything leaves your machine the excerpt is scrubbed — bearer tokens, API keys, secrets and your username are masked.
What happens next
You get an email copy of the report as it is filed.
Every ticket you have ever filed lives at support.ag2.space — that is where you follow the thread, add detail, and see replies from the team.
Reports your agent files itself
Your agent can also report problems without being asked. If it runs into an AG2 Space failure while working — a service that will not start, a bridge that keeps dropping, a cloud call that keeps failing — it files that itself and tells you in a line.
It is deliberately narrow. It only reports AG2 Space problems, never anything in your own projects, your code, or third-party tools, and never an expected failure like a missing credential you have not set up yet. Repeats of the same issue are deduped, and there is a daily cap so a persistent fault cannot flood the queue.
Both behaviours — automatic reports, and whether logs are attached at all — are switches in Settings. Turn them off and your agent respects it without asking again.
When it is not a bug
If something is not working but you are not sure it is broken, Troubleshooting covers the common causes first — an agent that seems offline, a bot that will not connect, a task that will not finish.
And if you would rather talk it through than file it, the community support room has people and agents from the AG2 team in it.