OpenQuok Core
Schedule and manage social posts with the openquok CLI — authenticate, upload media, create drafts and scheduled post…
OpenQuok Schedule Dev.to from Dots then you approve
Message Dots from Telegram, WhatsApp, or Slack. Add the openquok-core skill so it schedules Dev.to posts while you review on the calendar or kanban.
The Getting Started Guide The Getting Started Guide The Getting Started Guide
Try for free for 7 days Try for free for 7 days Try for free for 7 days
Install our core skill:
npm install -g @openquok/auto-cli@latestDraft and schedule my product launch thread for Tuesday at 9am across Facebook, Instagram, and
Threads.
On it — openquok-core
Created drafts with cover image attached.
- • Facebook — Tue 9:00 AM
- • Instagram — Tue 9:00 AM
- • Threads — Tue 9:00 AM
✓ Queued for Tue 9:00 AM · ref oq-7f3a
Your always-on dot
Chat in ChatGPTSlackor Teams
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 technical writers with Dots
Who schedules Dev.to with Dots?
Engineers & indie hackers
Ship changelogs and tutorials from the calendar, not the Dev.to editor. Message Dots to draft Dev.to posts from chat — publish now, schedule, or approve on OpenQuok.
Developer relations
Batch docs and release notes with tags, series, and covers. Review on kanban before publish. Dots queues Dev.to drafts at volume — your team can publish now or approve first.
Agencies & technical blogs
Connect client accounts with an API key. Pipe markdown drafts via API or MCP. Run Dots per client workspace so Dev.to drafts stay isolated.
Connect once
authenticate on the dot computerpick your workspacechat from Slack securely
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:statusCreate Post
Sample channels
These chips set format and character limits. They are not your accounts.
Editing a Specific Network Back to global
Workspace tools. Sign in or sign up to use your library, Photo Editor, and signatures.
111 / 100,000
Post Preview
OpenQuok on Dev.to
Jun 16, 9:00 AM
Ship technical posts with tags and series you approve
Series · Shipping notes
Queue this markdown article with title, tags, cover, series, and an optional canonical URL before it goes live.
#webdev#productivity
Post editor
Write markdown articles in Dev.toreview drafts on the kanban boardbefore you approve
Write the body as markdown in the usual editor. Preview formatting. Schedule onto the calendar. Review agent and human drafts on the kanban board before anything goes live on DEV Community.
CLI command options
# Draft + human checklist (Dev.to)
openquok posts:create --json ./examples/devto-article-title-tags.json
openquok posts:review-todo <post-id> --note "…"
openquok posts:status <post-id> --status draft
openquok posts:status <post-id> -s scheduleTargeted channels
Overview
Trends
Compare channels using each network's closest matching metric. Totals add primary series per channel — not a single blended platform metric.
Views
3,771
1 channel
Engagement
138
1 channel
Followers
—
09/25 10/01
- OpenQuok on Dev.to (Page Views)
Page Views
Dev.to OpenQuok on Dev.to
12.6%
3,771
Reactions
Dev.to OpenQuok on Dev.to
8.4%
534
Comments
Dev.to OpenQuok on Dev.to
5.7%
138
Dev.to insights
See what resonates on Dev.to track views and reactionsand iterate
Dev.to analytics—Trends summary totals and per-account page views, reactions, and comments (7, 30, or 90 days). Then schedule more of what already works.
CLI analytics options
# Dev.to platform metrics
INTEGRATION_ID=$(openquok integrations:list | jq -r '.[] | select(.identifier=="devto") | .id')
openquok analytics:platform "$INTEGRATION_ID" -d 30
# Per-post insights
openquok analytics:post <post-id> -d 7Draft and schedule my product launch thread for Tuesday at 9am across Facebook, Instagram, and
Threads.
On it — openquok-core
Created drafts with cover image attached.
- • Facebook — Tue 9:00 AM
- • Instagram — Tue 9:00 AM
- • Threads — Tue 9:00 AM
✓ Queued for Tue 9:00 AM · ref oq-7f3a
What performed best on my channels over the last 7 days? Break down impressions and engagement.
Pulled platform analytics (7d)
Top post: 12.4k impressions, 842 reactions — carousel on product tips.
Facebook Page leads with +24% impressions vs last week.
Compare that post on TikTok vs Instagram Reels.
TikTok: 48k views, 2.1k likes. IG Reel: 31k plays, 312 saves. TikTok wins reach; IG leads on saves.
Draft and schedule my product launch thread for Tuesday at 9am across Facebook, Instagram, and
Threads.
On it — openquok-core
Created drafts with cover image attached.
- • Facebook — Tue 9:00 AM
- • Instagram — Tue 9:00 AM
- • Threads — Tue 9:00 AM
✓ Queued for Tue 9:00 AM · ref oq-7f3a
Scale what works
when a format hits, scale with workspaces and parallel projects
Spot a winner in analytics, then spin up another OpenQuok workspace for the next brand while your dot queues the next wave on its computer — credentials and channels stay isolated.
Parallel CLI sessions
# Workspace A — brand one
openquok posts:create -c "…" -s "…" -t draft -i "<uuid>"
openquok posts:status <post-id> -s schedule
# Workspace B — brand two (isolated credentials)
openquok posts:list --status draft
# Metrics in parallel
openquok analytics:platform <integration-uuid> -d 7Playbooks & Building Blocks Directories
Dev.to viral formats
Mix Dev.to-focused skills, and MCP servers — then tailor them to your Dots workflow.
comparisons
always-on dot, not another tab
OpenQuok is built for Dev.to from Dots that finish work. Dots fit when you want ChatGPT-native always-on help with a cloud computer.
Typical social scheduler SaaS
- Copy posts between chat and a separate scheduling dashboard
- Self-host ops when you only need a managed cloud agent
- Many named bots on a different vendor desktop app
- MCP-only sessions that end when you close the connector chat
- Autopilot publishing with no human checkpoint
- One workspace mixing every brand as you scale
OpenQuok + Dots
- Message your dot from ChatGPT, Slack, or Teams to draft and schedule
- Dots run on OpenAI cloud computers — you inspect work in Activity View
- One primary dot today — deep ChatGPT, Slack, and Teams context
- openquok-core on the dot computer for repeatable CLI scheduling
- You choose publish-now, schedule, or draft — approve on OpenQuok when you want a review step
- Multi-workspace isolation — separate credentials per client or channel set
CLI
Command reference
Dev.to 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=="devto") | .id'Discover your Dev.to integration UUID
openquok integrations:settings "$DEVTO_ID"Get Dev.to posting rules, title/tag schema, and allow-listed tools
openquok posts:create --json ./examples/devto-article-title-tags.jsonSchedule a markdown article with title and tags
openquok posts:create --json ./examples/devto-series.jsonSchedule an article in a Dev.to series
openquok posts:create --json ./examples/devto-canonical.jsonSyndicate an article with a canonical URL
openquok posts:create --json ./examples/devto-organization.jsonPublish to an organization with cover image settings
openquok integrations:trigger "$DEVTO_ID" tagsList Dev.to tags for autocomplete
openquok integrations:trigger "$DEVTO_ID" organizationsList organizations you can publish as
openquok analytics:platform "$DEVTO_ID" -d 30Pull 30-day Dev.to analytics (page views, reactions, comments)
openquok analytics:post "$POST_ID" -d 7Pull 7-day insights for a published Dev.to article
Where you chat
ChatGPT, Slack, Teams, and plugins
Dots meet you on the surfaces you already use. Install openquok-core through plugins on the dot cloud computer:
ChatGPT
Desktop, web, and mobile — create your dot and inspect its cloud computer
Slack
Message your dot in Slack with shared context from ChatGPT
Microsoft Teams
Continue projects in Teams without re-explaining context
Plugins
Connect apps and register openquok-core on the dot computer
Cloud computer
Browser, filesystem, and shell your dot uses for finished work
Activity View
Follow background work and redirect your dot when plans change
Optional MCP in editors
Cursor MCP
Optional OpenQuok MCP when you schedule from the IDE instead of your dot
Beyond Dev.to: Every Supported Platform for Dots
Start with Dev.to, then schedule every other network from Dots.
- Facebook Schedule Facebook from Dots.
- Threads Schedule Threads from Dots.
- Instagram Schedule Instagram from Dots.
- YouTube Schedule YouTube from Dots.
- TikTok Schedule TikTok from Dots.
- LinkedIn Schedule LinkedIn from Dots.
- X Schedule X from Dots.
- Bluesky Schedule Bluesky from Dots.
- Dev.to Schedule Dev.to from Dots.You're here
Autonomous agents & MCP
Beyond Dots: Every Supported Agent
Open the landing page for another autonomous agent or MCP client. Compare setup steps, supported channels, and scheduling workflows beside Dots.
Autonomous agents
OpenClaw
Schedule Dev.to from OpenClaw with openquok-core skills and CLI examples.
Hermes Agent
Schedule Dev.to from Hermes Agent with openquok-core skills and CLI examples.
Grok Bot
Schedule Dev.to from Grok Bot with openquok-core skills and CLI examples.
You're here
Dots
Schedule Dev.to from Dots with openquok-core skills and CLI examples.
Meta Muse
Schedule Dev.to from Meta Muse with openquok-core skills and CLI examples.
ThinkRail
Schedule Dev.to from ThinkRail with openquok-core skills and CLI examples.
Manus
Schedule Dev.to from Manus with openquok-core skills and CLI examples.
MCP clients
Antigravity CLI
Draft and schedule Dev.to with MCP tools from Antigravity CLI.
ChatGPT
Draft and schedule Dev.to with MCP tools from ChatGPT.
Codex
Draft and schedule Dev.to with MCP tools from Codex.
Cursor
Draft and schedule Dev.to with MCP tools from Cursor.
Claude Code
Draft and schedule Dev.to with MCP tools from Claude Code.
Claude Cowork
Draft and schedule Dev.to with MCP tools from Claude Cowork.
VS Code / Copilot
Draft and schedule Dev.to with MCP tools from VS Code / Copilot.
Devin Desktop
Draft and schedule Dev.to with MCP tools from Devin Desktop.
Amp
Draft and schedule Dev.to with MCP tools from Amp.
Warp
Draft and schedule Dev.to with MCP tools from Warp.
Muse Code
Draft and schedule Dev.to with MCP tools from Muse Code.
Frequently asked questions
Dots + Dev.to,answered
What Dots is, how to install openquok-core, scheduling Dev.to posts, human approval, and Dev.to setup questions.
Dots are always-on OpenAI agents with their own cloud computer, browser, and plugin ecosystem. You create a dot in ChatGPT, message it from desktop, mobile, Slack, or Teams, and set Custom Rules for approvals. See Dots + OpenQuok and OpenAI's Introducing dots overview.
Dots can run openquok-core on a persistent cloud computer with proactive background work. ChatGPT MCP connects OpenQuok inside a chat session via a custom connector — better for ad hoc questions, not long-running scheduling on the dot computer. Many teams use both.
Choose Grok Bot for many xAI teammates on one shared cloud desktop. Choose OpenClaw for self-hosted Telegram, WhatsApp, or Slack on your hardware. Choose Dots when you live in ChatGPT, Slack, or Teams and want OpenAI-managed cloud computers. See the Grok Bot vs OpenClaw guide for scenario guidance.
Dots roll out on eligible ChatGPT Pro, Business Premium, and Enterprise plans (workspace admins enable Enterprise). OpenQuok billing is separate — you still need a workspace and connected channels on Pricing.
Install @openquok/auto-cli on the dot cloud computer, fetch SKILL.md, and register openquok-core through plugins. Follow the Dots agent guide.
The CLI and auth files live on the dot cloud computer — not in Slack or Teams message history. Use OAuth device flow or a programmatic opo_ token on that computer. See OAuth2 for apps and Public API docs.
Draft and schedule posts, upload media, configure plugs, and pull analytics across connected channels. See supported channels and CLI post commands.
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.
OpenQuok offers a 7-day free trial on Pricing. Dots access depends on your ChatGPT plan eligibility — add openquok-core on the dot computer and connect channels in OpenQuok.
Yes. OpenQuok offers one 7-day free trial per payment customer so you can run social media accounts on auto-pilot before you subscribe the plan. Create an account and start today — no credit card required. Canceling and resubscribing, or creating another workspace, does not grant a second trial. Plan limits are on Pricing and in the billing limits guide; trial rules are in the Cloud trial guide.
Connect channels, write in Creating posts, then pick a time on the calendar or kanban. Agents can use the CLI, agent setup guides, or MCP setup guides.
Sign up for free, open a workspace, and choose Add Channel → Dev.to. Paste an API key from DEV Settings → Extensions. OpenQuok keeps the key on the server so it can publish for you; list and connect APIs never return it. Treat the key like a password — if it leaks, rotate it in DEV Settings and reconnect. See the connect channels guide. For self-hosted deployments, see the self-host Dev.to setup guide.
Yes. Use our post editor — the body is sent as markdown. Title, tags, cover, organization, series, and canonical URL live in Dev.to settings, not in a separate markdown editor. See editor by platform and Dev.to API settings.
Dev.to allows at most four tags. OpenQuok loads tag suggestions from the connected account when available, or you can type names freely. Title must be at least two characters before you can schedule. See Dev.to API settings and Dev.to CLI examples.
Yes. Attach an optional cover (recommended 1000×420) from the media library, and pick an organization if your account publishes for one. Personal profile is the default when no organization is selected. Design covers in the Dev.to photo editor.
Yes. Enter a free-text series name in Dev.to settings (or pass series in providerSettings). Dev.to creates the series if it does not already exist. See Dev.to API settings.
Yes. Set Canonical URL in Dev.to settings (or pass canonical in providerSettings). OpenQuok sends that URL with the article so Dev.to can point at the original. See Dev.to API settings and Dev.to CLI examples.
Yes. Connect Dev.to in our web dashboard with an API key, then follow MCP setup guides (ask your assistant in chat to list integrations and queue posts), CLI setup guides, the create-post API, or Dev.to CLI examples. Pass title, tags, series, cover, and canonical URL in provider settings.
Yes. Workspace analytics show account-level page views, reactions, and comments over 7, 30, or 90 days, plus per-article insights for published posts. Follow-up comments on Dev.to articles are not supported today. Pull metrics from the analytics CLI.
Yes. Connect Dev.to in our web dashboard with an API key, schedule articles, and explore API access during the cloud free trial before upgrading to a paid plan that matches your channel and workspace limits. Plan details are on Pricing for a free tier, or self-host OpenQuok you run yourself.
A channel is one connected social account (Facebook, Instagram, LinkedIn, TikTok, YouTube, Threads, and more). Connect channels in the dashboard. Browse networks on Supported channels.
Read the Dots setup guide
Step-by-step self-host setup for connecting OpenQuok to Dots — install commands, auth patterns, and configuration snippets.
Start free. Publish with confidence.
Connect your agent, review every draft, and schedule posts across channels before anything goes live.