GPT DotFIELD GUIDE
Home/Essentials
Essentials

How to set up and use ChatGPT Dots (OpenAI Dots): setup steps, the first job to hand over, and what to do when a new Dot gets stuck

Set up ChatGPT Dots (OpenAI Dots) at chatgpt.com/dots, in the desktop app or in the ChatGPT mobile app. It comes with Pro ($100 to $500 a month, outside the EEA, UK and Switzerland) and Business Premium. Start with an access check and one read-only job, set custom rules before the first send, and see what fixed a new Dot that got stuck.

GPT Dot · Updated
OpenAI Dots product demonstration
Image source

The short version: what to hand over first, how to set it up, where it gets stuck

Can a new Dot do real work in its first week?

Yes, if the first job is one you can check. ChatGPT Dots (also called OpenAI Dots, and sometimes written "GPT Dots") is an always-on AI agent inside ChatGPT, launched on 29 September 2026: you give your Dot an ongoing job and the apps it needs, and it keeps working between conversations on its own cloud computer, messages you with results, and checks with you before decisions that need your judgment (What is ChatGPT Dots). Corey Noles put setup at about five minutes, and the first jobs that went well were all read-and-report work: @dyplaybook's Dot found an invoice 34 days overdue in a test inbox, Flavio Copes had two weeks of feedback grouped without a single reply sent, and BuildnWrite's Dot checked a hiring document against older emails and left its reply as a draft. What new users regretted in week one was anything that can't be undone: a reply sent before Corey had read it, a calendar event deleted the moment uehara said "delete that event", and Mac permissions that Jennifer Jolly ended up switching off herself after the Dot spent 22 minutes on them. So hand over one ongoing job, keep it to drafts, set the rules before the first send, and widen it once you've checked a few results. This suits anyone with an eligible plan and one recurring job they now check by hand.

How to set it up

  1. Check that you can get it. Dots are included in ChatGPT Pro ($100, $200 or $500 a month, for users 18 and over outside the EEA, the UK and Switzerland) and in Business Premium; Enterprise, Edu and Healthcare workspaces get a beta that an admin has to switch on (How to get ChatGPT Dots). Access rolls out gradually. After 整える旅行記 moved from Plus to Pro 100, there was no entry at first, and "Your dot" showed up in the left menu later (note, Oct 1, in Japanese).
  2. Open Dots at chatgpt.com/dots in a desktop browser, in the ChatGPT desktop app (Mac or Windows) or in the ChatGPT mobile app. Mobile web doesn't work. If the name you type won't save, 整える旅行記's saved once a pet had been picked for the Dot's look.
  3. Before you create it, open Plugins in ChatGPT to see what is already connected, and look at the "This computer" switch during setup. FSR found Mail and Drive already connected and the computer switch already on, left over from an earlier Dot.
  4. Connect only the app your first job needs, using the account you actually work in, and make the first ask an access check: 整える旅行記 asked "can you reach my GitHub? Only check, don't connect, change or create anything" before handing over any work. Mark Nguyen's Dot assumed Gmail while his agency uses Zoho, and the email part stalled. If the only Slack workspace you use belongs to someone else, leave it out: Joe Rice-Jones skipped Slack because connecting it would have handed the Dot other people's messages (XDA, Oct 8).
  5. Let the Dot interview you about your priorities and how you like to work, as Corey Noles did, or paste in a short handover brief written in a normal ChatGPT chat: what matters, the budget, and what to confirm before acting, as Haroka did. Then give it one ongoing responsibility and put the scope, the sources and the finish line in words: "all calendars" rather than "my events" (uehara), and "a link that opens" or "an entry in sent mail" as the result that counts (Artemis).
  6. Set the limits. Write "draft only" or "don't change anything" in the ask itself, because "send that draft" and "delete that event" were taken as approval. For standing limits, open Settings > Personalization > Custom rules and pick one of four levels per action: Take action without asking, Take action when you say so, Ask before taking action, or Hand off to you (Control your dot). You can also ask for a rule in the chat. Joe Rice-Jones asked his Dot to always ask before sending email, approved the Confirm custom rule dialog it showed, then asked for a test email to himself: it showed the sender, recipient, subject and body and waited for his approval in the chat. After a week, しろ sorted actions by two questions, whether a mistake can be redone and whether it reaches another person: research and drafts run without asking, scheduling and internal messages ask first, and anything sent outside the company or touching money or permissions is handed off. The rules were then widened a little at a time.
  7. When timing matters, ask for a fixed schedule with a time zone and an end date, have the Dot confirm it, and open the saved task in Scheduled. FSR asked for two checks and the edit screen showed a repeat that never ends.

