Guide diagrams OpenAI Dots setup with five agents and six-line briefs
A squirrel-and-nuts analogy explains how to write job files for five OpenAI Dots agents, stressing that the 'never' list should come first.
picture a squirrel briefing 5 ai agents with 6 nuts each, and the last nut goes in first that's how we drew a setup guide for openai's dots, agents that keep working after you close the tab one tree: 5 job files, 1 blank brief, 6 lines, 4,000+ apps in reach one dot, one job. never-list first. one week before a second one dot watches your rivals one dot filters freelance leads one dot drafts the monday client report the clicking takes minutes. the six lines take an evening, the guide says • the six nuts (00-blank-brief.txt) > JOB - one per dot > WHERE TO LOOK - apps you already pay for > WHEN - its clock > WHAT COUNTS - situations you can point at, not "important" > WHAT I GET - a reply you check in about 60 seconds > NEVER - the don't list • the five files > 01-founder-rivals - weekdays, 4 change types, before + after + link > 02-freelancer-leads - 2x a day, max 5 leads, up to 10 a day instead of an open-ended scroll > 03-agency-monday-report - monday before 9am, 4 blocks, left unsent > 04-creator-launch-watch - 2x a day, primary source, never a roundup > 05-inbox-queue - 4 buckets: today, this week, drop, unclear • rules > one-job - three jobs per dot, the guide claims, gets you work you'd refuse to pay for > quiet-day - if nothing moved, the report says nothing moved 14 checks a week. about 260 reports a year ↳ any twice-a-day dot, and the weekday rival watch. you open neither feed the source has no run logs or measured hours. every number above is a brief setting, so the time-saved figures stay out of the tree the nut that goes in first is NEVER. write the don't list first, even if you never switch a dot on ↓
This post quotes another post: x.com/6aw0ron0k/status/2107481353331614069