A missed scheduling detail
Dan Shipper says his Dot connected a Slack discussion with travel plans and flagged a conflict before he booked a flight.
A Dot is one personal agent inside ChatGPT. It can use its own cloud computer, work with apps you choose to connect, and bring back work for review. The reports below include completed jobs and failures.
Bot Cabinet has not task-tested this Dot workflow. The results below belong to the people who ran them.
Read what testers completed, where tasks failed, and which permissions caused trouble. Bot Cabinet has not independently tested these results.
Dan Shipper says his Dot connected a Slack discussion with travel plans and flagged a conflict before he booked a flight.
Peter Yang reports that his Dot found a five-figure sponsorship issue he had overlooked while reviewing his business work.
Yang says a transcript-to-newsletter task failed, and the failure was hard to find in a busy conversation.
Shipper reports missed replies, awkward site logins, and local-computer permission dropping during his early test.
Chase AI showed his Dot starting a Codex task and passing instructions to it while he continued using the Dot. He later opened the resulting local page.
In the same test, the task first hit a startup error, appeared outside the project he named, and the Dot did not clearly report that the preview was ready.
Peter Yang walks through research, app-launch work, sponsorships, and tasks Dots could not finish. His comparison with Grok Bot and Muse is his judgment, not a Bot Cabinet benchmark.
Open the video on YouTubePaste meeting notes to get a list of promises and follow-ups. Start without connecting an inbox.
Dots are rolling out to eligible Pro and Business Premium users, plus admin-enabled Enterprise beta workspaces. Create your first Dot on desktop web or in the ChatGPT desktop app. If you do not see it yet, check OpenAI's current help page.
Copy the practice prompt below, or paste notes from one real meeting. No connected accounts are needed.
Check each claim against your notes. Make sure missing owners or dates are marked unknown, and that the Dot says what failed.
Try the example before sharing your own notes.
Help me sort these three made-up commitments for this week: - Send a draft agenda to my team by Tuesday afternoon. - Review a six-page proposal by Thursday. - Decide whether Friday's project meeting needs to happen. Make a one-page brief. For each commitment, show the next action, owner if known, due date, and which line above supports it. Mark anything missing as a question; do not fill gaps with guesses. Then tell me what you finished and what you could not determine. Use only this message. Do not connect apps, send messages, change a calendar, set a reminder, or keep working after the brief. Stop for my review.
Remove details you do not want to share. Keep the Dot from sending or changing anything yet.
I am going to paste notes from one meeting. Find every promise, decision, and open question in those notes. Make a short table with: item, owner, due date, next action, and the exact line of my notes that supports it. Write "not stated" when a field is missing. Put the three most urgent follow-ups first. Do not send a message, edit a document, create a task, or schedule anything. End with two lists: "finished" and "needs my decision." Wait for my review before taking another step. Meeting notes: [Paste notes here. Remove private or sensitive details you do not want to share.]