OpenQuok Core
Schedule and manage social posts with the openquok CLI — authenticate, upload media, create drafts and scheduled post…
OpenQuok Schedule Dev.to from Meta Muse then you approve
Message Meta Muse 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:
Create a custom connector for OpenQuok using the public API spec at https://www.openquok.com/api/v1/openapi.json. Do not publish anything yet. First list my connected social accounts and the available scheduling operations.Your everyday agent
Message Meta Muse from phonewebor WhatsApp
Ask Muse to list connected channels, draft platform-specific copy, and queue schedules through OpenQuok. You can publish now, schedule for later, or save drafts and approve on OpenQuok when you are ready.
Built for technical writers with Meta Muse
Who schedules Dev.to with Meta Muse?
Engineers & indie hackers
Ship changelogs and tutorials from the calendar, not the Dev.to editor. Message Meta Muse 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. Meta Muse 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 Meta Muse per client workspace so Dev.to drafts stay isolated.
Connect once
store credentials in Musepick your workspacechat from anywhere securely
Use Muse secure credential storage for your OpenQuok API key. Choose a workspace, validate connected channels, and draft from mobile or web without opening another scheduling tab.
Public API authentication
# Programmatic token (Authorization header)
export OPENQUOK_API_KEY=opo_your_programmatic_token
# Custom connector: give Muse the OpenAPI URL
# https://www.openquok.com/api/v1/openapi.jsonCreate 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 (Secure VM)
# 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 7Scale what works
when a format hits, scale by adding workspaces and parallel tasks
Spot a winner in analytics, then spin up another workspace for the next client or brand while Muse queues the next wave — credentials, channels, and drafts 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 30Playbooks & Building Blocks Directories
Dev.to viral formats
Mix Dev.to-focused skills, and MCP servers — then tailor them to your Meta Muse 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 Meta Muse
Typical social scheduler SaaS
- Copy posts between your AI chat and a separate scheduling tool
- No first-party Muse connector for every SaaS on day one
- API keys pasted into chat history
- Autopilot publishing with no human checkpoint
- One workspace mixing every client as you add channels
- Terminal coding agents mixed up with consumer Muse
OpenQuok + Meta Muse
- Message Meta Muse to draft and schedule through OpenQuok
- Custom connectors from the public OpenAPI document Meta documents for APIs
- Store OpenQuok tokens in Muse secure credential prompts
- You choose publish-now, schedule, or draft — approve on OpenQuok when you want a review step
- Multi-workspace isolation — scoped API keys per brand so drafts never cross wires
- Clear split: Meta Muse here; Muse Code MCP setup lives on its own integration page
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
Mobile, web, and connectors
Meta Muse meets you on the devices you already use. OpenQuok connects through custom connectors, the public API, CLI in the Secure VM, or hosted MCP when your environment supports it:
iOS
Message Muse from iPhone or iPad
Android
Use Muse on Android phones and tablets
muse.ai
Chat in the browser at meta.ai
Reach Muse from WhatsApp when Meta enables it for your account
Secure VM
Muse runs tasks in an isolated environment with a terminal and filesystem
Secure credentials
Store API keys in Muse credential prompts — not in ordinary chat
OpenQuok surfaces
Custom connector
Muse can wire OpenQuok from your public OpenAPI document
Public API
REST endpoints for accounts, drafts, schedules, and publishing
openquok CLI
Shell commands inside the Secure VM when you install the skill
Hosted MCP
Use OpenQuok MCP when your Muse environment exposes MCP configuration
Beyond Dev.to: Every Supported Platform for Meta Muse
Start with Dev.to, then schedule every other network from Meta Muse.
- Facebook Schedule Facebook from Meta Muse.
- Threads Schedule Threads from Meta Muse.
- Instagram Schedule Instagram from Meta Muse.
- YouTube Schedule YouTube from Meta Muse.
- TikTok Schedule TikTok from Meta Muse.
- LinkedIn Schedule LinkedIn from Meta Muse.
- X Schedule X from Meta Muse.
- Bluesky Schedule Bluesky from Meta Muse.
- Dev.to Schedule Dev.to from Meta Muse.You're here
Autonomous agents & MCP
Beyond Meta Muse: Every Supported Agent
Open the landing page for another autonomous agent or MCP client. Compare setup steps, supported channels, and scheduling workflows beside Meta Muse.
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.
You're here
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
Meta Muse + Dev.to,answered
What Meta Muse is, how to install openquok-core, scheduling Dev.to posts, human approval, and Dev.to setup questions.
Meta Muse is Meta's personal AI agent for everyday work — not just Q&A. It runs on Muse Secure VM, can use a browser on your behalf, and chats like messaging in the Muse app or WhatsApp. It is powered by Muse Spark for agentic tasks. US rollout includes iOS, Android, and muse.ai. Overview: https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/. See the Meta Muse integration and agent guide.
Muse Secure VM is a dedicated cloud computer for one person's Muse. It holds connected app data and credentials in isolated storage. Muse asks before sensitive actions like email or purchases. OpenQuok fits the same pattern: schedule posts as drafts, then you approve on OpenQuok before anything goes live.
Yes. Muse can continue long tasks after you close the app and return when it needs input or when something changes. Pair that with OpenQuok so Muse queues social drafts while you focus elsewhere — publishing still waits for your calendar or kanban approval.
Yes — when your OpenQuok workspace has Facebook or Instagram connected. Ask Muse to call OpenQuok through a custom connector or openquok-core in the Secure VM. Muse drafts and queues posts; you approve on OpenQuok before anything publishes to your Page or professional account. See supported channels.
No. Meta Muse is the personal agent product for everyone. Muse Code is Meta's terminal coding agent for developers on macOS and Linux. Muse Code connects to OpenQuok over MCP in ~/.config/muse/settings.json — see the Muse Code MCP guide. Consumer Muse and Muse Code are separate subscriptions and apps.
Not as a pre-reviewed directory connector on day one. Meta says you can ask Muse to create a custom connector when a service exposes an API. OpenQuok publishes a public OpenAPI document and REST API so Muse can wire scheduling without a separate adapter.
Create a programmatic token under Developers → Access in your OpenQuok workspace. When Muse asks for credentials, use its secure credential prompt — do not repeat the key in normal chat. API requests use the Authorization header with your opo_ token. See Public API docs.
Start with a custom connector and the OpenAPI URL when you use consumer Muse in chat. Install openquok-core in the Secure VM when you want shell workflows. Use hosted MCP when your Muse environment exposes MCP configuration — same tools as other MCP clients.
List connected channels, inspect publishing rules, draft and schedule posts, upload media, and pull analytics. See supported channels and CLI post commands.
It depends on you. You can ask Muse 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 Muse to use draft-only or not to publish when you want a review step first.
Muse stores connector secrets in its secure credential store. When you use the CLI path, auth files live inside the Secure VM — not on your phone chat history. Rotate tokens from OpenQuok Developers → Access if you revoke access.
OpenQuok offers a 7-day free trial for scheduling on Pricing. Meta Muse access depends on Meta's plans for your region — connect OpenQuok once your Muse account is active.
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 Meta Muse setup guide
Step-by-step self-host setup for connecting OpenQuok to Meta Muse — 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.