Skip to content
AwayHand

Grok Bot vs Dots

Dots are ChatGPT's always-on agents — proactive, memory-fed, app-connected; Grok Bot is the narrower, more transparent pick for xAI-side operator workflows.

updated 2026-10-24

▦Side by side
dimensiongrok botDots
priceFree tier for manual runs; Pro adds scheduling and connectorsLives inside a ChatGPT subscription — check OpenAI's current tier
permissionScoped per-agent memories and connector permissionsYou choose which apps it can access and when it needs approval — permissions managed in ChatGPT
automationConfigured agents you define: prompt + memories + scheduleProactive always-on agents that own a responsibility and keep working between conversations
mcpMCP connectors for operator tools like SheetsUses your connected ChatGPT tools — including Codex — rather than a fixed connector list
audienceOperators who want to see and control exactly what the agent doesChatGPT power users who want a persistent agent to own projects end-to-end
⇄When to pick them
migration cost: Low to medium. Prompts and memory content port; Grok Bot's advantage is that each agent is a readable, inspectable recipe — a Dots workflow is more of a black box you delegate to.

See it in practice: our weekly ticket themes digest is the recipe-style version of what a Dot would own — same outcome, but every step here is inspectable and copyable.

?FAQ
Are Dots and Grok Bot the same kind of thing?
Adjacent, not identical. Both are persistent agents on a subscription platform; Grok Bot is per-task configurable and inspectable, Dots are always-on and delegated.
Which is better for a weekly digest?
Either can do it. Grok Bot gives you the explicit prompt+schedule recipe to copy; a Dot would own the outcome with less visible machinery.
Can I move my Grok Bot templates to Dots?
The prompts port fine — the deps don't. Memories, connectors, and scheduled runs are Grok Bot constructs you'd re-create inside ChatGPT.

New templates as they land. No hype.

Email to subscribe →