OpenQuok Core
Schedule and manage social posts with the openquok CLI — authenticate, upload media, create drafts and scheduled post…
OpenQuok Schedule Dev.to from Grok Bot then you approve
Message Grok Bot from the macOS, Windows, or iOS app. Add openquok-core on its cloud computer so it drafts and schedules Dev.to posts while you review and approve 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 desktop teammate
Message Grok Bot from macOSWindowsor iOS
Ask your Bot to draft and schedule like any other teammate message. The openquok-core skill runs on its cloud computer. It finds connected channels, 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 Grok Bot
Who schedules Dev.to with Grok Bot?
Engineers & indie hackers
Ship changelogs and tutorials from the calendar, not the Dev.to editor. Message Grok Bot 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. Grok Bot 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 Grok Bot per client workspace so Dev.to drafts stay isolated.
Agent & MCP operators
Schedule Dev.to from OpenClaw, Grok Bot, Cursor, or ChatGPT MCP. Open each agent landing page for Dev.to CLI examples and setup FAQs. Run Grok Bot per client workspace so Dev.to drafts stay isolated.
X as your home network
Grok Bot fits xAI’s cloud computer and many named Bots. X is first-class; connect other networks in OpenQuok when you need them.
Connect once
authenticate on the cloud computerpick your workspacechat from desktop securely
Choose a workspace, connect with OAuth2 — approve in your browser, and credentials stay on the Bot shared computer. Message Grok Bot from desktop or iOS to draft and schedule without opening another app.
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/30 10/06
- 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 by adding workspaces and parallel Bots
Spot a winner in analytics, then spin up another workspace for the next client or brand while Grok Bot queues the next wave on its cloud computer — credentials, channels, and agent context stay isolated as you scale.
Parallel CLI sessions
# Workspace A — launch (client brand)
openquok posts:create -c "…" -s "…" -t draft -i "<uuid>"
openquok posts:status <post-id> -s schedule
# Workspace B — another client (isolated credentials)
openquok posts:list --status draft
# Same workspace — metrics in parallel
openquok analytics:platform <integration-uuid> -d 7
openquok analytics:post <post-id> -d 30Backlinks, Playbooks & Building Blocks
Dev.to viral formats
Mix Dev.to-focused backlink guides, playbooks, skills, and MCP servers — then tailor them to your Grok Bot workflow.
comparisons
agent-native scheduling, not another dashboard
Most social scheduler SaaS keeps you in a browser tab. OpenQuok is built for Dev.to from Grok Bot
Typical social scheduler SaaS
- Copy posts between your AI chat and a separate scheduling tool
- Siloed API keys and workflows that do not compose with your agent stack
- Always-on integrations that bloat agent context
- Locked to one vendor's models or automation layer
- One workspace mixing every context as you add channels and parallel sessions
- Autopilot publishing with no human checkpoint
OpenQuok + Grok Bot
- Message Grok Bot from desktop or iOS to draft and schedule
- Credentials stay on the Bot shared cloud computer — workspace isolated
- Skills load on demand via Plugins or / — keep chat context clean
- CLI-first openquok-core works beside any other Bot skill or routine
- Multi-workspace isolation — spin up a workspace per context so channels and drafts never cross wires
- You choose publish-now, schedule, or draft — approve on OpenQuok when you want a review step
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
Desktop, mobile, and plugins
Grok Bot teammates run on a shared cloud computer — message them from macOS, Windows, or iOS, then invoke skills with / in chat or Settings → Plugins:
macOS
Native desktop app for Apple Silicon and Intel Macs
Windows
Desktop app for Windows 10 and 11
iOS
Message your Bot from iPhone or iPad on the go
Plugins
Install skills via Settings → Plugins or / in chat
Routines
Scheduled work on the Bot shared cloud computer
Cloud computer
Persistent browser, filesystem, and terminal for each Bot
Connectors & MCP (optional)
Connectors
Optional MCP connectors for third-party tools
Beyond Dev.to: Every Supported Platform for Grok Bot
Start with Dev.to, then schedule every other network from Grok Bot.
- X Schedule X from Grok Bot.First-class
- Facebook Schedule Facebook from Grok Bot.
- Threads Schedule Threads from Grok Bot.
- Instagram Schedule Instagram from Grok Bot.
- YouTube Schedule YouTube from Grok Bot.
- TikTok Schedule TikTok from Grok Bot.
- LinkedIn Schedule LinkedIn from Grok Bot.
- Bluesky Schedule Bluesky from Grok Bot.
- Dev.to Schedule Dev.to from Grok Bot.You're here
Autonomous agents & MCP
Beyond Grok Bot: Every Supported Agent
Open another autonomous agent or MCP client landing page. Compare xAI Grok Bot workflows, X-first channels, and other hosts beside Grok Bot.
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.
You're here
Grok Bot
Schedule Dev.to from Grok Bot with openquok-core skills and CLI examples.
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
Cursor
Draft and schedule Dev.to with MCP tools from Cursor.
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.
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
Grok Bot + Dev.to,answered
What Grok Bot is, how to install openquok-core, scheduling Dev.to posts, human approval, and Dev.to setup questions.
X is first-class for Grok Bot on OpenQuok. Grok Bot runs on xAI’s cloud computer with many named Bots. Connect other networks when your workflow needs them.
Choose Grok Bot for many named Bots on one xAI cloud desktop without server ops. Choose OpenClaw when you must self-host and message from Telegram, WhatsApp, or Slack. Choose Dots for OpenAI workplace chat. See the Grok Bot vs OpenClaw guide.
Grok Bot is an AI teammate product with a shared persistent cloud computer — browser, filesystem, and terminal — for each Bot you create. You message it from macOS, Windows desktop, or iOS, install skills via Settings → Plugins or / in chat, and set up routines for scheduled work. See the Grok Bot integration and agent setup guides.
Grok Bot requires an eligible subscription such as SuperGrok Heavy, Cursor Ultra, or Cursor Teams Premium. Sign in with your Cursor account when you install the desktop or iOS app. OpenQuok billing is separate — you still need an OpenQuok workspace and connected channels. Plan limits are on Pricing.
Install @openquok/auto-cli on the Bot cloud computer, add openquok-core as a skill, and authenticate once. See the Grok Bot agent guide or the scheduling walkthrough.
The global CLI and auth files live on the Bot shared cloud computer — the same environment where openquok-core runs shell commands. Your OpenQuok workspace tokens never need to be pasted into chat; use OAuth device flow or a programmatic opo_ token on that computer. See OAuth2 for apps and Public API docs for token setup.
Grok Bot can draft and schedule Dev.to posts, upload images and video, apply per-platform settings, and pull platform and post analytics for your connected Dev.to account. The openquok-core skill documents integrations:list, posts:create, posts:status, analytics:platform, upload, and more — every command returns structured JSON for the agent to parse. See Grok Bot + Dev.to and the Dev.to humanizer tool for channel-specific workflows.
Connect your Dev.to account via the Dev.to setup guide or the Dev.to channel landing. Install openquok-core on Grok Bot with the Grok Bot agent guide. Message your assistant to schedule — Grok Bot uses integration UUIDs from openquok integrations:list to target your Dev.to account. Every post lands as a draft or scheduled item until you approve on the calendar or kanban. Browse Dev.to playbooks and Dev.to building blocks for format ideas.
It depends on you. You can ask Grok Bot 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 Grok Bot to use draft-only or not to publish when you want a review step first.
openquok-core is CLI-first for repeatable Bot workflows on the shared cloud computer. MCP fits ad hoc editor tools — see OpenQuok for Cursor or MCP setup. Many teams use both.
Grok Bot is the always-on teammate; Cursor MCP is OpenQuok inside Agent and Composer. Same workspace and approval flow — pick Grok Bot for messaging-first volume or Cursor when you stay in the repo. See the Grok Bot scheduling walkthrough.
OpenQuok offers a 7-day free trial for scheduling on Pricing. Grok Bot access depends on your xAI or Cursor plan eligibility — install the app, create a Bot, add openquok-core, and begin scheduling from desktop chat.
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 Grok Bot setup guide
Step-by-step self-host setup for connecting OpenQuok to Grok Bot — 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.