A 35 minute call with Dots to make one task, and it still got it wrong
He spent 35 minutes on a call with Dots trying to create a task on his remote PC. Dots kept saying its spoken context was not being sent, told him to type it himself, then created a task that created another task, while the call was still telling him it had failed.
How it works
- Call Dots and describe the task
- Get repeated errors about spoken context not being sent
- Type the request himself as told
- A task gets created that creates the task he asked for
- The call still reports failure
Why it’s worth knowing
The tool built to take instructions by voice could not receive its own spoken instructions.
Where it’s from
Summarized from a public post on reddit.com. See the original ↗