Real use case

A ChatGPT Dot took overflow work when Grok Bot hit its cap

Jesse ran his AI work on Grok Bot until the weekly cap stopped morning scorecards and reply checks for almost two days. He paired Link, his Grok Bot, with Neo, a ChatGPT Dot. They share one Notion workspace as a brain and one Slack room. Link assigns in-scope tasks; Neo drafts in Notion and returns work for review; Jesse still approves anything public. On Nov 6 he describes two handoffs: a beginner AI lesson draft in about 19 minutes, then a Spanish version for Latin American readers in about 8 minutes to delivery. Times are to a draft, not to published. The useful pattern is a shared task list and a hard rule that nothing goes out without a person.

AgentChatGPT WorkGrok Bot

Copy this prompt

I want two agents to share work without either spending money or posting in public without me. Shared brain: a Notion page with an operating guide, memories, skills and a tasks database with an Agent field. Shared room: Slack channel [#agents]. Rules: one task per thread, drafts only, Ready for Review before anything advances, and nothing public, purchased or sent outside the team without my OK. Set up your side, list what you connected, and stop for my approval before the first real handoff.

Our own prompt, written from what the source describes. We haven't run it ourselves. Text in [BRACKETS] is what you replace.

Watch out for

  • Dots are directed by their owner. Partner-bot mentions may need an extra Slack automation, which is a workaround.
  • A shared Notion brain still needs least-privilege sharing. Give each agent only the pages it needs.
  • This is not automatic failover. A person still decides who does what when a meter runs out.

Where this comes from

Original post by @JesseHeredia on X, Nov 7, 2026. We rewrote it in our own words. The result is what the poster reports.

Read the original

Guides for this job

Email & workPrompt run 2026-10-19

Turn a messy inbox into a 5-minute daily summary

Paste in today's emails and get back what needs a reply today, what can wait, what to ignore, and a one-line reply for each. It also flags emails that look like scams.

ChatGPTClaudeGeminiGrok
Prompt guide
Keep going

More like this

LessonEmail & work

A ChatGPT Dot's files vanished overnight

He says his Dot's whole workspace was suddenly recreated empty on the evening of Nov 7 (UTC), and his original work was gone. Missing were a large handoff package and three project folders, some of which he had not saved anywhere else. He emailed OpenAI support with timestamps and file details and asked them to preserve the old disk, but says the only reply so far was automated. He also points to other users reporting wiped or rolled-back workspaces. Whatever the cause, an agent's computer is not a backup.

PromptAt the end of each work session, list every file you created or changed today, then copy them to my [GOOGLE...

ChatGPT Work
Copy prompt
@jerry_ying42171 on X · Nov 8, 2026
LessonEmail & work

An OpenClaw project corrupted, backups and all

UID -2 says their OpenClaw project got corrupted recently, including the backups. They tried Codex for hours with no luck, then Opus, which failed faster and burned their limit. A different stack (they name Argon and Antigravity) recovered the project in about five minutes using under 3% of the limit. Self-hosted agents fail in ordinary ways: bad upgrades, broken state, backups that share the same disk fault. Keep off-box backups, and practice a restore on a spare folder before you need one.

PromptAudit my OpenClaw install at [PATH]. List the data directories, which folders a backup must include, and...

OpenClaw
Copy prompt
@axelhyyd on X · Nov 7, 2026
LessonEmail & work

Grok Bot hit the weekly limit in 4.5 days; pause, don't rebuild

Rob's Grok Bot roster burned the weekly usage limit in about four and a half days. He considered upgrading, buying credits, or moving work to Meta Muse. He exported the usage CSV and asked Claude to read it. Claude found that about 91% of tokens were cached context reloads and that four routines on one bot drove about 70% of the burn. They paused seven routines instead of deleting bots, kept all 16 bots, and had the main bot check the usage meter each morning so nice-to-have jobs only run when there is room. He upgraded to Super for a short measured stretch, with a plan to drop back to Premium if the numbers fit. The lesson: inventory and pause before you rebuild everything elsewhere.

PromptI hit my Grok Bot weekly usage limit early. Here is my usage export: [CSV OR SCREENSHOT]. Rank routines and...

Grok BotClaude Cowork
Copy prompt
@LegalDadHacks on X · Nov 7, 2026