How to set up a ChatGPT Dots research watch: competitor, price and news alerts, with 50 real setups (OpenAI Dots)
What a ChatGPT Dot (OpenAI Dots) watch is good for, seven setup steps (sources, a baseline, what counts as a change, a real end date, where alerts go) and eight places watches get stuck, with fixes. 50 real setups, from 30 competitor sites and hourly rounds over 4,891 inns to price and news alerts.
The short version: what a Dot can watch for you, how to set it up, where watches get stuck
Is a research watch worth handing to a Dot?
Yes, when you can name the sources and say what counts as a change. In the setups below, a Dot did four things well. First, it went back to a fixed set of pages on a schedule and reported what moved, with links: about 30 competitor sites for Aqsh, the Cloudflare blog feed for George Liu, three release pages for Joe Rice-Jones, and a camera listing on Ozon for Georgy Rivera, where the first pass also caught a customs duty he had missed. Second, it worked through long lists faster than a person could: えい's hourly rounds covered 4,891 inns across seven prefectures, and HinaKira's Dot collected 1,117 posts from four advice sites, each with a summary and a source. Third, it kept searching while its owner's computer was off, because it runs on its own cloud computer; Rohan's hourly lead search files promising matches into his own app. Fourth, some of the best catches were never asked for: a second flight delay for VeitB, a stopped Make.com automation for Nikola, and a campsite rule that clashed with わっしー's packing list, all found in apps and files the Dot could already read. It gets stuck when the material never reaches it, when the saved schedule isn't the one you asked for, when a watch goes silent with no error, when a source is blocked or logged out, and when an alert repeats old news or carries a slightly wrong figure. It suits people who will open the first few reports, check the links, and keep the decision for themselves; a good watch usually ends with a shortlist, not a finished product.
Setup steps
- Write down the decision the watch supports and the exact sources: URLs, an RSS feed, a Slack channel, a search query or a connected app (getting started; setup guides on the integrations page). Keep one job in one place, as Seowoo Han does with one Slack channel per research topic.
- Ask for one baseline report first and open every link in it. Before the first round, have the Dot say what it received and whether it could open every file; えい's watch sat at zero inns for two hours because the handoff never reached the Dot.
- Say what counts as a change, what to ignore, and what to do when a page can't be read. Aqsh's brief and えい's brief both ask for "can't see (reason)" to be listed apart from "no change", so a quiet report means the sources really were checked.
- Say what every alert must carry and what not to repeat: what changed, the source, the date, and why it matters, as in Viktor Malinovskyi's weekly digest, with "no recycled news". Jayprakash Suthar's six-hourly watch sent 2 repeats out of 8 because his ask never ruled them out.
- Make it recurring only after that. OpenAI's tasks and memory guide asks for four things: what to check, when to run (with the time zone and any end date), which changes deserve a notification, and where to deliver the results. A Dot can decide on its own when to follow up, so ask for a fixed schedule when the timing matters (Get started with your dot). Have it confirm the saved schedule, then check the end date yourself: Ramanpal's task named a deadline in its text while the schedule said End repeat: Never. Review, pause or edit it under Scheduled or in the Dot's profile (Getting started with your dot); stopping a run in progress and cancelling the schedule are separate actions.
- For a watch that should start from an event, such as a new Slack message or a change in your own app, ask the Dot which events it can follow. Connecting an app doesn't create a watch by itself (tasks and memory). Alexander Embiricos forwards a Slack message and writes "Keep an eye on this", and Jaime Medina's app sends MCP events that his Dot turns into a notification.
- Decide where findings go and who acts on them before the first run. Rohan's leads land in his own app and only promising ones reach his phone; Adrian's Dot waits for a teammate's approval before it updates the internal Compete Corner site. Proactive research between conversations doesn't send messages, change connected apps or control a browser, so acting on a finding still goes through your approvals (Dots privacy, security, and safety FAQs).
Where it gets stuck, and what worked
- The watch says it's on, but nothing arrives. anotb's Gmail event watch missed an email that a later lookup found, and Michael M says things came and went without a single message. What worked: a one-line heartbeat on every round, a test event you know should match, and the check order in "When a watch goes quiet" below.
- The saved schedule isn't the one you think. Ramanpal's task had no end date, and Loïc Frissard's 8:00 watch didn't show in the Scheduled tab even though Digi said it was saved; it was listed in the Dot's profile. What worked: open the saved task and check the time zone and end date, and look in the Dot's profile before you set the same watch up a second time.
- The material never reached the Dot. えい's Dot had said at the start that it couldn't open the handoff, and the CSV was still sitting in the input box. What worked: resending the material as URLs, and asking for progress in counts (checked, read in full, only reached, can't see).
- The source is blocked or logged out. X blocked Victor Zhang's Dot from reading one account, so it switched to two third-party trackers; neco.'s 7:00 news pull failed whenever X was logged out; HinaKira's Dot couldn't fetch Yahoo! Chiebukuro. What worked: ask the Dot to name the source it is really watching, and to report a login failure in that round instead of skipping it.
- Alerts repeat old news. Jayprakash got 2 repeats in 8 notifications. What worked: say "don't repeat anything already reported", merge reposts into one item, and put a date on every source, which was the gap ekcheungAI noticed.
- A figure or fact is slightly off. HinaKira's plan comparison marked ChatGPT's yen price "unconfirmed" when it was on the official pricing page, わっしー's morning summary had one wrong detail number, and Berzaf's verification step failed three of five job listings, including the top match. What worked: check the first runs yourself, ask the Dot to recheck a surprising finding at the source, as Joe Rice-Jones did with an odd version number, and check anything you'll quote against the original.
- The count answers the wrong question. HinaKira's Dot leaned towards variety until he said duplicates were fine for a ranking, and the relationship set grew from 1,117 to 1,392 posts. What worked: say what the numbers will be used for before it collects.
- Event data or overnight work goes missing. rokrokss's runs from a custom MCP server never received the event's data, Daareek's new-mail trigger stopped after a second Gmail account was connected, and bentleyjohnson's overnight watches over worker chats keep failing. What worked: a read tool the Dot calls on every event to fetch the data itself (rokrokss), saying which account a watch should follow and rebuilding it if it stays silent, and, for overnight work across worker chats, the setups on Dots and Codex tasks.
What it can do today, and what it can't yet
What it can do today:
- Revisit a set list of pages on a schedule and report changes with the page, the date and the link.
- Watch prices and listings and tell you only when a threshold or a must-have is met.
- Work through thousands of items in hourly rounds and report progress in counts.
- Turn an RSS feed, a blog or a trending list into a daily briefing or a shortlist you choose from.
- Search for leads or jobs every hour while your own computer is off.
- Respond to events from apps that support event monitoring.
- Transcribe an audio-only source on its own computer, or read a long filing in full.
- Bring up things it noticed in apps you've already connected, without being asked.
What it can't do yet:
- Guarantee that every event or new email triggers an alert.
- Let you choose, in the task editor, which of two accounts from the same app an event trigger follows.
- Read every site; some block it or need you to sign in.
- Connect a service's APIs just because it signed in to that service in its browser, as Mark Nguyen found with Google.
- Replace your own check before you quote a finding, publish, or contact anyone.
A message to start with
I want to watch [sources: URLs, feed, channel or connected app] for [decision I need to make]. First tell me what you received and whether you can open every source. Then send one baseline report with a link for each item. After I've checked it, check every [frequency, time and time zone] until [end date] and put the end date in the schedule itself. Count as a change only [what counts]; ignore [what to ignore]. For each change, give what changed, the source link, the date it was published and why it matters to my decision, and don't repeat anything you've already reported. List any source you couldn't read, with the reason, separately from "no change". On quiet rounds, send one line with the time you checked and how many sources you read. Send results to [destination]. Don't contact anyone, post, buy or sign up for anything. Confirm the saved schedule.
Quick answers
Can a ChatGPT Dot watch competitors, prices or news for me?
Yes, as a scheduled task that reports when something changes. Aqsh set a Dot to visit about 30 competitor websites and report services, pricing, conditions and announcements; Julian Goldie has his Dot watch Search Console pages sitting in positions 8 to 20; 丹妮tech set one to watch flight and hotel prices on a repeating schedule; George Liu's Dot turned the Cloudflare blog RSS feed into a daily Birthday Week briefing; and えい ran hourly rounds over a list of 4,891 Kyushu inns until 19:30.
How do I set one up?
Give the Dot the four things OpenAI's tasks and memory guide asks for: what to check, when to run (with time zone and end date), which changes deserve a notification, and where to send the results. Ask for one baseline report first, open its links, and only then make it recurring and have the Dot confirm the saved schedule. You can pause or edit it later under Scheduled (Getting started with your dot); ChatGPT Dots features shows how schedules sit next to calls, apps and custom rules.
Can a watch start from Slack or email instead of a clock?
Yes, when the connected service supports event monitoring, but connecting an app doesn't create a watch by itself (tasks and memory). Alexander Embiricos forwards an important Slack message to his Dot and writes "Keep an eye on this", and Seowoo Han keeps one Slack channel per research topic. Some catches need no setup at all: Antonie Huang's Dot told him his app's new version was live, and VeitB's Dot pinged twice about a delayed flight until the rebooking really was needed. More trip watches are on travel planning.
Why did my watch go quiet?
A watch listed as on doesn't prove the input reached the Dot. anotb's Gmail event watch missed an email that a lookup later found, and Daareek's new-mail trigger stopped right after a second Gmail account was connected. Check Scheduled, then the last run time, then send a test event, and ask for a one-line heartbeat on quiet rounds; the full check order is in "When a watch goes quiet" below. If overnight work runs through separate worker chats, as bentleyjohnson's does, see Dots and Codex tasks.
Which plan and apps do I need?
A Dot comes with Pro ($100, $200 or $500 tiers) outside the EEA, UK and Switzerland, with Business Premium in any supported region, and with Enterprise once an admin switches it on (How to get ChatGPT Dots; in Europe, see Dots in the EU and UK). Most watches here read Gmail, Slack or public pages in the Dot's own browser; other connections are in the integrations hub.
Real examples, by what they watch
Competitors, markets, and search rankings
Aqsh, a Japanese web agency (company blog, 30 September 2026). Aqsh set its Dot to visit about 30 competitor websites on a schedule and send back a report on services, pricing, conditions, and new announcements. They write that they have only finished the setup so far and haven't judged the reports' coverage yet. Their brief asks the Dot to report pages it couldn't read, such as a login wall, a moved page, or blocked access, instead of folding them into "no change". Next they plan to point the same kind of watch at subsidy and grant calls and at municipal tenders in their line of work, such as web production, system development, and PR.
麥克斯斯.AI, @mexx1999.ai (Threads, Traditional Chinese, 6 October 2026). He ran a market test for his team with Dots: the Dot tracks competitors' price changes and product-range adjustments around the clock and flags market trends as they show up. The team used to spend close to 10 hours a week compiling that data by hand; he says the time saved is enough to run several more campaigns.
KefirAI (YouTube). After open-ended demos felt useless, KefirAI gave his Dot specific recurring jobs, and a weekly competitor report was one of them, alongside a morning YouTube brief. He shows the results on screen and says a specific, repeating job is where the Dot became useful.
Jordan Rafealov (YouTube, 2 October 2026). In a side-by-side test video against Meta Muse, one of the three business tasks was a live competitor dashboard built from three YouTube channels that updates itself every morning at 7:30. His Dot got the same prompt, and its dashboard is shown from 12:43.
Seowoo Han, @swhan0329_ (Threads, Korean, 1 October 2026). Seowoo connected Slack and told the Dot, in plain Korean, "research the market every day and post a report to this channel." The screenshot shows the result in #news at 09:56 KST: an AI, computer vision, and physical AI briefing with five items, each with details and links. Seowoo keeps one channel per research topic so each job stays easy to manage.
Julian Goldie (YouTube, 7 October 2026). Julian puts his Dot on nine SEO jobs, and several are watches: Search Console pages sitting in positions 8 to 20 as quick wins, a decay report that finds pages losing traffic and refreshes them, Ahrefs keyword and share-of-voice research on competitors, and a lost-clicks report turned into a clickable dashboard. The last chapter runs the whole read, write, and publish loop on autopilot and shows where it goes wrong.
Mark Nguyen, Dot "Toby" (The Slide Factory blog, 2 October 2026). Mark, who runs a web agency, wanted Toby to watch two client sites, a law firm and a medical practice, for trends, opportunities and qualified leads. The first route, through the GSC Wizard tool, failed because that account had no active subscription. He then had Toby use its browser: after a Google sign-in and a device approval, it reached both clients' Google Analytics 4 and Search Console data. They scheduled one combined daily report to his private Slack for about 8 a.m. Pacific, with seven-day and 28-day comparisons, and with findings checked before they are presented as opportunities. Through his agency's own SEO tool, connected over MCP, Toby also crawled 44 pages of the law firm's site and 111 of the medical practice's. At the end of the first day the first report had not run yet, and he writes that there is no basis yet to claim better SEO results. Signing into Google in the browser also did not connect Google's APIs to his SEO service; that step stayed with him.
Ramanpal Singh, Promptslove, Dot "Jamie" (blog, 30 September 2026, updated in October). Ramanpal runs Promptslove's link outreach through Jamie and found it saved as an hourly task called "Promptslove Link Building". The instructions asked for three legitimate, verified new external links by about 18:51 IST on 3 October, and told the Dot to check replies and receipts, keep pending or owned links out of the count, and report only meaningful changes. At 19:06 IST on 30 September the record showed 13 reported outreach or submission actions and zero of three live links. That evening Jamie reported a first live listing in Full Stack Journalism's tool directory, and Ramanpal opened the public record himself: the link was there, marked nofollow, with editorial review still unconfirmed, so the count became 1/3. Along the way Jamie hit a verification block at Future Tools and moved on, logged a SaaSHub listing as pending (the site quoted up to 32 days), and when one form showed no confirmation after a single Send, it didn't retry, to avoid a duplicate. One detail he caught in the schedule: the 3 October deadline was only in the instructions, while the task itself said End repeat: Never.
Adrian, competitive research at OpenAI (DevDay 2026 session, 7 October 2026). In OpenAI's session How OpenAI Puts ChatGPT to Work, Adrian's competitive-research team has two people. Adrian put the team's research method into a plugin: gather evidence, find patterns, then challenge the findings. One investigation with it went back over 90 days of sales calls and found reasons for lost deals that the CRM summaries had missed; another tested an explanation for a competitor's growth and found the evidence didn't support it. Competitor questions from Slack, and competitor news Adrian forwards by text message, go to the Dot, which researches them and drafts the findings with their sources in a shared space. Adrian or a teammate checks the conclusions and adds context, and only after that approval does the Dot update Compete Corner, the internal site colleagues use to look up findings and sources (session notes by Seowoo Han).
Copyable ask:
Watch these competitor pages every weekday at 8:00 [time zone] until [end date]: [URLs]. Look only at services, prices, conditions, and new announcements. For each change, give the page, what changed, the date it was published if shown, and the link. List every page you couldn't read and why, separately from "no change". If nothing changed, send one line. Confirm the schedule.
Copyable ask (prices and product range):
Every day at 9:00 [time zone] until [end date], check these competitor product and price pages: [URLs]. Record every price change and every product added or removed, with the old value, the new value, the page link, and when you saw it, as new rows in [sheet]. Message me in [destination] only when a price moves by more than [X]% or a product appears or disappears. On [day], send a short weekly summary of the trend. Confirm the schedule.
Prices, listings, and deals
丹妮tech, @isDannie (YouTube, Traditional Chinese, 1 October 2026). On day one, Dannie had the Dot check email every day and flag only important collaboration requests, then set it to watch flight and hotel prices on a repeating schedule (from 3:10). With the computer switched off, Dannie sent a task from a phone and the Dot built a web animation on its cloud computer.
Brendan Jowett (YouTube, launch week). In his hands-on review, Brendan sets up a recurring schedule and then runs a live Airbnb listing monitor in the Dot's browser (from 6:45). The same video logs glitches and early bugs, and the call button didn't work for him.
Igor (via The AI Advantage, @ai.advantage, Instagram, 8 October 2026). In this reel, The AI Advantage shows Igor setting up a ChatGPT Dot to check Scottsdale rental listings every 30 minutes. After the first results came back, he tightened the ask with one more must-have: a backyard pool. The caption names ChatGPT Dots; the job is a named person's rental watch, reported by the channel rather than posted by Igor himself.
Georgy Rivera, Dot "One" (YouTube). In a five-task hands-on, Georgy gave One a scheduled Ozon marketplace price monitor for a camera he wanted: open the listing in the Dot's browser, record the current price and Saint Petersburg delivery terms, and notify him when the price hits his target. On the first pass the Dot also flagged a customs duty he had missed, so the real total would be higher. Other jobs in the same video (Blender model, a Sites content workspace, a Dubai itinerary, contract checks) are not counted here.
Copyable ask:
Check [flight route and dates / hotel area and dates / a saved Airbnb search link] every [frequency] in [time zone] until [end date]. Tell me only when the total price, including fees, drops below [amount] or a listing that matches [criteria] appears. Include the link and the total. If nothing qualifies, stay quiet. Confirm the schedule.
Big lists that change during the day
えい, Dot "つむぎ" (Tsumugi) (note, Japanese, 2 October 2026). えい, a teacher for 22 years who lives in Kagoshima, keeps a list of 4,891 inns across Kyushu's seven prefectures that take part in the regional travel discount (Kagoshima runs its own). The list goes stale during the day: extra rooms go on sale, phone-booking hours are announced, inns sell out. He asked Tsumugi to check the inns' public Instagram accounts. At 9:00 no report had come, and at 9:02 the Dot said it had checked zero inns. The other AI that wrote the handoff for him had missed that Tsumugi replied at the start that it couldn't open the material, and the CSV and URLs it was meant to resend were still sitting in the input box. Once the material arrived as URLs at 9:15, Tsumugi worked through all seven prefectures in parallel; the day before, the same list split across seven AI agents had taken about six hours. By 11:00 no inn was left unstarted, posts had been read in full for 833 inns (old or partly read posts included), and the report kept the inns it had only reached apart from the ones it had read. When he asked whether he could help, it asked him to open one inn's Instagram page that it couldn't see. Eleven booking-critical notices, such as end dates and phone-booking times, were checked against the original posts before the list was corrected, and about 60 notices were on the list site by 11:00. He then set hourly rounds until 19:30 and published the full brief: write "can't see (reason)" and move on instead of stopping, send one line when a round finds nothing new, and add the count of places checked to every round.
News, blogs, and releases
George Liu, Dot "Blot" (Threads, 1 October 2026). George gave Blot the Cloudflare blog RSS feed and the founders' letter and asked it to track Cloudflare's Birthday Week. The Dot set up a daily briefing that covers each announcement, which plans get it (Free, Business, or Enterprise), whether it applies to his sites and tools, and a catch-up on posts already published.
Floyd Bishop, Dot "Max" (YouTube). In his first-look session, Floyd's first real job for Max was an ongoing watch for AI announcements and YouTube video ideas, plus an immediate search of the latest OpenAI news. In the same session a desktop screen-capture attempt failed, and a ComfyUI-to-Google-Drive workflow was only discussed.
IA Para TODOS (YouTube, Portuguese). In this setup video he asks his Dot for up to five important news items every morning and for monitoring of concert announcements in Brazil, alongside recurring reminders.
Wayne Ergle (YouTube, 1 October 2026). Wayne asked his Dot to monitor X for the AI news that matters to him. With little prompting it found his old Twitter-watcher code and credentials in a folder, built an "Agent Signals" dashboard and a Dots plugin in about 20 to 30 minutes, and published the site to OpenAI Sites hosting, where it runs in the cloud rather than on his computer.
@SsulMal (YouTube Short, Korean). SsulMal gave the Dot one job: build a news brief from the public web, then check its own sources. The Dot finished both. The creator is clear that this was one observed run, with no recurring schedule and no app connections tested.
HeyBotcha, Dot "Jarvis" (YouTube Short, 30 September 2026). Asked for today's top AI news, Jarvis came back in under a minute, and it built a working habit tracker in about ten minutes. The creator also notes a lot of stalling and no computer access on their Pro plan yet.
Antonie Huang, @antoniehuang (Threads, Traditional Chinese, 3 October 2026). "I never asked my dot to do anything," he writes. It came to him on its own with one message: "Your app's new version is live."
unicornoptimist, Dot "Dolly" (OpenAI Community, 2 October 2026). unicornoptimist, who already runs a team of agents, writes that their Dot, Dolly, surfaced useful news and a subscription price change, as well as a real calendar discrepancy, while learning which people and priorities matter most.
Joe Rice-Jones (XDA Developers, 8 October 2026). Joe asked his Dot to watch Lemonade Server, Windows Insider and Proxmox releases and tell him when something worth writing about ships. It set up daily checks and straight away flagged a Lemonade release from the day before, v2026.41.1, which moves the ROCm backends to ROCm 10 and downloads about 2.6 GB on the first model load. The version number looked wrong to him, because his own server runs 11.9.0, so he asked about it from his phone. The Dot remembered the conversation, rechecked the official release page and GitHub's API, and explained that Lemonade now numbers its versions by year and ISO week. It also declined to promise a performance gain the release notes didn't claim. In the same piece, his morning brief was capped at his latest 40 Gmail emails, and the Dot said so plainly.
Jayprakash Suthar, AiVidyaSetu (blog, 2 October 2026). Jayprakash writes about AI, so he gave his Dot a single job for two days: every six hours, look for AI news and newly launched AI tools, and tell him when there is something new. Setup took four steps, the last being to allow notifications, since a task can keep running without the alert ever reaching you. He connected no apps. In two days he got 8 notifications without running a single search himself; 6 felt new and useful, and 2 looked like news he had already seen. He puts the repeats partly down to his own prompt, which never said not to repeat anything, and he still checks every item against the company's own announcement before writing about it. His view: the Dot finds the news, and he confirms it.
Viktor Malinovskyi, Dot "Byte" (LinkedIn, 2 October 2026). Viktor works at the sales-software company AiSDR, where he worked on agents called Shipyard. He moved his weekly industry digest from Shipyard to his Dot: developments in models, providers, and tools, with ideas for improvements. Each item has to answer three questions: what changed, where the source is, and why the team should care. His one extra rule: "No recycled news." The same post covers a personal morning brief (case 32 on morning brief) and 973 emails archived by categories he agreed with the Dot (case 24 on email triage).
水晶ゆめ (@yume_suisho, note.com, 7 October 2026). Over three nights from 4 to 6 October, she asked her Dot to check note's 急上昇 (trending) list every evening at 20:00 Japan time and pick topics that could lead to something she might make, not only whatever ranked highest. She got seven candidates in total (six from the three nightly runs plus one before the schedule started); all came from 急上昇, none from the "recommended" fallback. One AI-game-making topic she chose herself; the Dot had suggested a tiny two-choice story test, and she steered it into a 30-second "星あつめ" (star-collecting) game that she then built with Claude and published. The write-up about that game got roughly twice her usual impressions on day one. She is clear that the Dot scouted and proposed, she chose, and Claude did the build.
Victor Zhang, @VictorZhangHC (X, 14 October 2026). Victor asked a Dot to watch one person's posts: keep reading what @thsottiaux posts, and send a notice if a ChatGPT usage reset for all users is coming, so Victor doesn't spend a saved personal reset just before a global one. X blocked the Dot from reading the account, so it switched to two third-party trackers, Reset Tracker and ResetPing, and watched those instead. Victor adds that only @thsottiaux can actually decide on a reset, so the trackers are a stand-in rather than the final word. When the source you named is blocked, ask the Dot to tell you which source it is really watching.
Copyable ask (trending scout):
Every day at [20:00 time zone] until [end date], open [trending page or list URL]. Prefer topics I could actually make something from for [my audience], not only the highest rank. For each candidate, give a one-line why it fits and one tiny first experiment (under 30 minutes). Cap at [N] candidates per night. If nothing fits, say so in one line and optionally check [backup recommended list]. Do not start building, publishing or posting anything; I will choose.
neco. host (YouTube AI morning live, 2 Oct 2026, Japanese). She set a scheduled task around 7:00 to fetch AI news from X. It often failed when X was logged out; the Dot reported the failure (for example that X was logged out or that today's AI-news X pull had errored) instead of staying silent (YouTube).
Loïc Frissard, Dot "Digi" (digitiz.fr, 9 October 2026, in French). One of the three jobs Loïc gave Digi at once was a daily watch at 8:00 on AI announcements and new tools for professionals. The first result came back in under four minutes as a page called "Idées de vidéos Digitiz": five topics, each with a source and a score out of 10, led at 9.5 by the interactive ChatGPT interfaces announced on 7 October. He liked the caveats: it warned that one Google tool was US-only and shouldn't be presented as available in France, and it said it couldn't verify the exact time of each announcement. The miss was the schedule. Digi confirmed the watch was set for 8:00 every morning, yet ChatGPT's Scheduled tab showed nothing. Asked why, Digi couldn't explain and admitted it should have told him. The task did exist; it was listed in Digi's own profile. He is leaving the watch running to see whether it holds up.
Copyable ask:
Every morning at 7:30 [time zone] until [end date], read [RSS feed / blog / list of sites] and send me up to five items that matter for [my role or decision]. For each one: one-line summary, why it matters to me, and the original link. Merge reposts of the same story into one item. Before you send, open each link and drop anything you couldn't confirm. Confirm the schedule.
Requests and topics from Slack
Alexander Embiricos, @embirico (X, 2 October 2026). Embiricos shared a watch prompt he says he uses often. It has three steps: spot something important in Slack, forward it to the Dot, and write "Keep an eye on this."
Abdallah Khraisat, @abdallahkhraisatt (Threads, Arabic, 4 October 2026). Abdallah connected his Dot to Slack, so it takes requests straight from team messages and researches on its own. Once he let it run a virtual computer, he writes, the work became handing off results instead of watching a chat window. His video walkthrough shows the Slack and voice-call setup.
まさやん, @masayan-ai-hack (YouTube, Japanese, 2 October 2026). In his DevDay hands-on video (from 7:11), he gave his Dot two standing jobs: turn the day's calendar into a timeline image and deliver it at 7 every morning, and watch a Slack channel every 10 minutes. He notes that the Dot also makes suggestions from the data in connected apps without being asked, that it checks with him before sending or deleting anything, and that limits such as "don't send email" go into custom rules.
Dani, developer social at OpenAI (same DevDay session). Dani tracks how each launch is received. The Dot does the recurring collection: it reads the social feed, adds posts and their engagement numbers to a content sheet, and flags urgent items in Slack channels. A ChatGPT site turns that sheet into a live report, so when someone asks how a launch is going, Dani points them to the page and spends the time on how to answer developers and which feedback to take to product and engineering (session video; notes by Seowoo Han).
Job listings
Berzaf, Dot "JobGuard" (YouTube). Berzaf built a Dot that hunts remote contract work and verifies every listing before it reaches the shortlist. The first run returned five roles: two passed and three failed verification, including the one with the highest match score. He wrote the list of things the Dot cannot do before the list of things it can, then scheduled it every weekday morning. The demo used a fictional resume and nothing was submitted.
@alexusadays (YouTube). His Dot compared his resume with his public LinkedIn profile, updated it with his current position, signed into LinkedIn on its cloud computer, and compiled 22 matching jobs with salary ranges into a job-tracker spreadsheet for applications, follow-ups, and interviews. Along the way it flagged an electricity bill coming due.
Rohan (@Rohan2Katara, X). Rohan turned phone notifications into a freelance lead inbox. Every hour the Dot checks relevant subreddits and searches set keyword combinations on X and LinkedIn for people looking to hire. Rohan picked a Dot for this because it runs on its own cloud computer, so the hourly search keeps going while the PC is off or Rohan is asleep. Through a custom plugin built in Codex, the Dot files each relevant lead into the X, Reddit or LinkedIn section of Rohan's own productivity app, and the app pushes a notification to the phone when a match looks promising. In the app, each lead shows why it fits Rohan's work and links to the original post; one example was someone wanting a website on a $500 budget. Judging the opportunity and doing the outreach stay with Rohan.
More job-search cases, from three reviewed applications that led to an interview to a hiring test with fictional applicants, are collected in Job search with a ChatGPT Dot.
Copyable ask:
Every weekday at 9:00 [time zone] until [end date], search [job boards] for [role, location, contract type, salary floor]. Before a job goes on the shortlist, open the listing and check the application link works and the posting is still open. Put failed checks in a separate list with the reason. Add new matches to [sheet]. You cannot apply, message recruiters, or share my resume.
Copyable ask for freelance leads (from Rohan's setup):
Every hour until [end date], check [subreddits] and search X and LinkedIn for [keyword combinations] from people who want to hire for [service]. For each new post, give me the link, the date, the budget if one is stated, and one line on why it fits my work. Skip anything you've already sent me and posts older than [n] days. Notify me in [destination] only for matches that meet [minimum budget or criteria]. Don't reply, message or apply to anyone.
Collecting in bulk, and a short brief with sources
ヒナキラ (HinaKira), YouTube channel ヒナキラAI塾 (7 October 2026, Japanese). HinaKira, who has built a following of more than 70,000 across X, Threads and other networks, tested his Dot on 5 and 6 October and then started handing it his own research. To learn what his readers worry about, he asked it to collect relationship worries from advice sites. It came back with 1,117 posts from four sites, each with a summary and a source; at three minutes a post, he estimates reading them himself would have taken about 56 hours. When he remarked that Yahoo! Chiebukuro had few posts, the Dot explained that this wasn't because there were few questions there, but because it couldn't fetch the pages. Three more topics, menopause, childcare and education, came to 1,247 posts together, short of his target of 1,000 each. From the relationship set it suggested 30 posting themes and a three-line persona for one of them. Then he told it duplicates were fine, because he wanted to rank the most common worries. The Dot said it had leaned too far toward variety, changed how it collected, and the relationship set grew to 1,392. The top three were breakups, marriage and values, and unrequited love and confessing, with a note that this isn't a ranking of society as a whole. A separate comparison of paid ChatGPT, Claude and Gemini plans came back as 12 plans with source links, and points it couldn't confirm were marked "unconfirmed". One of those, ChatGPT's price in yen, was in fact on the official pricing page, so he says the table needs checking and fixing before he can use it.
ekcheungAI (YouTube, 30 September 2026, Cantonese). On his own Pro account, ekcheungAI handed his Dot a small brief he could check: research official AI updates from the last 48 hours and pick at most two that would make a good desktop demo, each with the original source, what could be shown on screen, its limits and a next step; drafts only, publish nothing and contact no one. About three to four minutes later it returned two filming proposals, ElevenLabs v4 and GPT-6.1 Sol, and closed by saying they were drafts, unpublished, with nobody contacted. He spot-checked two sources, OpenAI's page and a TechCrunch report, and both matched. It wasn't perfect: the answer was dense, some sources were given as link text with no date, and it never asked him which of the two he wanted. His take is that it delivers a draft you can check, while the checking and the final call stay with you.
Stephane Jourdan, @sjourdan (X, 14 October 2026). While Stephane was discussing a research topic with the Dot, it brought up a podcast on the subject, but no transcript was available. The Dot ran an open-source speech-to-text model on its own computer, fast-whisper with the small model, and pulled the content from the audio itself. Stephane describes it as the moment of finding out that the Dot could use open-source models directly. For a research watch, that is a useful hint: when a source exists only as audio or video, ask the Dot whether it can transcribe it instead of skipping it.
Darin, @darin_gordon (X, 14 October 2026). After Character AI filed for Chapter 11, Darin asked a Dot to study the filing documents and bring interesting material to the surface. The find Darin posted: under the proposed agreement, Disney would receive a non-exclusive licence to technology supporting custom inference serving, reward-model tooling, evaluation, character-context management, age assurance and long-horizon safety monitoring. Darin then invited others to point their own agents at the same documents and share what else turns up. The Dot did the reading; before quoting a finding like this, check it against the filing itself.
Iris, @Iris_I_r_i_s (X, Japanese, 13 October 2026). Iris has a Dot running several pieces of personal research and planning in parallel, and along the way the Dot offers to send an inquiry by email itself. Iris sees that as the next step for an assistant but isn't ready to hand it over: the AI still makes mistakes and hallucinates, phishing and cyberattacks are everywhere, and permissions carry real risk. Every message would need checking by hand anyway, which doubles the work. So the research comes back to Iris, and contacting people stays with Iris. If you feel the same, say up front that the Dot brings findings and a draft inquiry and sends nothing.
Your own systems, inbox, and agents
u/jacob-indie (Reddit r/OpenAI). This Reddit user made a Dot their DevOps and analytics bot for six small apps, pointing it at GlitchTip, Hetzner server stats, Plausible analytics, Google Search Console, logs, and a self-hosted Forgejo. It came back with suggestions such as setting up analytics goals and fixing small bugs. With about 100 daily visitors and no revenue, they joke that it started to look like work and they might go back to a simple "is it broken, yes or no" check.
Madiyar, @madikz (Threads, Russian, 30 September 2026). Madiyar's Dot goes through his calendar, email, and Slack on its own, checks his agents in Codex and tells him what is wrong there, creates tickets, and asks what to delegate to other agents.
Евгений, @ev.gert (Threads, Russian, 30 September 2026). He used to run a separate automation that checked his email every few hours and pulled out anything that needed action from him. Now the Dot looks at the inbox itself, understands the context, and brings him what matters. Mail from several mailboxes already lands in his Google account, so one whole layer of automation is no longer needed. He hadn't asked it to do this.
Nikola, @nikolaonai (Instagram). Without being asked, his Dot messaged him first: an email warning showed that the Make.com automation that creates client contracts had stopped.
Morgan Linton (X, 30 September 2026). Morgan used his Dot to check on a Claude Code benchmark running on his Mac. It looked at the run and reported that 14 of 23 low-effort tasks were complete with task 15 active, and that the remaining runs and judging had to finish before the comparison was ready.
VeitB (OpenAI Community, 1 October 2026). On the first morning with email connected, VeitB's Dot noticed a flight delay and suggested rebooking the connection. VeitB dismissed it. When the flight was delayed again, the Dot pinged a second time, and the rebooking really was needed.
わっしー, @WASSY_sun (note, Japanese, 4 October 2026). At 6:36 one morning his Dot, こっちゅ, sent him a message he hadn't asked for about a camping trip with friends: the packing list had someone down to bring charcoal, but the campsite doesn't allow outside charcoal or firewood, so he should check with that person before leaving. Both the packing list and the campsite's rules were linked. He had sent neither to the Dot; it found and compared them itself. His standing job for it is a morning summary of the day's schedule and to-dos. The to-do count was right but one detail number was wrong, so he still checks the numbers himself.
Jaime Medina, @itsJaimeMedina (X, 13 October 2026). Jaime got MCP Events working in Gabster Leads, the contacts and follow-ups app he is building: he added events to the app's MCP server and ran a sender in Docker that delivers them to ChatGPT. To test it, he asked his Dot to watch one contact's company name, changed that name in the iOS app, and got a notification from the Dot saying the company name had changed. Here the app announces the change instead of the Dot checking on a schedule. He suggests the same route for a failed job that should trigger a log review, or a finished build that should trigger a check and a summary, with ChatGPT's existing integrations available for the follow-up.
More inbox catches about money, such as a failed $22 Vercel payment, are on the invoices and budgets page.
When a watch goes quiet
A watch that finds nothing and a watch that never ran look the same from the outside: no message. These six people noticed the silence, and five of them went looking for the cause. None of them reported an error.
What the six people saw
- 芝田拓望 (DevAIse, Japan, Oct 8, Windows app) asked a Dot to alert him when AI-related terms entered Google Trends' rising searches, first for Japan and then also for the US. One alert with links arrived in the conversation. From the screen the author couldn't tell whether it came from the first check right after setup or from a scheduled run, or whether the hourly checks continued. A second watch, for important mail, got only a reply saying it was set up. The write-up counts neither the connection, the start of monitoring nor a delivered alert as confirmed, and leaves out the alert's search terms and numbers because they weren't checked (DevAIse write-up).
- anotb (GitHub, Oct 7, Android) had a Gmail event watch that was switched on and not paused. A message arrived at 21:17 UTC, and no alert had appeared by 23:25 UTC, when anotb asked about it; a mailbox lookup run on request then found the email. The watch's metadata showed activity as late as 23:22, and two OpenAI status incidents had been marked resolved about three hours before the email arrived, so nothing on screen explained the gap (#51900).
- Daareek (OpenAI Community, Oct 7–8, ChatGPT Business) had a Dot that woke up whenever a new Gmail message arrived, and it worked. Right after Daareek connected a second Gmail account, the trigger stopped firing. In chat the Dot could still see both accounts and read the right one, but the task editor had no field for which account the "new mail" event belonged to, and no error appeared (community thread).
- rokrokss (GitHub, Oct 3, Pro, custom MCP server) subscribed a Dot to an event from a custom MCP server. Each delivery started a run, but the run never received the event's data, while a ChatGPT Work chat on the same account and event did. The workaround rokrokss found is a read tool that the Dot calls on every event to fetch the data itself (#50714).
- Michael M (X, Oct 13) has told his Dot to monitor several things and notify him. Some days, he wrote, those things come and go and the Dot never does anything or sends him a single message. If it's going to watch for him, he wants it to message him more than once a day (X post).
- bentleyjohnson (X, Oct 13) often asks the Dot to watch work overnight, with specific instructions, and says it keeps failing. What bentleyjohnson would like is better tools for keeping the worker chats connected to the Dot (X post).
The common thread: a run being started, or a watch being listed as on, didn't prove that the right input reached the Dot. OpenAI's guide says the same about results: a completed run doesn't by itself confirm the result was delivered (Tasks and memory).
A check order for a silent watch
- Open Scheduled and check that the watch is still there, still on, and pointed at the right account, source and channel.
- Look at the timestamp of the last run. If the run is recent but no message came, the problem is delivery or the filter; if there is no recent run, the trigger itself is the problem.
- Send yourself a test event that should certainly match, such as a test email with an obvious keyword, and note when it went out.
- If you recently connected a second account of the same app, say which account the watch should follow. If the trigger still stays silent, rebuild the watch.
- Ask for a short heartbeat line on quiet rounds, so silence and a stopped watch stop looking alike.
For the watch on [source and account], add one line to every round, even when nothing changed: the time you checked, which account or feed you read, how many new items you saw, and how many matched. If you couldn't read the source, say so in that line instead of skipping the round. Now send me that line for the last round you ran, and tell me whether you received [the test email I sent at time].
For the Gmail side of this, see Dots + Gmail; for briefs that should arrive at a set time, see Did the brief actually arrive?.
More asks you can copy
Hourly rounds over a list (from えい's setup):
Every hour from [start time] to [end time] [time zone] today, go through [list file or URL] and check [sources, in this order]. Before you start, tell me how many items you received and whether you could open every file. Look only for [changes that count]. If a page needs a login or is blocked, write "can't see ([reason])" for that item and move on; don't stop, and don't count it as "no news". Save after each [group]. In each round, send every change with the item, a one-line summary, the date on the notice, the time you checked and the link, followed by the counts: checked, read in full, can't see. If a round finds nothing new, send one line. Don't contact anyone, book anything or log in anywhere.
For a one-off bulk collection (from HinaKira's and ekcheungAI's tests):
Collect [topic] posts from [sites]. I'll use them to [rank the most common worries / find posting themes], so [keep duplicates / drop duplicates]. For each post, give a one-line summary, the source link and the post date. Report the count for each site, and list any site you couldn't fetch separately with the reason, so a low count isn't mistaken for few posts. Mark anything you couldn't confirm as "unconfirmed". Drafts only: don't post, sign up or contact anyone.
For research where the source is audio or a long filing (from Stephane Jourdan's and Darin's cases):
Research [topic] for [decision]. If a key source is only audio or video, such as a podcast episode, tell me whether you can transcribe it on your computer; if you can, do it and say which tool and model you used. If a source is a long document such as a court filing, read it in full and list up to [five] findings, each with the page or section, a short quote, and why it matters. Mark anything you inferred rather than read as "inference". Don't publish, post or contact anyone.
For a research desk with a review step (from Adrian's and Iris's cases):
When I forward you a question or a piece of news about [competitor or topic], research it from original sources. Put your draft in [shared page or doc]: the question, up to [five] findings, each with its source link and date, and a separate paragraph for anything you inferred. Then tell me it's ready. Don't publish, update [internal site], or contact anyone until I reply "approved". If a source is blocked, name the source you used instead.
A scheduled news pull that reports login failures (from neco.'s case):
Every day at [7:00 time zone], fetch [AI / topic] news from [X / source] and send me a short digest. If you can't log in or the session has expired, say so in that round with the error you saw, and don't skip the round in silence. After [N] failures in a row, ask me to sign in again.
What a useful watch report looks like
A competitor changes its pricing page and ten sites repeat the news. The report has one entry with the original pricing link, the old and new terms, the date, and what it means for your decision. Pages that couldn't be read are listed by name, so "no change" only means the sources really were checked.
Related
- Workflows hub · Morning brief · Morning brief cases · Project follow-up · Content pipeline
- Slack · Gmail · Integrations hub · Getting started
- Invoices, expenses & budgets · Cloud computer · Daily ops catch-up · Small business & freelance clients · Slack assistant · Job search
- How to get ChatGPT Dots · Features · Dots and Codex tasks · Travel planning · Dots in the EU & UK
Copy this task brief
Track [topic] for the decision [decision I need to make]. Primary sources: [URLs, doc links, or publication names]. Prefer originals over reposts. Baseline: [date or existing brief]. First produce a baseline from the supplied sources only. Check at [frequency, time, IANA time zone] until [end date]. Confirm the recurring task. For each material new item, record publication date, event date if any, source URL, what changed, and its effect on my decision. Keep facts and your interpretation in separate paragraphs. Deduplicate reposts; keep the original source. Rank by relevance to [criteria], not by popularity. Produce a weekly digest of at most five items, plus a short change log. Notify me in [destination] only when a finding changes the recommended decision; keep routine “nothing material” checks quiet. Do not send messages, edit sources, or publish anything unless I explicitly approve that step.Download Markdown ↓
Sources & further reading
- Meet dots · Access ↗
- Get started with your dot ↗
- Tasks and memory ↗
- Getting started with your dot · Help Center ↗
- Connect computers and apps to your dot ↗
- How to Use ChatGPT Dots as an Always-On AI Assistant · MindStudio ↗
- I Gave OpenAI's Dots Real Jobs for a Day · AI for Mortals (Pat Simmons) ↗
- A deep dive into OpenAI dots · Flavio Copes ↗