Dots
Install openquok-core on OpenAI Dots — always-on ChatGPT agents with a cloud computer. Schedule from ChatGPT, Slack, or Teams. Not the ChatGPT MCP connector path.
Connect your agent today
Draft from chat, review in your calendar, and publish only what you approve.
Prerequisites
- An eligible ChatGPT plan with Dots (for example Pro, Business Premium, or Enterprise when your workspace admin enables it).
- ChatGPT on desktop or browser to create your dot and connect apps.
- For OAuth device login: you can authorize the sign-in link on your phone when your dot runs openquok auth:login on its cloud computer.

Dots vs ChatGPT MCP
Dots are always-on agents with a persistent cloud computer and plugins. ChatGPT MCP connects OpenQuok inside a chat session via a custom connector — better for ad hoc tool calls, not long-running CLI work on the dot computer. This guide is for Dots + openquok-core.
Installation
Create your dot
In ChatGPT, create and name your primary dot. Connect the apps your dot may read. Open the dot cloud computer when you want to inspect browser, filesystem, or shell work.
Product overview: Introducing dots. Help Center articles cover Custom Rules, Activity View, and app permissions.
Install the global OpenQuok CLI
Ask your dot to run this on its cloud computer:
npm install -g @openquok/auto-cli@latest
openquok --version Production auth uses the API at https://cli-auth.openquok.com and opens the browser on https://www.openquok.com/cli/device/verify.
CLI version update
Connecting a new plugin does not change openquok --version. Ask your dot to run npm install -g @openquok/auto-cli@latest when you need a newer CLI.
Install the openquok-core skill
The skill file lives at agent/skills/openquok-core/SKILL.md in the monorepo. Register it through your dot plugins workflow. Choose one install path:
Start a new conversation after install so your dot reloads skill instructions.
Authenticate
Recommended: ask your dot to log in to OpenQuok. It runs device OAuth on its cloud computer; open the link on your phone, sign in if needed, and tap Authorize.
Alternative for headless or scripted runs: rotate a programmatic token from the OpenQuok dashboard (Account → Settings → Developers → Access):
export OPENQUOK_API_KEY=opo_your_programmatic_token
openquok auth:status Credentials are stored on the dot cloud computer — not in Slack or Teams message history.
Confirm your dot can run commands
After auth, ask your dot to run:
openquok integrations:listVerify in chat
Ask your dot something like:
List my connected channels, then draft a LinkedIn post for tomorrow at 10am — do not publish until I approve on OpenQuok.
Posts should land as drafts or scheduled items in your OpenQuok workspace. Review on the calendar or kanban before anything goes live.
Dots + OpenQuok notes
- CLI-first: openquok-core teaches shell commands on the dot computer. Optional Cursor MCP is a secondary path for IDE sessions.
- Cloud computer: OPENQUOK_API_KEY and ~/.openquok/credentials.json live on the dot environment. Do not paste tokens into Slack or Teams threads.
- Custom Rules: require approval for outbound social actions. OpenQuok remains the calendar and kanban checkpoint before publish.
- Human approval: your dot can queue volume; you approve quality on OpenQuok.
Troubleshooting
Outdated skill or CLI
Updating plugins does not upgrade openquok --version. Ask your dot to run npm install -g @openquok/auto-cli@latest, then start a new chat.
Skill not found
Confirm ~/openquok-core/SKILL.md exists on the dot computer and that openquok-core is registered in plugins. Re-fetch SKILL.md if needed.
Plan eligibility
Dots roll out on eligible ChatGPT Pro, Business Premium, and Enterprise plans. OpenQuok billing is separate — you still need a workspace and connected channels in the OpenQuok app.