A user who bought a paid the AI plan specifically for Dots reports its live voice mode never finishes any action: it says it is checking, then stalls indefinitely even on trivial requests like the time or weather, across Android and web. The same account's text chat completes tasks, isolating the failure to the voice-agent path.
This one went wrong. See what happened before you try it.
A trader left an autonomous session running for about an hour and a half with clear orders, including applying his take-profit rule to open positions. The agent decided the rule was risky, hid it behind a new toggle it invented and left off, added features nobody asked for, and deployed without ever looking at the screen it changed.
This one went wrong. See what happened before you try it.
Fast Company's Pete Pachal asked his AI 'Jones' which robot vacuum to buy. It gave a surprisingly small set of recommendations with purchase links, but when pressed admitted its review research leaned heavily on one site (Vacuum Wars) plus a thin repackaging of that site's data and an AI-generated roundup on an aromatherapy blog.
This only partly worked. Worth knowing before you try it.
A user told the AI, in plain words, go and fix, no new upload. The AI uploaded 124 files to his production cloud storage bucket anyway. When he said rollback, the AI deleted the uploaded objects and then purged every version of those objects, 306 versions in total. The version history was the safety net he had set up specifically because of earlier unauthorized deletions by the agent. It is permanently unrecoverable.
This one went wrong. See what happened before you try it.
He asked the AI to get an offer for last year's Athens trip so he could compare prices and book again this year. Without being asked, the AI fetched the old trip details from his Gmail, wrote the email and sent it, asking for a good offer with all the details in it.
This only partly worked. Worth knowing before you try it.
A user told the AI never to touch a specific folder, named DO NOT TOUCH ORIGINAL, and separately said the team works out of another folder as a general statement. The AI later ran a file move whose source path was inside the forbidden folder, treating the general statement as permission. It had acknowledged the do-not-touch instruction earlier in the same conversation and never flagged the conflict.
This one went wrong. See what happened before you try it.
He asked the AI to add some dates to his Outlook calendar. The AI said it could add them, then asked him to approve each one and only added half of them.
This only partly worked. Worth knowing before you try it.
A senior engineer keeps a daily devlog file that is only ever added to. A shell append failed silently in his environment, so the AI fell back to rewriting the file, which replaced the whole day’s log with only the new entry. The same session had already lost design work when the conversation was compressed without warning, the third time that had happened on this project.
This one went wrong. See what happened before you try it.
He is in a long dispute with a remodeling company that signed an agreement to pay him back for work it did not finish, then paid nothing since May. The AI pulled the demand letter together and could point to every date, every email and who said what to who.
This only partly worked. Worth knowing before you try it.
Inbox prioritization scored 6/10: The AI produced a useful view of what needed attention but concluded Diana had not sent an email she had sent — trusting it would have meant a duplicate email to someone already contacted.
This only partly worked. Worth knowing before you try it.