OpenQuok Core
Schedule and manage social posts with the openquok CLI — authenticate, upload media, create drafts and scheduled post…
OpenQuok Schedule Dev.to from Rakazo then you approve
Use Rakazo with openquok-core to draft and schedule Dev.to posts. 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 bot team
Message Rakazo from desktop mobile or Slack
Ask a bot to draft and schedule like any other teammate chat. The openquok-core skill runs in its sandbox. It lists 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 Rakazo
Who schedules Dev.to with Rakazo?
Engineers & indie hackers
Ship changelogs and tutorials from the calendar, not the Dev.to editor. Message Rakazo to draft Dev.to posts. Approve on OpenQuok.
Developer relations
Batch docs and release notes with tags, series, and covers. Review on kanban before publish. Schedule Dev.to at volume through Rakazo. Your team approves on OpenQuok.
Agencies & technical blogs
Connect client accounts with an API key. Pipe markdown drafts via API or MCP. Run Rakazo per client. Dev.to workspaces stay separate.
Connect once
authenticate on the bot computer pick your workspace chat from Slack securely
Run OAuth device login on the bot sandbox once. Credentials stay on your server. Message from desktop 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.to review drafts on the kanban board before 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
—
- 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 reactions and 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 7Backlinks, Playbooks & Building Blocks
Dev.to viral formats
Mix Dev.to-focused backlink guides, playbooks, skills, and MCP servers — then tailor them to your Rakazo 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 Rakazo
Typical social scheduler SaaS
- Copy posts between your AI chat and a separate scheduling tool
- Vendor cloud computers that hold your credentials offsite
- Always-on integrations that bloat agent context
- Locked to one vendor's models or automation layer
- Autopilot publishing with no human checkpoint
OpenQuok + Rakazo
- Message Rakazo from desktop, mobile, or Slack to draft and schedule
- Sandboxes run on infrastructure you control — workspace isolated per bot
- Skills and MCP load on demand — keep chat context clean
- Bring your own model keys; CLI-first openquok-core beside any other skill
- 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
Web, desktop, mobile, and Slack
Rakazo bots keep persistent sandboxes. Message them from the web app, Electron desktop, Expo mobile, or Slack when your operator enables messaging:
Web app
Browser UI for bots, routines, and approvals
Desktop
Electron app for macOS, Windows, and Linux
Mobile
iOS and Android clients for your Rakazo server
Slack
Mention a bot in your workspace channel
Telegram
Self-hosted bot bridge when you configure it
Bot computer
Isolated browser, shell, and files per bot
MCP & integrations (optional)
MCP
User-installed HTTPS MCP servers from Integrations
Self-hosted messaging when your operator enables it
Beyond Dev.to: Every Supported Channel for Rakazo
Start with Dev.to, then schedule other networks and launch on directories from Rakazo.
- Facebook Schedule Facebook from Rakazo.
- Instagram Schedule Instagram from Rakazo.
- Threads Schedule Threads from Rakazo.
- YouTube Schedule YouTube from Rakazo.
- TikTok Schedule TikTok from Rakazo.
- LinkedIn Schedule LinkedIn from Rakazo.
- X Schedule X from Rakazo.
- Bluesky Schedule Bluesky from Rakazo.
- Reddit Schedule Reddit from Rakazo.
- Dev.to Schedule Dev.to from Rakazo.You're here
- Skool Schedule Skool from Rakazo.
- PeerPush Launch on PeerPush from Rakazo.
- Uneed Launch on Uneed from Rakazo.
Autonomous agents & MCP
Beyond Rakazo: Every Supported Agent
Open the landing page for another autonomous agent or MCP client. Compare setup steps, supported channels, and scheduling workflows beside Rakazo.
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.
Dots
Schedule Dev.to from Dots with openquok-core skills and CLI examples.
Gemini Task
Schedule Dev.to from Gemini Task with openquok-core skills and CLI examples.
Claude Duet
Schedule Dev.to from Claude Duet with openquok-core skills and CLI examples.
Meta Muse
Schedule Dev.to from Meta Muse with openquok-core skills and CLI examples.
Manus
Schedule Dev.to from Manus with openquok-core skills and CLI examples.
ThinkRail
Schedule Dev.to from ThinkRail with openquok-core skills and CLI examples.
You're here
Rakazo
Schedule Dev.to from Rakazo with openquok-core skills and CLI examples.
MCP clients
Antigravity CLI
Draft and schedule Dev.to with MCP tools from Antigravity CLI.
Android Studio
Draft and schedule Dev.to with MCP tools from Android Studio.
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.
Grok Build
Draft and schedule Dev.to with MCP tools from Grok Build.
Frequently asked questions
Rakazo + Dev.to answered
What Rakazo is, how to install openquok-core, scheduling Dev.to posts, human approval, and Dev.to setup questions.
Rakazo is an open-source platform for persistent AI teammates with isolated computers, memory, and routines. You self-host the API and worker, connect your own model keys, and message bots from web, desktop, mobile, or Slack. See the Rakazo integration and agent setup guides.
Choose Rakazo when you want self-hosted persistent bots with sandboxed computers and your own model keys. Choose Grok Bot when you prefer a managed xAI cloud desktop without operating a server. Choose OpenClaw or Hermes Agent for gateway-first Telegram or WhatsApp setups. See the Grok Bot vs OpenClaw guide.
Choose Grok Bot when you want a managed xAI cloud desktop with Cursor, iOS, and plugin installs — no API server, worker, or database to operate. Choose Rakazo when you need Apache-2.0 source, self-hosted sandboxes, and your own model keys. Both pair with openquok-core for scheduling; see the agent host comparison guide.
Install @openquok/auto-cli on the bot sandbox, save SKILL.md as a bot skill, and authenticate once. Optional: add OpenQuok as an HTTPS MCP server under Integrations. See the Rakazo agent guide.
The global CLI and auth files live on the bot sandbox — the same environment where openquok-core runs shell commands. Tokens stay off chat threads; use OAuth device flow or a programmatic opo_ token on that computer. See OAuth2 for apps and Public API docs.
Rakazo 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 Rakazo + Dev.to and the Dev.to humanizer tool for channel-specific workflows.
A cloud browser can click through sites, but it is a poor fit for a social calendar. Do not put social passwords or payment details in Rakazo chat. Scripted logins often hit captchas and can break platform rules.
OpenQuok connects each channel once with OAuth or app credentials and publishes through official APIs. Tokens stay encrypted on our servers. You still message Rakazo to draft and queue; you approve on the calendar or kanban before anything goes live. See the connect channels guide.
Connect your Dev.to account via the Dev.to setup guide or the Dev.to channel landing. Install openquok-core on Rakazo with the Rakazo agent guide. Message your assistant to schedule — Rakazo 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 Rakazo 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 Rakazo 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 sandbox. MCP fits ad hoc tool calls from Integrations — see MCP setup. Many teams use both.
OpenQuok offers a 7-day free trial on Pricing. Rakazo software is Apache-2.0 — you pay for your own server and model usage. Install Rakazo, add openquok-core, and begin scheduling from 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. From Chrome, install Add to Chrome, it's free and draft from the browser extension side panel without opening the dashboard every time.
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.
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.
Read the Rakazo setup guide
Step-by-step self-host setup for connecting OpenQuok to Rakazo — 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.