ToShop DocsReporting Bugs
How to send a bug report we can actually act on.
A good bug report saves a round-trip. Capture these three pieces and we can almost always reproduce.
What to include
What you did
The goal you gave your agent, in plain language. Paste the prompt if you can.
What you expected
The result that would have been correct.
What actually happened
The wrong output, error, or behavior. Screenshots help.
If the bug is intermittent, mention how often (1 in 5 runs? always?). Including your app version, macOS version, and the model class in use also speeds up triage.
Where to send
Drop a message in our Telegram group: @toshop_ai.
Best for: quick questions, repro back-and-forth, anything you'd rather hash out in chat.
Join our Discord community and post in the bugs channel.
Best for: longer threads, screenshots, conversations you want others to find later.
support@toshop.ai if you can't reach us in chat — or for anything you'd rather keep private.
Best for: install failures, auth issues, sensitive details.
Response time
We aim to triage reports within one business day. Severe regressions get a same-day reply.
Security issues
Don't open a public issue
For anything that looks like a vulnerability, email security@toshop.ai directly. Coordinated disclosure terms are in our security policy.
What we don't ask for
Phishing red flags
We never ask for:
- Your model API keys.
- Your account password (auth is OAuth-only).
- Remote screen-share access without your explicit consent.
If anyone claiming to be ToShop support asks for these, it's a phishing attempt. Report it.