ChatGPT
Desktop, web, and mobile — create your dot and inspect its cloud computer
We are finishing the Skool integration for Dots. Check back soon for platform-specific workflows, examples, and setup guides.
On it — openquok-core
Created drafts with cover image attached.
✓ Queued for Tue 9:00 AM · ref oq-7f3a
Your always-on dot
Ask your dot to draft and schedule like any other project. The openquok-core skill runs on its cloud computer. It lists integrations, attaches media, and queues posts. You can publish now, schedule for later, or save drafts and approve on OpenQuok when you are ready.
Built for community builders with Dots
Keep groups warm with a steady calendar. Approve every post before it hits the feed. Message Dots to draft Skool posts from chat — publish now, schedule, or approve on OpenQuok.
Batch announcements and prompts for multiple groups. Reuse drafts from agents without manual copy-paste. Dots queues Skool drafts at volume — your team can publish now or approve first.
Connect client Skool accounts from the dashboard with the extension. Pipe drafts via API or MCP after connect. Run Dots per client workspace so Skool drafts stay isolated.
Dots are always-on agents on OpenAI-managed cloud computers with plugins and workplace chat. Choose OpenClaw when you need a self-hosted Gateway instead.
Connect once
Run OAuth device login on the dot cloud computer once. Credentials stay off casual chat threads. Message from ChatGPT or Slack to draft and schedule without opening another dashboard.
CLI authentication options
# OAuth2 device flow (interactive — opens browser)
openquok auth:login
openquok auth:statusbot
Sample channels
These chips set format and character limits. They are not your accounts.
Groups load from your Skool account after you connect the channel.
Group settings
Choose the target group from your connected account. Add a post title and category in Settings. Attach images when your group allows media. Preview the card before you queue the slot.
CLI command options
# Draft + human checklist (Skool)
openquok posts:create --json ./examples/skool-text-title-group.json
openquok posts:review-todo <post-id> --note "…"
openquok posts:status <post-id> --status draft
openquok posts:status <post-id> -s scheduleFollow-up comments
When the group allows it, add follow-up comment rows in the composer with delays and optional media. OpenQuok publishes the main post first. Then it posts each comment on your connected account.
CLI analytics options
# Skool post with follow-up reply
openquok posts:create --json ./examples/skool-follow-up.jsonSample channels
These chips set format and character limits. They are not your accounts.
Workspace tools. Sign in or sign up to use your library, Photo Editor, and signatures.
84 / 5,000
Follow-up comment publishes after your chosen delay.
comparisons
OpenQuok is built for Skool from Dots that finish work. Dots fit when you want ChatGPT-native always-on help with a cloud computer.
CLI
Skool commands from the openquok-core skill — structured JSON on stdout, human-in-the-loop drafts, and workspace media uploads.
openquok integrations:list | jq -r '.[] | select(.identifier=="skool") | .id'Discover your Skool integration UUID
openquok integrations:settings "$SKOOL_ID"Get Skool posting rules, title/group schema, and allow-listed tools
openquok integrations:trigger "$SKOOL_ID" groupsList Skool groups as { value, label } options
openquok integrations:trigger "$SKOOL_ID" label -d '{"id":"<group-id>"}'List labels for a Skool group
openquok posts:create --jsonSchedule a Skool post with title and group
openquok posts:create --jsonSchedule with an optional label id
openquok posts:create --jsonSchedule a Skool post with a cover image
openquok posts:create --jsonSchedule a post and follow-up comments on skool.replies
Where you chat
Dots meet you on the surfaces you already use. Install openquok-core through plugins on the dot cloud computer:
Desktop, web, and mobile — create your dot and inspect its cloud computer
Message your dot in Slack with shared context from ChatGPT
Continue projects in Teams without re-explaining context
Connect apps and register openquok-core on the dot computer
Browser, filesystem, and shell your dot uses for finished work
Follow background work and redirect your dot when plans change
Optional MCP in editors
Optional OpenQuok MCP when you schedule from the IDE instead of your dot
Start with Skool, then schedule every other network from Dots.
Autonomous agents & MCP
Open another autonomous agent or MCP client landing page. Dots and OpenClaw stay pinned first so you can compare OpenAI-aligned hosts beside Dots.
Autonomous agents
Preview Skool workflows for Dots — coming soon.
Preview Skool workflows for OpenClaw — coming soon.
Preview Skool workflows for Hermes Agent — coming soon.
Preview Skool workflows for Grok Bot — coming soon.
Preview Skool workflows for Meta Muse — coming soon.
Preview Skool workflows for ThinkRail — coming soon.
Preview Skool workflows for Manus — coming soon.
MCP clients
Preview Skool workflows for ChatGPT — coming soon.
Preview Skool workflows for Antigravity CLI — coming soon.
Preview Skool workflows for Codex — coming soon.
Preview Skool workflows for Cursor — coming soon.
Preview Skool workflows for Claude Code — coming soon.
Preview Skool workflows for Claude Cowork — coming soon.
Preview Skool workflows for VS Code / Copilot — coming soon.
Preview Skool workflows for Devin Desktop — coming soon.
Preview Skool workflows for Amp — coming soon.
Preview Skool workflows for Warp — coming soon.
Preview Skool workflows for Muse Code — coming soon.
Preview Skool workflows for Grok Build — coming soon.
Frequently asked questions
What Dots is, how to install openquok-core, scheduling Skool posts, human approval, and Skool setup questions.
It depends on you. You can ask your dot to publish now when the copy is ready, or save drafts and scheduled posts and approve them later on the OpenQuok calendar or kanban. Tell your dot to use draft-only or not to publish when you want a review step first.
Step-by-step self-host setup for connecting OpenQuok to Dots — install commands, auth patterns, and configuration snippets.
Connect your agent, review every draft, and schedule posts across channels before anything goes live.