Where it gets stuck, and what fixed it

  • It sent or deleted before you looked. Herman sent a reply before Corey Noles had read it, and uehara's "send that draft" and "delete that event" went through without another prompt. What worked: write "draft only" in each ask, and set sending to Ask before taking action or Hand off to you, then test the rule with an email to yourself.
  • A login, code or captcha stopped the job. In none of the cases on this page did a Dot sign in without its owner. What worked: have it list every login before it starts, then use the secure sign-in form or take over the Dot's browser; never type a password in the chat. The sign-in section below has the details.
  • The Dot's browser wasn't signed in, or the login expired. The Dot's browser is separate from yours, and apps and sessions on its cloud computer can disappear (neco., wschenkai). What worked: sign in once in the Dot's browser, and tell recurring jobs to report "login needed" instead of retrying.
  • "In progress" was really waiting for you. Approval prompts can sit inside a child conversation or a desktop task. linerking found one that way, and uehara's Notion deletion was aborted after about 21 minutes because nobody saw the prompt. What worked: look for the sidebar's "needs approval" mark, open Activity, or ask the Dot to read the child task.
  • Pause didn't stop everything, and Completed didn't mean it ran. Pause stops only the current main task, and FSR saw a one-time task marked Completed with nothing delivered. What worked: stop scheduled tasks in Scheduled and delegated ones in Activity, then read the conversation.
  • Stop didn't stop. Every press of Stop gave SatireLord "turn … is not active". What worked: send a plain "stop working" message in that chat.
  • It said the work was done when it wasn't. u/anthonyaluna's Dot reported a quote as accepted while the email was still in drafts. What worked: say what result counts as done, and check it outside the chat.
  • The first week went badly and deleting the Dot looks like a clean start. leon_rivers deleted a Dot that kept failing, and for more than five days afterwards the Dot list was empty while every attempt to create a new one failed with HTTP 409 and "cloud_aeon_recovery_required", in Chrome, Incognito and on iOS (OpenAI Community, Oct 19). What helps: change the rules, the connections or the job first, and read Dots not showing or not working before you delete anything.
  • It stops with "Your dot is on a break". That is a pause on the Dot itself, not your plan running out. What helps: don't reset the Dot, note when the break started, and see what that message means and what to do. Short answers to other common questions are in the ChatGPT Dots FAQ.
  • Computer access was easy to give and slow to take back. What worked: connect your computer only for a job that needs it, and write down which permissions you granted.

What it can and can't do in week one

It can:

  • Read connected email, calendar, Slack and files and flag deadlines, clashes and forgotten bills (@dyplaybook, Mark Nguyen, BuildnWrite, kensakuedison).
  • Find the right person from a first name and earlier emails, and save the message as a draft instead of sending it (Joe Rice-Jones).
  • Group feedback or mail by problem with links to the originals, and draft replies for you to send (Flavio Copes, BuildnWrite).
  • Run on a schedule, after a meeting or every weekday, and say so when a source isn't ready yet (curt.kennedy).
  • Carry on through a website once you've done the sign-in step (Yoma, 셩PM).
  • Talk with you without using your ChatGPT message limits; Work or Codex tasks it starts use those products' allowance (pricing and usage limits).

It can't, or shouldn't yet:

  • Sign in, change passwords or pay for you. Those steps come back to you.
  • Hold back after you've said "send" or "delete".
  • Read a whole inbox in one pass. Joe Rice-Jones's morning brief covered his latest 40 Gmail emails, and the Dot said so.
  • Prove its own follow-through. A Completed label or a "done" message isn't evidence.
  • Keep logins on its cloud computer indefinitely.

One message to start with

