GPT DotFIELD GUIDE
Home/Guides
Guides

How to get a ChatGPT Dot morning brief from calendar and Gmail — 42 real setups

Schedule a ChatGPT Dot morning brief from calendar and Gmail: Help's own example is a daily calendar check. Connect only what you need, ask before send or calendar changes, then copy from 42 real daily-digest setups—overnight reports, five decisions a day, and briefs the Dot wrote for itself.

GPT Dot · Updated
OpenAI Dots demo: Dot Alfred updates next-step slides for a proposal review
Image source

The short version: what a good morning brief looks like, how to set it up, where it gets stuck

The verdict

A morning brief is worth setting up if you ask for decisions, not a digest. The briefs people kept are short lists of what needs them today: five decisions plus the replies owed (@hkunimitsu), a "Decisions needed" section (Tiffany Kyazze's Pixel), next steps and blockers from a Notion board (Snapper AI). The most valuable items are often ones nobody asked for, such as a visa application that had gone quiet for eight days (Igor Pogany) or an event QR code sent on the morning it was needed (Flavio Adamo). A bedtime instruction turns the same habit into an overnight work report (@koh_kira). The weak spot is trust after the first week: a brief that looks finished is not proof that it ran on time, read every source or got its facts right, and a scheduled run that sends mail on its own is where things went wrong. Start read-only, delivered to the Dot chat, and add more once a few briefs have checked out.

How to set it up in seven steps

  1. Create the Dot (getting started) and connect only what the brief needs: Google Calendar for the day, Gmail for mail that needs you, and Slack if you want the brief in a channel.
  2. Run one brief by hand and open every source link before you schedule anything. The Rundown's practice guide does this with sample notes before any live source is connected.
  3. Ask for the schedule with the four things OpenAI lists for recurring work: what to check, when to run (time, time zone and end date), which changes deserve a notification, and where to deliver the result. Then ask the Dot to confirm what it saved (Tasks and memory). You can also let the Dot draft the task, as Tim Moylan's dot-face did, and read its wording first.
  4. Say what to leave out and how to mark doubt. Chaen's mail summary skips newsletters and automatic notifications and writes "needs checking" instead of guessing; dot-face separates confirmed facts from uncertain ones and looks for newer replies before calling anything outstanding.
  5. Put two lines at the top of every brief: what it covered (time window, sources read, sources it couldn't open) and when the last brief ran. Lee Shand valued the "partial day" label most, and a last-run line makes a missed morning visible the next day.
  6. Keep the scheduled run to reading and drafting. Set a custom rule so sends and calendar changes ask first, and have drafts collected in a list you approve in a live chat, as けんすみ does with an overnight Dot that never sends. How approvals work is on what is Dots.
  7. Check the saved task under Scheduled for the first few days, not the chat's description of it. Open the task to change its repeat schedule, time or completion notifications; a run marked completed is not the same as a brief you opened (Getting started with your dot). Since the October 5–9 update your Dot can also read and edit your ChatGPT Work automations when you ask it to (what's new, October 5–9).

Where it gets stuck, and what worked

  • A confident summary of half the day. Lee Shand's Dot marked its draft as covering only the morning, and one item still sounded more certain than the conversation behind it. What worked: a coverage line at the top and a source link on every item.
  • The Dot's own edit to a scheduled task was refused with "You cannot modify this task." The same edit worked eleven minutes later in the task editor on the ChatGPT website (OKJOIZJ). What worked: change the task there instead of asking for a new one.
  • The Dot couldn't see every scheduled task, while a ChatGPT Work chat could list them all (markifur). What worked: list what exists before creating anything; recreating a brief can leave two live jobs sending duplicate alerts.
  • "Stop everything" took fifteen minutes and a manual stop (stream727). Pausing stops the current main task but does not cancel future scheduled runs; stopping active work and cancelling a schedule are separate actions (controls). What worked: disable or delete the brief under Scheduled and ask the Dot to read each task's state back.
  • A trigger went quiet without an error. Daareek's new-mail trigger stopped after a second Gmail account was connected, and lucas27's custom events were accepted but never ran the task. What worked: a "last brief" line, and checking the task's last and next run before rebuilding it.
  • A break with no reset time. ivg-design's Dot answered "on a break" from about 18:50 to 20:30 EDT, so any brief due then would not arrive. What worked: the same last-run line, which shows the gap the next morning.
  • Too chatty, too quiet, or forgetful. The fix from Graham (@Graham_Tonkin) for noise is to ask only for new and relevant items during working hours; Riley Brown's hourly check sends nothing unless one of his written conditions is met. Ravin Sharma's Dot kept forgetting earlier context, and Peter Swartz kept his existing admin routine as the source of rules, using the Dot to direct it.

What it can do, and what it can't yet

It can read your calendar, mail, Slack, a Notion board or a course site at a fixed time and turn them into fixed sections; flag something you didn't ask about; keep working overnight within what you've approved and report at a set hour; rewrite one page in place every morning, as Brian Sunter's does; and deliver the brief in the Dot chat or a Slack channel. In the reports below it could not yet always edit or even see its own scheduled tasks, warn you that a trigger had stopped firing, stop all delegated work with one request, or run while it was on a break. Recent activity also mixes one-off checks with scheduled runs, so use Scheduled when you want the list.

One message to start with

Every weekday at 7:30 [IANA time zone] until [end date], send me a morning brief in this chat. Start with one line saying the time window it covers, the sources you read, any source you couldn't open, and when the last brief ran. Then list only what needs me today: decisions, replies I owe, meetings that changed, and anything stalled for more than three days. Mark each item "confirmed" or "needs checking" and link it to its source. Leave out newsletters and automatic notifications. Only read and summarize; put any reply you'd send into a "Drafts waiting for me" list. After you save the task, reply with its title, time, time zone, days, end date, where results go and the next run time.

Quick answers

What is a ChatGPT Dot morning brief?

A short, recurring update your Dot builds from connected apps (usually Google Calendar and Gmail, sometimes Slack) and delivers in the Dot conversation—today's meetings, mail that needs you, decisions waiting, or work it finished overnight—instead of a vague "summarize my life" dump.

How do I schedule one?

Ask your Dot to run a recurring check with a time, time zone, and end date. OpenAI Help's own example is asking it to review your calendar each morning and tell you what's coming up. Manage the saved task under Scheduled in your Dot's profile (or the Scheduled section in ChatGPT). Run one full brief by hand and open every source link before you rely on the schedule (Getting started with your dot).

Which apps should I connect?

Only what the brief needs: Google Calendar for the day, Gmail for mail that needs you, and Slack if you want delivery to a channel. Set a custom rule to Ask before taking action (or Hand off) for any send or calendar change.

Can it report overnight work?

Yes—several of the setups below ask the Dot to summarize what it did while you slept. Scheduled runs and proactive updates appear in the conversation; a task marked completed is not the same as a brief you actually opened, so check the first few deliveries.

Is this the setup page?

No. This page collects real morning-brief setups people posted about their own Dots. For the step-by-step template and shorter copyable asks, use the morning brief workflow.

Decisions first, not a digest

1. Five decisions a day, plus the replies he owes (@hkunimitsu)

The founder of gumi, posting as @hkunimitsu on Threads (Japanese, Oct 7), already had Gmail, Google Calendar, Slack, Drive, and Notion connected to ChatGPT, so the tools themselves didn't feel new. What changed is that the Dot now owns the job. Every morning it checks email, Slack, and the calendar and lists only the five things he has to decide that day. It also keeps a running list of messages he promised to answer but hasn't, messages where he's waiting on someone else, and deals that have stalled for a few days. Before meetings it reads past mail, the last minutes, and related files, then lists what to ask and what homework is left over from last time. His summary: "a super-capable secretary and chief of staff."

2. A personal agenda she didn't have to ask for (Tiffany Kyazze and "Pixel")

Tiffany Kyazze (@techtiff.ai) got tired of always texting ChatGPT first, so she gave her Dot, Pixel, a morning routine (Threads, Oct 8). Every morning Pixel checks her email, calendar, and open tasks and sends a personal agenda. Her screenshot of the Oct 7 edition, "Good morning, Tiff! Your Daily Agenda", is split into Schedule, Priorities, a drafted reply to a podcast host's invitation, Decisions needed, and Deadlines.

3. Weather, drafted replies, and calendar conflicts, then the work itself (Zoe Lu and "Sage")

Tech executive and mother Zoe Lu (@leadwithzoe) uses her Dot, Sage, every day (Instagram carousel, Oct 4). Each morning Sage sends a brief with the weather, replies it has already drafted, calendar conflicts, and anything it wants to flag, and then it does most of the tasks on the list itself.

4. Client-proposal issues, conflicts, and missed mail (AI 서대표)

Korean creator AI 서대표 put a Dot on real work for three days with only Gmail, Google Calendar, Drive, and Slack connected (YouTube, Korean). Every morning it summarized the open issues in client proposals, schedule conflicts, and emails that had slipped through. Without being asked, it pointed out that a meeting time in an email didn't match the calendar. Before video meetings it attached his Slack history with the attendees as context. He notes that with other agents he had to build these skills himself; here they worked out of the box.

5. A brief the Dot wrote for itself, read-only by its own rule (Tim Moylan and "dot-face")

Former CTO Tim Moylan (AI: Beyond the Buzz newsletter, Oct 5) connected Gmail, Google Calendar, and Drive, then asked the Dot, dot-face, to get Tim ready for the next day. It went through the calendar, the emails where Tim had promised to do something, the ones Tim had forgotten to answer, and the Drive files Tim had been tagged in, and turned all of it into one list for tomorrow. Then it wrote its own scheduled task, 8 a.m. daily, with rules nobody had asked for: check for newer replies before calling something outstanding, separate confirmed facts from uncertainties, include direct source links, end with the most useful next action, and "only read and summarize; do not send messages to others or change my calendar." Tim's takeaway: a rule a Dot writes for itself is still only an instruction, so watching its computer is how you check.

6. Next steps, blockers, and decisions from a Notion board at 7 a.m. (Snapper AI)

In 3 jobs to give your Dot on day one (YouTube, Oct 7), Snapper AI makes the first job a daily priorities briefing: every morning at 7 a.m. the Dot reviews a Notion board and surfaces next steps, blockers, and the decisions that need attention. Custom rules set which changes it has to check first. For the video, the workflows are triggered by hand rather than waiting for the schedule.

Today's schedule, school included

7. Today's schedule in the morning, tomorrow's in the evening (nicheco)

Developer nicheco (Instagram, Oct 4, Korean) connected Google Calendar and set two check-ins: a briefing on today's schedule every morning, and a note about the next day's events every evening. He says it feels like having a secretary, and he likes that he can watch the screen of the computer the Dot is using.

8. Schedule, to-dos, and follow-up mail (Nicholas Wu)

After about a week, Nicholas Wu (Threads, Traditional Chinese) called the morning routine the most practical part: with his mailbox connected, the Dot sorts out the day's schedule, to-dos, and emails that need a follow-up, and sends different jobs to Chat or Work mode. His complaint is reliability across chats and files: some files wouldn't open, a .md file he had prepared went missing, and finished work didn't always come back cleanly into the original chat. Those failures are covered on Dots not showing / cloud computer unavailable.

9. A university course site, digested at 8 a.m. and 8 p.m. (@simon_vaerion_roc)

A National Taiwan University student, @simon_vaerion_roc (Threads, Oct 5), skipped building a connector for NTUcool, the university's course system. Instead he let the Dot's cloud computer sign in to it. The Dot now organizes everything there twice a day, in the morning and at 8 p.m., reports what matters, and messages him when a new announcement or assignment appears. Asked "when is the midterm?", it listed every exam with its details and offered to remind him nearer the date.

10. Calendar, Trello, and Gmail at 6 a.m., AI news at 7, school handouts folded in (Makari)

Japanese blogger Makari (note.com, Oct 7) asked the Dot to check Google Calendar, Trello, and Gmail and send the day's plan at 6 a.m. every morning, so the work spread across those apps no longer has to be opened one by one. A second daily task brings the latest AI news at 7 a.m. on the topics Makari picked. For the child's school mail, the Dot saves the PDF handouts to a Google Drive folder for elementary-school handouts and adds what to bring and prepare to the morning notice. Makari still checks the original emails and handouts.

The inbox first thing

11. A 6 a.m. inbox summary, and one send that stalled (Onde eu Clico and "James")

Brazilian channel Onde eu Clico (YouTube, Portuguese) runs a daily 6 a.m. job: the Dot, James, checks both the channel inbox and his personal inbox, summarizes everything that arrived since 6 p.m., and asks whether he wants it to reply or block spam. That part worked every day. When he asked James to send a company an invoice email with a PDF attached to request a refund, it stalled repeatedly and never confirmed the send, so he sent it himself.

12. Inbox every morning, Teams all day (Jeff Hall and "Hank")

Jeff Hall has his Dot, Hank, process his inbox each morning and watch his Microsoft Teams messages, so the work he runs in Codex keeps moving. The part he doesn't love: when Hank instructs other agents, those agents don't get his plugins. Teams setup is on Dots + Microsoft Teams.

13. It read his email before he gave it a job (Build Alone and "Scout")

The creator behind Build Alone found that his new Dot, Scout, had already gone through his email before he gave it a single task. He then gave Scout the same 6 a.m. job his Claude Code routine had run every morning since August and compared what came back. His closing rule for any agent that works while you sleep: give it the smallest key that does the job.

14. An interactive HTML brief styled like Pulse (u/eflol)

On r/ChatGPT, u/eflol wrote: "I really like the ability of my dot to give me morning brief in a html interactive format", then asked for a version that looks like OpenAI's earlier Pulse. Worth trying when a chat message is too flat to scan.

15. A weekday 8 a.m. mail summary in three buckets, newsletters left out (Chaen)

Chaen, head of the Japanese AI training company Digirise, runs a weekday-morning mail summary on the same Dot that prepares sales-call reports (Japanese, Oct 2). The rule for any recurring job: decide the trigger, where the result goes, and what to leave out. Here that means a fixed weekday-morning time, delivery to the Dot chat, and no newsletters or automatic notifications. The example ask sorts mail into needs a reply, needs action today, and FYI only, attaches the original email to each item, runs at 8 a.m. Japan time for four weeks, and marks anything unclear as "needs checking" instead of guessing.

Things it noticed overnight and raised in the morning

16. A visa application that had gone quiet for 8 days (Igor Pogany, The AI Advantage)

In his first 24 hours, Igor of The AI Advantage had a Dot that used his connected plugins overnight to look for work. At 8:00 a.m. it raised two things on its own: an upcoming US trip, and an O-1 visa application with no status update in eight days, with a suggestion to follow up with his assistant.

17. A reminder to cut ad spend, with the meeting transcript attached (Andrew Southworth)

Andrew Southworth (Threads, Sep 30) had a calendar reminder to reduce the ad spend on a campaign. His Dot cross-checked it against his meeting transcripts and messaged him that morning, unprompted, to make sure he followed through, with a link to the September 24 call so he could check the details.

18. The DevDay QR code, sent that morning (Flavio Adamo and "Marvin")

Flavio Adamo had early access. His Dot, Marvin, picked up all of his existing ChatGPT connections, "so there's basically zero setup". It helps him with customers and with organizing his day, and on DevDay morning it reminded him about the event and sent him the QR code to get in.

19. A figure to recheck before the morning meeting, then the all-clear (AI Never Sleep and "네슬")

The Korean consultancy AI Never Sleep named its Dot 네슬 and connected Gmail and Calendar (blog, Oct 5). Without being asked, 네슬 posted that one number in the material for the next morning's meeting needed checking. The day after, it posted again: the missing data had been updated and the issue was resolved. How 네슬 handles drafts and sends in Slack is on the Slack assistant page.

Ideas and news on a schedule

20. A video idea every morning (Benjamín Cordero)

After 72 hours with a Dot, Spanish-language creator Benjamín Cordero says it prints him a video idea every morning, prepared a meeting brief without being asked, and makes thumbnails with Higgsfield. His verdict is mixed: he says it also falls short in the area OpenAI promised most.

21. "Felt useless" until it got a recurring job (KefirAI)

The open-ended demos KefirAI tried first felt useless. Giving the Dot a specific, recurring job is what made it useful: a YouTube brief every morning and a weekly competitor report, plus a Blender animation built on its cloud computer.

22. A daily news briefing among the everyday admin (Kol Tregaskes)

Kol Tregaskes asked people to show the everyday stuff, not flight bookings. His Dot handles parcel tracking, failed-payment alerts, receipts, spending records, spreadsheet fixes, annual-leave maths, routine updates, and a daily news briefing. Next he wants weekly grocery top-ups based on cupboard stock; that part isn't running yet.

36. Morning news patrol with zero wait (@shuntabi6)

旬之旅人 @shuntabi6 (Threads, Traditional Chinese) got Dots test access and handed over a daily morning news patrol that used to take about 20 minutes of manual work. Waiting time is now 0: he reads the result in the morning. (The same post's Excel research timing is on Google Drive.)

37. Latest tech news compiled as HTML (@thaqifdev)

@thaqifdev (Threads, Malay) asked his Dot to fetch the latest tech news, compile it into HTML, and send it to him so he can catch up without opening a stack of tabs.

Overnight work, morning report

23. A software bug and a data issue, fixed by morning (Kurt Bell)

Kurt Bell went to bed with a software bug and a data issue and woke up to both fixed. His Dot tested and verified the fixes and left him a morning report. It also found and tested a possible product improvement but didn't deploy it without his approval, which impressed him most.

24. The bedtime instruction that sets up the 8-hour report (@koh_kira)

Japanese poster @koh_kira (Threads, Oct 2) shared the exact message he leaves before bed. In English: "I'm going to sleep for 8 hours. Within what I've already asked for and approved, keep moving the remaining tasks in each session on your own. Resume sessions that stopped at a goal or a scheduled check, switch to another approach if you get stuck, set aside anything waiting on my input and carry on with other work, notify me only about important changes, and after 8 hours report what's done, what's left, and why anything is on hold." He wakes up to the work finished.

25. "Surprise me by morning" (Himanshu Jha and "Buddy")

Himanshu Jha told his Dot to surprise him by morning, with three rules: spend nothing, leave existing projects alone, and work through the night. By 9 a.m. Buddy had published three new GitHub projects, opened an independently audited draft pull request, passed 193 targeted tests, and sent three developer-relations applications, one of which came back with a take-home invitation. Partway through, the cloud workspace reset; Buddy rebuilt the lost files, reran the checks, and saved everything again. He handled sign-ins and permission approvals himself.

26. A draft plan and a diagram after 8 hours alone (Ren Gaku and "Ciel")

In a four-day work trial (Japanese), Ren Gaku left his Dot, Ciel, on an eight-hour task overnight. By morning it had delivered a draft plan, an explanatory diagram, and a short report. He also lists what to watch: usage allowance, memory, approvals, and where the data ends up.

27. A 60-page deck on the phone by morning (顏世倫, @yenshilun58)

顏世倫 (@yenshilun58) (Threads, Traditional Chinese, Oct 1) phoned the Dot late at night with a presentation to build. It kept saying it was still working on it, then suggested going to sleep and promised to report when it was done. By morning a 60-page deck was on the phone, and the job had taken only 23 minutes. Before building the slides, the Dot had checked the class time on the calendar, the official website, and the course site for the Oct 2 Taoyuan session, and the content held up instead of being stitched together.

28. A creative side project of its own every night (Adrian C. Murray and "Anuki")

Adrian C. Murray (Threads, Oct 5) told the Dot, Anuki, to fit in a personal side project with full creative freedom between the tasks it had running overnight. By morning there was a short, relaxing piece Anuki had made in the middle of the night. Adrian plans to make it a nightly habit and let Anuki build up a library of its own projects.

Evening and catch-up versions

29. A nightly summary instead of a morning one (Ekello Harrid and "Butch")

In his first 48 hours, Ekello Harrid had his Dot, Butch, repair his daily audio report, work on a video edit overnight, and set up a nightly summary and wiki workflow. Butch also reminded him, on its own, to call the vet about his dog Daisy.

30. Two hours late, caught up during a 42-minute dog walk (u/Ice2jc and "Pip")

On r/ChatGPT, u/Ice2jc overslept by two hours on the first day of a new month and quarter. During a 42-minute dog walk with the Dot, Pip, in their ear, it scheduled all of the month's tasks, talked through priorities against their quarterly goals and their business coach's tasks, kept an eye on one chat collecting prospect contact details and another doing deep research, and then helped write a prospect script. By the end of the walk they were only 30 minutes behind.

Between briefs: an hourly check that stays quiet

31. An hourly heartbeat, and the only app allowed through Do Not Disturb (Riley Brown and "Bluey")

After a week of daily use, Riley Brown showed two scheduled jobs on his Dot, Bluey, in a video posted on 10 October. The first is a 9 a.m. brief that reads all his connected apps and opens with the most important item. The second he calls a heartbeat: every hour Bluey checks everything related to his content work, says nothing if there is nothing he needs to know, and messages him when something matters. He runs it hourly and says every 30 minutes is possible, but he didn't need it more often. His iPhone is on Do Not Disturb most of the day, so he set ChatGPT as the only app whose notifications get through, and told Bluey exactly which kinds of things deserve a message. What reaches him now is a short note such as a marketing task that has to be finished within the hour. asi.tokyo published a Japanese transcript translation. His earlier 45-minute walk call is case 1 on voice calls.

A version to copy:

Every hour from [08:00] to [20:00] ([IANA time zone]), check [mail, Slack, calendar and other apps]. If nothing meets these conditions, send nothing: [a reply I owe is more than a day late; a meeting moved; something is due today]. If something does, send one message with the item, why it matters now, and the link. Keep a one-line log of each check in [Space page] so I can see it ran.

Personal digests that replaced an old setup

32. Good news for Ukraine, AI updates, and what's on in Lviv (Viktor Malinovskyi and "Byte")

Viktor Malinovskyi (LinkedIn, Oct 2) had been using his Dot, Byte, for three days when he set up a personal morning brief with three parts: good news for Ukraine, an idea he credits to Maryna Mushtai; AI updates; and theatre, exhibitions, and events in Lviv that fit his interests. What he wanted was "something personal to wake up to, without scrolling through three feeds." Next he wants to add what he calls a creative kick: a tiny challenge, or one concrete step toward something he keeps putting off, in place of another plain reminder. He also moved his weekly industry digest to the Dot; that one is on the research watch page, and his inbox clean-up is case 24 on email triage.

33. A research report ready every morning, instead of the system he was building himself (ludicmind and "Alfred")

Japanese blogger ludicmind (note, Oct 2) named his Dot Alfred (アルフレッド) and treats it as a butler. After one day he wrote that a problem he'd had for years, spending hours gathering information, was close to solved: a report he asked for is brought up to date every morning before he wakes. Its contents include sections on cancer treatment and dementia; he points out that neither he nor anyone around him has these conditions, he just wants to keep up with the latest work. He can hand over three or four requests before bed and find them finished in the morning, and when he wants something changed, it changes straight away. He had been building the same kind of system himself on Google Cloud with Gemini and Hermes Agent, and says he no longer needs it, although what the Dot costs after the first month might change that. Alfred also watches his mail, Slack, and calendar and tells him things like "that event is going ahead as planned" or "they've replied about that, and they'd like you to do this." When he asked when to use Slack instead of the ChatGPT app, it suggested one Slack thread per project for short exchanges and progress checks, and the app for long discussions and voice.

34. One page a scheduled task rewrites: plan, news, ideas, and backlog (Brian Sunter)

Brian Sunter (Threads, Oct 9) liked the feed and ideas features in Muse, so he rebuilt them with his Dot: a recurring task updates a page in Space. The page has four parts. A daily plan comes from his goals pages and Todoist. A news brief pulls from X, Hacker News, and other sites. An ideas section is where the Dot looks through his conversation history, tasks, and pages for things it could help with. The last part is an inbox and backlog: a daily scratchpad that is organized automatically at the end of the day, plus a backlog of tasks and notes he hasn't sorted yet.

Priorities from Slack and calendar first thing

35. Top priorities pulled from Slack and calendar (Ellen Chen / Lola)

Software engineer Ellen Chen (YouTube, "How Codex and Dots Save Me Hours Every Week") named her Dot Lola. Each morning Lola pulls connected Slack, calendar, and other apps into a short list of top priorities for the day. She keeps a home-base todo in ChatGPT Space pages the Dot can edit: status, linked PRs, where the ask came from (Slack thread or meeting notes), and when it was raised. When she gets pinged on Slack, the Space todo updates. From a row she can tell Lola to start the work (for example finishing a CSV export), and Lola spins a Codex session on the local or cloud computer.

Security camera events every morning

38. A morning report from security cameras across several sites (CXCarroll)

CXCarroll (X thread, 12 Oct 2026) uses a Dot as a power-user setup: slower and careful with permissions, strong at browser and computer use, and comfortable next to the Codex desktop app. The concrete morning job: the Dot reviews security camera events from multiple sites every morning and writes a report. He says it is powerful if you put in the time to customize it. He did not publish the report template or name the camera software.

Moving a ChatGPT chief-of-staff routine to the Dot

On Oct 13 Derrick Choi (@derrickcchoi) posted: "Your dot should take over your existing chief of staff automation in ChatGPT." Most replies were complaints or wishes; three described what happened when they tried it.

39. A week as chief of staff, first in desktop Codex, then in Work Codex (Edward Fariñas)

Edward Fariñas (@edwardfarinas) had used his Dot for exactly this over the past week, first in the desktop Codex app and more recently in Work Codex, and said it had been "really good" for him.

40. The Dot directs an existing admin agent, and follows instructions less exactly (Peter Swartz)

Peter Swartz (@peter_swartz) kept his existing personal admin agent in chat, with its own rules, boundaries and automations, and uses the Dot to direct it instead of replacing it. His verdict: the Dot doesn't always follow his instructions as exactly as the admin agent does; "still too loose".

41. It kept forgetting, so the reminding went elsewhere (Ravin Sharma)

Ravin Sharma (@ravinsharma7) found the Dot kept forgetting past things and got tired of reminding it, so he found it easier to hand the reminding itself to something else.

Two tips from the same thread, both aimed at a brief that talks too much: Graham (@Graham_Tonkin) suggests telling the Dot to include only new and relevant information, and only during your working hours; Zeinaldo Arrevedo (@ZArrevedo) suggests asking for a "10/10" proactivity level when the Dot is too quiet. The pattern across all three: keep a working routine as the source of rules if you have one (Peter's setup), and move it over only once the Dot holds the context it needs (Ravin's problem).

One overnight job, and only the urgent items in the morning

42. Overnight messages sorted into urgent and later, replies drafted but never sent (けんすみ, @kensumi_ai)

けんすみ (@kensumi_ai) (13 Oct, Japanese), who edits overseas AI case studies, was tired of client messages piling up overnight and the morning disappearing into reading them. So their Dot now checks what arrives during the night, and the urgent items are ready to handle from email first thing. There is one fixed rule: it always asks before sending any email. In a follow-up post they say they tried a setup N01ennn had described as the way Altman uses his Dot: one Dot with a single overnight job. It reads the mail, calendar, Slack messages and DMs that came in overnight, splits them into urgent and can-wait, drafts replies without sending anything, and sends one message in the morning with only the urgent items. If you try it, keep that Dot to this one job, and put the no-sending rule in its rules rather than repeating it in every ask.

Copyable asks from these cases

Every weekday at 7:30 [IANA time zone], check my email, Slack, and calendar and list only the five things I need to decide today, each with its source link. Also keep a running list of replies I promised but haven't sent, replies I'm waiting on, and anything stalled for more than three days.

Every morning at 7:00 [IANA], send me a personal agenda with these sections: Schedule, Priorities, Drafted replies (don't send them), Decisions needed, and Deadlines.

Every day at 8:00 and 20:00 [IANA], check [course site or portal] and tell me about new announcements, assignments, and exam dates. Message me straight away if a new assignment is due within 48 hours.

Every morning at 6:00 [IANA], summarize everything that arrived in [inbox 1] and [inbox 2] since 18:00 yesterday. For each message, ask whether I want a reply drafted or the sender blocked. Don't send anything.

I'm going to sleep for 8 hours. Within what I've already approved, keep moving the open tasks. If you get stuck, try another approach; set aside anything that needs my input. Notify me only about important changes, and at [time] report what's done, what's left, and why anything is on hold.

Build today's brief as one interactive HTML page: a card each for meetings, emails that need my reply, and decisions waiting on me, every item with its source link and collapsed by default.

Every day at 8:00 [IANA], send me a concise briefing based on my connected email and calendar. Cover my top priorities, important outstanding decisions and commitments, meaningful updates, and today's schedule with a short look ahead to tomorrow. Check for newer replies and resolutions before calling something outstanding, distinguish confirmed facts from uncertainties, include direct source links, and end with the most useful next action. Only read and summarize; do not send messages to others or change my calendar.

Every weekday at 8:00 [IANA] for the next four weeks, check my connected mail and sort it into: needs a reply, needs action today, and FYI only. Attach the original email to each item, write "needs checking" instead of guessing, and leave out newsletters and automatic notifications.

When [school] emails a handout, save the PDF to my [school handouts] Drive folder and add anything to bring or prepare to my morning notice.

A version built from cases 32 to 34:

Create a Space page called [My morning] and update it every day at [07:00] ([IANA time zone]) until [end date]. Keep these sections: Today (from my calendar and [task app]); News (up to five items from [sources], each with its link, nothing you have already reported); Ideas (up to three things you could do for me, based on our recent conversations and my pages); Backlog (sort what I added to the scratchpad yesterday). Don't send or change anything outside this page. Confirm the saved schedule.

  • Priorities from Slack and calendar (from Ellen Chen / Lola): Each weekday morning, from my connected Slack and Google Calendar (and any other apps I named), give me a short top-priorities list. For each item include why it is on the list, the Slack or calendar source link, and whether you can start it or need a decision from me. Keep a matching todo page in Space updated when new Slack pings arrive. Do not send messages or change calendar events without asking.

After it's scheduled: what went wrong

The setups above show what a good brief looks like on the day it's set up. The reports below cover the next stage, when the brief has been running for a while and you've stopped reading it closely. They come from Substack and blog posts, a YouTube description, OpenAI Community threads and openai/codex GitHub issues in early October 2026, grouped by where things went wrong: whether the brief was true, a schedule the owner couldn't fully see, change or stop from the chat, triggers that stopped firing without an error, and a Dot that went on a break. A brief that looks finished is not proof that it ran, read every source or got its facts right.

Is the brief true?

  • Label what the brief didn't cover. Lee Shand (Substack Wired Differently, Oct 6) asked the Dot, Purple, for a draft of the day's Obsidian daily note. It added to the existing note without overwriting the entries already there and marked its own contribution as a partial day, through about 11 a.m. Shand calls that the useful part: "A convincing summary of half the day is still half the day." There's also a 6 a.m. refresh of a To-do Page that carries unfinished work forward. One item described an outcome more confidently than the conversation behind it justified, and Shand wants every item to link back to whatever made it a task. The other catch: the cloud browser couldn't reliably open the Substack pages Shand wanted read, the signed-in local Chrome could, and that local route only works while the PC is on with the ChatGPT app open (post).
  • Separate confirmed from uncertain. Tim Moylan's Dot wrote its own 8 a.m. task with these rules: check for newer replies before calling something outstanding, distinguish confirmed facts from uncertainties, include source links, and only read and summarize (AI: Beyond the Buzz, Oct 5).
  • Write "needs checking" instead of guessing. Chaen's weekday 8 a.m. mail summary gives the Japan time zone and a four-week end date, attaches the original email to each item, marks anything unclear as 要確認 ("needs checking") and leaves out newsletters and automatic notifications (Digirise, Oct 2).
  • Flag missing sources. Snapper AI's day-one video makes a 7 a.m. Notion priorities brief the first job. Across its three demo jobs, the description notes, the Dot flags incomplete source access and missing timestamps rather than filling in the gaps. The demo runs were triggered by hand, not by the schedule (YouTube, Oct 7).

A schedule you can't fully see or change from the chat

  • The Dot's own edit was refused; the website edit worked. On Oct 6, OKJOIZJ authorized the Dot to change the title and instructions of an existing scheduled task. The Dot's update call returned "You cannot modify this task." Eleven minutes later the same edit worked in ChatGPT on the web (Dot profile → Recent activity → task editor), and the time zone, recurrence and end date were kept (openai/codex#51285).
  • The Dot couldn't see every scheduled task. markifur's Dot couldn't access all of their existing scheduled tasks, while a separate ChatGPT Work conversation listed them with instructions, schedules and paused/enabled status. markifur didn't want to recreate the tasks and risk duplicate runs. Daareek replied that recreating is one of the worst fixes, because you can end up with two valid jobs sending duplicate alerts (OpenAI Community, Oct 7).
  • No single view of what's scheduled. ANTVirGEO found that Recent activity mixed individual checks with scheduled activity. With several jobs running, including a scheduled morning summary, they had to ask in chat what was running. Their request: schedules shown separately, with time zone, next run and run history (#51214, Oct 6).
  • "Stop everything" is not one button. stream727 asked their coordinating Dot to stop all related work. Over the next 15 minutes it reported some stop requests cancelled, no direct force-stop available, and stop replies from 2 of 9 workers. Then stream727 stopped the work by hand, and the Dot corrected its earlier claim that it had done so (#52209, Oct 9 JST, Japanese). This matches OpenAI's own controls page: Pause stops the current main task but doesn't cancel future scheduled runs. Disable or delete the brief under Scheduled.

Triggers that go quiet

  • A second Gmail account stopped the new-mail trigger. Daareek (ChatGPT Business, Europe/Warsaw) had a Dot task that woke on new Gmail. It stopped firing right after a second Gmail account was connected. The Dot could still read both inboxes when asked directly, and the task editor had no field for which account the trigger belongs to (OpenAI Community, Oct 7–8).
  • "Accepted" is not "ran". lucas27's custom MCP events got HTTP 200 from OpenAI's callback, but the Dot never ran. Asked about the task, the Dot reported it enabled with no last or next run time. toppk's similar setup worked, with a delay. Daareek's point: a 200 only proves the event was received, and blindly recreating the task can create duplicate subscriptions (OpenAI Community, Oct 8–9).

When nobody is watching

  • A break with no reset time. On Oct 6, ivg-design's Pro Dot kept answering "Your dot is on a break… Check back in a bit!" from about 18:50 to 20:30 EDT, with no meter and no reset time (#51540). A brief due in that window would simply not arrive. More on usage is on updates, and on overnight runs that hit a pause on project follow-up.

Prompts that guard against these problems

Adjust the times, names and sources to your setup before you use them.

Honest brief

Every weekday at [time] [IANA time zone], send my morning brief. Start with one line: the time window it covers, which sources you read, and any source you couldn't open. Mark each item "confirmed" or "needs checking", and check for newer replies before calling anything outstanding. Link every item to the email, message or file it came from. Only read and summarize. Don't send, archive or change my calendar.

Schedule receipt

After you create or change my morning-brief task, reply with its exact title, time and IANA time zone, days, end date, where results go, and the next run time. If an edit fails, quote the error and tell me to make the change in the task editor on the ChatGPT website instead of making a new task.

Check before you create

Before setting up a new daily brief, list every scheduled task you can see with its title, time, and whether it's enabled. Tell me if you think there are tasks you can't see. Don't recreate or duplicate an existing brief. Ask me which one to keep.

Gap line for a missed run

Begin every brief with "Last brief: [date and time]". If more than one scheduled run has passed since then, or a trigger such as new mail should have woken you and didn't, say so first.

Read now, send later

In the scheduled run, only read and prepare. Put any reply you'd send into a "Drafts waiting for me" list with the recipient and a link to the thread. I'll approve or send them in a live chat. Don't try to send from the scheduled run.

Stop, then read the state back

Stop my morning brief: disable the scheduled task named [title], then list every scheduled task and delegated task you started for me, each with its current state. Don't say something is stopped unless you've read its state back. Tell me which ones I have to stop myself under Scheduled or Activity.

Related

Copy this task brief

How to get a ChatGPT Dot morning brief from calendar and Gmail, how to schedule it, where it gets stuck, and real daily-digest setups: overnight work reports, five decisions a day, and briefs the Dot wrote for itself.
Download Markdown ↓

Sources & further reading