Based on what you know about me and the apps I've connected, suggest three ongoing jobs I could hand you first, and the sources you'd use for each. Before anything else, check which of those apps and accounts you can actually reach, and only report back; don't connect, change or create anything. Once I pick one: read and summarize only, draft any reply for my review, and don't send, delete, pay for or change anything. Add a custom rule that you always ask before sending an email, and show me the confirmation. Before you start, list every site that will need me to sign in, and stop there to wait for me. The job counts as done when [a result I can check outside this chat]. If you get stuck or need my approval, tell me what is blocking you and where I approve it.

1. Create your Dot on your computer or phone

  1. Open chatgpt.com/dots in a desktop browser, or open Dots in the ChatGPT desktop app on Mac or Windows.
  2. Follow the introduction. Connect apps such as email, calendar and files, or skip this and add them later.
  3. In the desktop app, choose whether to connect your computer. You only need this when your Dot should reach local files, code or apps.
  4. Pick a name and look. You can change its name, shape, color, eyes, glasses and accessories later.

You can also create it in the latest ChatGPT mobile app: name it, pick its look and connect plugins on your phone, then connect your computer from the desktop app whenever you need it. Mobile web is still not supported (Set up on mobile or desktop). Whichever device you start on, you keep the same Dot on the others. Steps follow OpenAI's Get started with your dot guide.

2. Connect only what the first job needs

Apps, contact methods and your computer are three separate connections. Apps (Gmail, Google Calendar, Drive, GitHub and others) let your Dot read and act on that information. A contact method, added from your Dot's profile with Add, lets you message it in Slack or Teams; it doesn't grant access to your inbox or files. Your computer only matters for local work, and it has to stay online with the ChatGPT app open while your Dot uses it. Texting your Dot is a limited US Pro beta per the Help Center.

Pick the app closest to your first job and ask your Dot to find one specific email, event, document or issue, so you know it's looking at the right account.

Your computer is the broadest of the three connections, so save it for a job that needs it. Tech columnist Jennifer Jolly (Oct 6) uses her Dot every day, but only with a burner email. She let it tidy her Mac desktop, which meant giving it permission to control the Mac and see everything on screen. As far as she could tell, all it did was turn on Stacks, a built-in macOS feature she could have switched on with a right-click. When she asked the Dot to give the access back, it spent 22 minutes finding two settings and then asked whether she was sure, and she ended up turning them off herself. If you try a local job in week one, write down which permissions you granted so you can switch them off yourself.

3. Let it introduce itself, then give it a responsibility

Your Dot introduces itself, uses your relevant ChatGPT memory and connected apps to learn about your work, and suggests where it can help. You can talk to it while it gathers that context. OpenAI's own example of a good first responsibility:

Help me keep our offsite on track. Use the plan and venue emails I shared to keep track of decisions, deadlines, and unanswered questions. Let me know when something needs my attention, and draft suggested replies for my review.

Review the first result and name the exact fix: shorter, source links on every item, a different priority order. In the desktop app, your Dot's profile has an Activity view where you can check work it handed to ChatGPT Work or Codex and anything waiting for your input.

4. Keep the work moving

You don't need a new conversation for each request. Keep talking to the same Dot to add context or change priorities. When timing matters, ask for a fixed schedule with a time zone and an end date, and ask it to confirm what it set up:

Check the connected planning channel each weekday at 9 AM Central for the next four weeks. Update my checklist when a deadline changes. If a deadline is at risk, message me in ChatGPT and draft a reminder for my review. Confirm the schedule.

Where a connected app supports it, you can also have your Dot act when something happens, such as a new bug report in a Slack channel. Hanging up a call or ending a conversation doesn't necessarily stop work you assigned. How to stop work is covered further down this page, in "How to stop your Dot".

What new users saw in the first minutes

A Dot that started messaging within three minutes (@ugc.growth.lab)

A Japanese user posted a lock screen with four push notifications from "dot" that arrived one to three minutes after setup: it said hello, offered to chat any time, asked to be given a name, and said it would look for useful things to do in the background. The caption translates as "the pressure from the moment you install it is something else."

A deadline question before setup was even finished (@kensakuedison)

Partway through setup, kensakuedison's Dot asked whether he had already cancelled a service that has a 30-day cancellation deadline. Nobody had asked it to look for deadlines; it found one in the context it was gathering.

A scratchpad of what's pending (Aishwarya Srinivasan)

Aishwarya Srinivasan named her early-access Dot Bit and showed the scratchpad it keeps for her: what's pending, what needs her attention, and where it can help. Her summary of the setup is "give it a goal, tell it how you like things done."

Apps already connected, and a computer switch already on (Future Stack Reviews)

When Takashi Fujino's team at Future Stack Reviews (FSR) created a new Dot on Oct 4 (macOS app, Japanese interface), the app-connection step already listed Mail and Drive as Connected, and the only way past it read "Continue without connecting additional plugins." Nobody typed anything, and four minutes later the Dot had posted two suggestions drawn from the editor's email. The next screen showed the switch for "This computer" already on, although OpenAI says local access starts off. An earlier Dot on the same account, deleted that day, had been connected to the same Mac. They switched it off, and the profile then showed the Mac with an Allow button (FSR's test write-up). Before you create a Dot, open Plugins in ChatGPT to see what is already connected, and look at the computer switch before you continue.

First jobs people gave a new Dot

1. Five-minute setup, then an interview (Corey Noles, The Neuron)

Corey Noles named his Dot Herman and estimated the setup at about five minutes. He connected Google Calendar, Docs and Drive, and the most useful step was letting Herman interview him about his priorities and how he likes to work. Early on, Herman wrote a reply to a simple email and sent it before he had looked, so he now tells it to show him outgoing messages first.

2. Editing a whole reel (Matt Paige)

Matt Paige, in the early-access group, gave his Dot its first job: editing the very reel he posted, and says it turned out well. His suggested first message for anyone starting: "Based on what you know about me and the apps I've connected, what should I delegate to you first?"

3. Logging into the ad dashboard on a voice call (Yoma, Hong Kong)

Yoma named his first Dot Ms Choi and gave it his Meta ads as its first job. On the call, the Dot asked whether to log in with Facebook or a Meta work account, Yoma typed the password and verification code himself, and the Dot switched the page back to Chinese when it flipped to French. It then compared which ad types sold better, pointed out that profit can't be claimed before costs are deducted, and suggested checking ad numbers against real orders.

4. One line, a closed laptop and a $450 invoice (@dyplaybook)

@dyplaybook named a Dot Ledger and gave it one instruction: "Find anything I've forgotten that costs me money or a deadline. Don't send anything." On a test inbox set up for the video, it came back with an unpaid $450 invoice that was 34 days overdue, a follow-up already drafted, and a question before sending.

5. A DevOps bot that came back with homework (u/jacob-indie, Reddit)

On day one, jacob-indie pointed a Dot at six self-hosted tools: GlitchTip error tracking, Hetzner server stats, Plausible analytics, Google Search Console, logs and a Forgejo git server. It came back with suggestions such as setting up analytics goals and fixing small bugs, which, the post jokes, "is starting to look like work really."

6. Every Tech Week event, found and RSVP'd (Grace Ling)

Grace Ling created her Dot, Fluffle the bunny, at OpenAI DevDay and had it find events for SF and LA Tech Week and RSVP to all of them.

7. Calendar and Slack flags for an agency (Mark Nguyen, The Slide Factory)

Mark Nguyen's Dot, Toby, read the agency's Slack and calendar and flagged a Monday client discussion about work outside the budget that overlapped another meeting, then a second conflict on Wednesday. Email stalled because Toby assumed Gmail while the agency uses Zoho through Apple Mail and Outlook, so start with the accounts you actually use.

8. Group two weeks of feedback, reply to nobody (Flavio Copes)

Flavio Copes suggests connecting fewer apps than you're tempted to. His first job: read Slack #feedback and two weeks of Gmail support mail, group the reports by problem, count how many people hit each one, link the originals, separate bugs from feature requests, and don't reply to anyone.

9. A hiring document reviewed against earlier emails (BuildnWrite)

On day one with a Korean Pro account, BuildnWrite opened the Dot and, before asking for anything, saw three tasks it could take off their plate drawn from recent email. They handed over a hiring-project evaluation document. The Dot read the email and two attachments, compared them with earlier messages in the thread, flagged an explanation that no longer matched a setting that had changed later, and drafted a reply without sending it. It also warned, unasked, that a storage-plan email was about to expire. Their takeaway for a first job: start with read-and-summarize work, and keep send permissions closed until you've checked a few results.

10. A meeting summary scheduled before the call (curt.kennedy)

curt.kennedy scheduled his Dot to run after a virtual meeting the next day: retrieve the Google transcript, write a summary of decisions, action items, owners and deadlines, keep checking if the transcript was still processing, and say so if capture failed. His part was to join as host in the browser and handle any recording prompt. The Dot told him he wouldn't need to prompt it again for that run.

One setting worth copying in week one

Dan Shipper set his iPhone Work Focus so that only his Dot can send push notifications while he's in work mode, which makes the Dot the one thing allowed to interrupt deep work.

Sign-ins, codes and captchas: where first jobs stall

The first real job usually stops at a login screen. Here is what happened at a sign-in, a verification code or a captcha, grouped by how it ended.

The owner typed it in, and the job carried on

When 셩PM's Dot reached a login while cancelling an unused subscription, it stopped and sent a separate secure box with a note to type the password there, not in the chat. 岩永奈々 of アルル制作所 signed in by taking over the Dot's browser, and the Dot confirmed nothing had been published or scheduled. Axton Liu took over for one sign-in during an internship search. Future, Already did the Government24 login and ID check by hand before the Dot filed a move-in report, and 이성곤 typed his Garmin password and code on his own Mac mini after the Dot confirmed the access would be read-only.

The code was read out on a call

u/BraveBrush8890 read the Walmart login and 2FA code to the Dot while driving, and Yoma gave the Meta ads password and code during a call. Both jobs finished. OpenAI's protection for passwords covers the secure sign-in form; it doesn't cover passwords you share in a chat or document, and a code said aloud on a call goes into the conversation too.

A captcha came up

Dr Nici Sweaney's Dot asked whether it could complete an "I am human" check and handle future ones; she agreed, and it saved that as a standing rule. Reece Rogers let his Dot try a puzzle captcha that was blocking a cancellation. It failed and asked him to solve it.

The login didn't carry over

neco. found the Dot's browser is separate from your own, so expect to sign in again there. wschenkai came back to find WeChat gone from the cloud computer and WhatsApp Web asking for a new login. BoomBigNose still had to sign in to Google Sheets by hand before the Dot could fill the sheet.

Money or a standing login

When an internet provider asked for bank details, Allison Johnson typed nothing into the Dot's browser and finished on her own computer (errands cases). simon_vaerion_roc went the other way: one login to the NTU COOL course site in the Dot's cloud computer now feeds a digest every morning and evening.

What to remember at the sign-in step

In none of these cases did a Dot sign in without its owner supplying the password or code. You may need to give an authentication code or take over for a security check, and changing a password always comes back to you. The jobs that went smoothly were the ones where the owner knew in advance which step would be theirs.

Four copyable prompts

Each one targets a problem that came up more than once above. Swap the parts in brackets for your own.

1. Find every login before you start

Built from 셩PM, neco., 岩永奈々 and 이성곤. It avoids a password typed into the chat and a surprise login halfway through a job.

Before you start, list every website in this job that will need me to sign in. When you reach one, stop and send me the secure sign-in form, or ask me to take over your browser. Never ask me to type a password or code in the chat. After I sign in, tell me whether the session will still be there next time.

2. A captcha rule you choose

Built from Dr Nici Sweaney and Reece Rogers. It avoids failed attempts and a captcha rule you didn't mean to save.

If a site shows a captcha or an "I am human" check, stop and tell me the site and the step. Don't try to solve it and don't save any rule about captchas. I'll take over, solve it and return control.

3. Say where to stop

Built from 岩永奈々, neco., Reece Rogers and 셩PM. It avoids a Dot that goes further than you wanted once it is signed in.

Go as far as [the cart / the cancellation confirmation page / a saved draft] and stop there. Show me what the final screen says and wait. Paying, cancelling, publishing and changing passwords are for me to do.

4. Watch for a lost login on recurring jobs

Built from simon_vaerion_roc, wschenkai and BoomBigNose. It avoids a daily digest that quietly leaves out a site after the session expired.

This check runs every morning and evening. If you find you're signed out of [site], or an app you installed is gone, don't keep retrying. Message me "login needed for [site]" and mark that part of the digest as missing.

More sign-in stories by job: shopping and checkout, family paperwork, the Dot's cloud computer, course sites for students and teachers, publishing to a blog or social account and handing over a job on a voice call.

How to stop your Dot, and what stopping actually did

OpenAI describes three separate controls (Control your dot). Pause stops your Dot's current main task, but not every delegated task and not future scheduled runs. A delegated task is stopped from Activity in your Dot's profile. A recurring task is disabled or deleted in Scheduled. Stopping doesn't undo actions already taken, and OpenAI adds that a completed run doesn't by itself confirm the result was achieved or delivered (Tasks and memory). The Dot menu on FSR's screen offered Rename, Pause, Reboot and Delete. Here is what happened when people actually used these controls.

Three pause tests, one run each (FSR, Oct 4)

FSR wrote down what it expected before each test, on one Pro 200 account.

  • Pause while the Dot was writing a long reply. The message box turned into a Paused label and nothing more arrived for 54 minutes. A minute after Resume, the reply came.
  • Pause one scheduled task, not the Dot. No result arrived at the scheduled time. Ten minutes later the Dot posted that the check "did not run at the requested time", did the check itself, gave the result and said the schedule was disabled. Scheduled then listed the task as Completed.
  • Keep the Dot paused while a one-time task came due. The task was meant to send the single word "ping". Nothing arrived during the pause, after Resume, or by the next morning, yet Scheduled listed the task as Completed. Fifty minutes after Resume the Dot said, unprompted, that there was "no recorded run". FSR ran no control without a pause, so it doesn't claim Pause was the cause.

The same tests turned up a schedule detail worth knowing. FSR asked for two checks 20 minutes apart. The Dot confirmed the right times and the end, but the task's edit screen summarised it as a 20‑minute repeat that never ends; the two-run limit only showed once the recurrence rule was opened. The saved instructions were the Dot's own rewrite, with constraints FSR hadn't written (FSR test write-up, sections 05 and 06).

When Stop doesn't stop

SatireLord (macOS, Pro 200, Oct 2) had a durable chat in the Codex app that stayed visibly running while its runtime was idle. Every press of Stop returned "turn … is not active". Pausing the Dot and clearing the goal didn't clear the spinner, and neither did disconnecting and restarting. What worked was an ordinary message, stop working, sent in that chat. The reply was "Understood. I'm stopping work now. No further changes were made.", and the chat went back to normal (openai/codex #50450, resolution comment). A delegated task stuck at "running" for nine days with "Could not stop this task" is on Dots not showing or not working.

"In progress" can mean "waiting for you"

linerking (Sep 30) asked a Dot for a read-only task on a connected Mac. In the main Dot conversation the task only ever showed as in progress. The approval prompt was inside the desktop task; once it was approved there, the result arrived three minutes later (#49531). Wulfgardr (macOS, Oct 7–8) had delegated tasks ask for input that never showed up in the main conversation, and got them back by having the Dot explicitly read the child tasks (comment). How approvals carry between a Dot and its Codex tasks is on Dots with Codex.

A safer stop order, and two asks

This order avoids the surprises described above.

  1. Open Scheduled first and note what is due soon. Pause or delete those tasks there, rather than pausing the Dot.
  2. Open Activity and stop each delegated task you want ended. A task that looks stuck may be waiting for your approval.
  3. Pause the Dot only to stop what it is doing right now.
  4. If Stop fails or a spinner won't clear, send a plain message such as "stop working" in that chat.
  5. Afterwards, read the conversation. A task marked Completed may not have run, and a paused one may have been done another way.

Two asks you can copy. The second borrows one rule from FSR's own template.

Before I pause you: list every scheduled task due in the next 24 hours and every delegated task still running, with its name and status. Mark any that are waiting for my approval or input, and tell me where I approve it. Don't change anything.

I've paused or deleted [task]. Don't run that check any other way and don't recreate it. If you think it still needs to run, ask me first.

Your first week: six changes worth copying

People who used a Dot for more than a day changed how they worked with it after the first job. These six changes are easy to copy, and the full cases are on the linked pages.

  1. Write the handover before the first job. Haroka, a UX researcher who used a personal Pro account for a week (note, Oct 7), first wrote a handover brief in a regular ChatGPT chat: what matters to the family, the budget, and what to confirm before acting. The Dot then worked from that brief on recipes and a shopping list, seasonal orders within a budget, and reminders to leave on time. Those are cases 27 and 28 on family and health.
  2. Name the scope in words. uehara gave a Dot 17 real tasks over three days and checked the results against the apps themselves (DEV, Oct 9). The first schedule summary read only the main calendar and missed two events. Once the ask said "all calendars", the Dot read all 16 of them. The weekday brief set for 8:30 arrived at 8:44, which is on the morning brief workflow page.
  3. Treat "delete it" and "send it" as the approval. In the same test, "make a draft" stopped at the draft, but "send that draft" sent it without another prompt, and "delete that event" removed it in about 30 seconds even though the calendar was set to confirm before changes (tested once). In week one, put "draft only" or "don't change anything" in the ask itself.
  4. Look for approval prompts in the child conversation. When uehara asked for a Notion page to be deleted, the Dot switched to Chrome on the connected Mac in a separate child conversation, and the permission prompt appeared only there. Nobody pressed it, so the step was aborted after about 21 minutes, and the main chat said only that the deletion hadn't happened. If a report doesn't arrive, check the sidebar for a "needs approval" mark and open the child conversation. The full case is on Notion.
  5. Check follow-through, not only the report. Matthew Bradford's Dot, Riri, drafted email replies by default and usually kept the CRM and task board up to date without being told (Oct 9). u/anthonyaluna, who runs a property management business, saw the other side (r/AI_Agents): the Dot said a quote had been accepted while the email was still sitting in drafts, and it brought back requests that had already been answered. The post compares it to a new hire whose follow-through still needs checking. More cases like these are on small business and email triage.
  6. Say what counts as done, and who acts if it stops. Artemis (@artemis.log.jp, Instagram, Oct 10, in Japanese) put a Dot named ABYSS into real work for about ten days. The jobs that finished all left something outside the chat: a check that a scheduled article could be read on the public page, a filled-in Word draft ready to submit, a first sort of 202 email threads, and six tasks registered with the right people contacted. The job that stalled was the write-up about Dots itself. The text and cover were ready, but the Dot didn't save the post because it couldn't confirm the publish instruction in the conversation, and it refused the step of handing the finished draft over to the computer. Another AI took the draft over, ran it through review and saved it as a draft. Artemis's main takeaway is that a Dot is closer to a colleague with its own PC than to a smart chat, and that talking to it doesn't count against usage while Codex-type work tasks do. Since then, every ask says what result counts as done and who does what if the work stops. Artemis hasn't measured time saved or revenue yet.

A check-in to send at the end of the first week:

It's the end of your first week. List every job I gave you, what you actually finished, what is waiting for my approval and where that approval is, and anything you reported as done that I should double-check. Don't change anything.

A definition of done to add to any first job, based on the ABYSS report:

Job: [task]. It counts as done when [a result I can check outside this chat, such as a link that opens, a file in Drive or an entry in sent mail]. If you get stuck or can't confirm an instruction, stop, tell me what is blocking you and what you need from me, and don't hand the work to another tool without asking.

Copyable first asks

Accept one proactive suggestion, draft only, as in the BuildnWrite day-one report:

Pick one of the tasks you already suggested from my connected email or calendar. Do only that job. Read and summarize; draft any reply for my review; do not send, delete, or change anything. When you're done, list what you used as sources.

Based on what you know about me and the apps I've connected, what should I delegate to you first? Suggest three options and say which sources you'd use for each.

Find anything I've forgotten that costs me money or has a deadline. List each with a link to the source, and draft any follow-up for my review.

Read my Google Calendar and Slack for the next five days. Flag calendar conflicts and threads that look like scope, budget or scheduling problems, one line each with a link.

Where to go after the first job

Copy this task brief

How to set up ChatGPT Dots, which first job to hand over, how to set and test custom rules in week one, where new users got stuck and what fixed it, and the first jobs people gave a new Dot.
Download Markdown ↓

Sources & further reading