OpenQuok Core
Schedule and manage social posts with the openquok CLI — authenticate, upload media, create drafts and scheduled post…
OpenQuok Schedule Threads from Meta Muse then you approve
Message Meta Muse from Telegram, WhatsApp, or Slack. Add the openquok-core skill so it schedules Threads 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 Meta Threads with Meta Muse
Who schedules Threads with Meta Muse?
Creators & founders
Stay consistent on Threads without daily manual posting. Ask your agent to schedule, reply, and repost while you focus on building. Message Meta Muse to draft Threads posts from chat — publish now, schedule, or approve on OpenQuok.
Social managers
Batch a week of Threads. Review drafts before they publish. Track engagement alongside your other channels. Meta Muse queues Threads drafts at volume — your team can publish now or approve first.
Developers & agents
Pipe Threads drafts from your backend via the public API, CLI, or MCP. Configure Thread-specific settings such as follow-up replies. Run Meta Muse per client workspace so Threads 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.
71 / 500
Follow-up comments
Reply
Drag and drop images or videos here, or use the icons on the editor.
39/500
Delay
09:00 + 300s ≈ 09:05:00
Post Preview
OpenQuok Brand OpenQuok Brand
Jun 12, 9:00 AM
Ship the company thread — a personal profile can comment after publish.
Scheduled thread replies
- OpenQuok BrandAfter 5 min
Each reply runs after your chosen delay
Post editor
Attach media to Threads postsqueue follow-up replies with delaysbefore go-live
Compose within the 500-character limit. Attach a single image, a carousel, or a video. Queue same-account follow-up replies before the main thread goes live. Preview the full thread from one draft.
CLI command options (Secure VM)
# Draft + human checklist (Threads)
openquok posts:create --json ./examples/threads-text-only.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
4,401
1 channel
Engagement
800
1 channel
Followers
—
09/25 10/01
- OpenQuok Brand (Views)
Views
Threads OpenQuok Brand
11.2%
4,401
Likes
Threads OpenQuok Brand
9.1%
800
Replies
Threads OpenQuok Brand
6.4%
243
Reposts
Threads OpenQuok Brand
4.8%
114
Quotes
Threads OpenQuok Brand
3.5%
64
Insights
See what resonates on Threads track views and engagementand iterate
Threads analytics—Trends summary totals and per-profile views, likes, replies, reposts, and quotes. Then schedule more of what already works.
CLI analytics options
# Threads platform metrics
INTEGRATION_ID=$(openquok integrations:list | jq -r '.[] | select(.identifier=="threads") | .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
Threads viral formats
Mix Threads-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 Threads 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
Threads 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=="threads") | .id'Discover your Threads integration UUID
openquok integrations:settings "$THREADS_ID"Get Threads posting rules and character limits
openquok posts:create --json ./examples/threads-text-only.jsonSchedule a text-only Threads post
openquok posts:create --json ./examples/threads-follow-up-replies.jsonSchedule a post and follow-up replies
openquok posts:create --json{ "scheduledAt": "2026-01-01T12:00:00.000Z", "status": "scheduled", "body": "Thread 1/2: Why we built this", "integrationIds": ["<integration-id>"], "providerSettingsByIntegrationId": { "<integration-id>": { "threads": { "replies": [ { "id": "reply-1", "message": "Thread 2/2: Architecture diagram", "delaySeconds": 60, "media": [{ "id": "<reply-media-id>", "path": "https://cdn.example.com/reply.jpg" }] } ] } } } }Schedule a follow-up reply with image or video on threads.replies
openquok posts:create --json{ "scheduledAt": "2026-01-01T12:00:00.000Z", "status": "scheduled", "body": "Main thread from channel A", "integrationIds": ["<integration-id-1>"], "providerSettingsByIntegrationId": { "<integration-id-1>": { "threads": { "crossAccountPlugs": [ { "plugName": "threads-cross-account-comment", "enabled": true, "delayMs": 120000, "integrationIds": ["<integration-id-2>"], "fields": { "comment": "Great thread — sharing from our other account." } } ] } } } }Comment from another Threads channel after publish (crossAccountPlugs)
openquok posts:create --json{ "scheduledAt": "2026-01-01T12:00:00.000Z", "status": "scheduled", "body": "Big announcement! 🧵", "integrationIds": ["<integration-id>"], "providerSettingsByIntegrationId": { "<integration-id>": { "threads": { "internalEngagementPlug": { "enabled": true, "message": "Have questions? Reply here and I will get back to you.", "delaySeconds": 300 } } } } }Same-account delayed engagement reply (internalEngagementPlug)
openquok plugs:catalog | jq '.plugs[] | select(.identifier=="threads")'List global plug types and field names for this provider
openquok plugs:list "$ID"List saved global plug rules on this channel
openquok plugs:upsert "$ID" --func autoPlugPost --fields '[{"name":"likesAmount","value":"100"},{"name":"post","value":"Thanks for reading!"}]'Auto-reply when a thread reaches a likes threshold (global plug)
openquok analytics:platform "$THREADS_ID" -d 30Pull 30-day Threads analytics
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 Threads: Every Supported Platform for Meta Muse
Start with Threads, then schedule every other network from Meta Muse.
- Facebook Schedule Facebook from Meta Muse.
- Threads Schedule Threads from Meta Muse.You're here
- 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.
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 Threads from OpenClaw with openquok-core skills and CLI examples.
Hermes Agent
Schedule Threads from Hermes Agent with openquok-core skills and CLI examples.
Grok Bot
Schedule Threads from Grok Bot with openquok-core skills and CLI examples.
Dots
Schedule Threads from Dots with openquok-core skills and CLI examples.
You're here
Meta Muse
Schedule Threads from Meta Muse with openquok-core skills and CLI examples.
ThinkRail
Schedule Threads from ThinkRail with openquok-core skills and CLI examples.
Manus
Schedule Threads from Manus with openquok-core skills and CLI examples.
MCP clients
Antigravity CLI
Draft and schedule Threads with MCP tools from Antigravity CLI.
ChatGPT
Draft and schedule Threads with MCP tools from ChatGPT.
Codex
Draft and schedule Threads with MCP tools from Codex.
Cursor
Draft and schedule Threads with MCP tools from Cursor.
Claude Code
Draft and schedule Threads with MCP tools from Claude Code.
Claude Cowork
Draft and schedule Threads with MCP tools from Claude Cowork.
VS Code / Copilot
Draft and schedule Threads with MCP tools from VS Code / Copilot.
Devin Desktop
Draft and schedule Threads with MCP tools from Devin Desktop.
Amp
Draft and schedule Threads with MCP tools from Amp.
Warp
Draft and schedule Threads with MCP tools from Warp.
Muse Code
Draft and schedule Threads with MCP tools from Muse Code.
Frequently asked questions
Meta Muse + Threads,answered
What Meta Muse is, how to install openquok-core, scheduling Threads posts, human approval, and Threads 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 Connect channel → Threads. Complete Meta OAuth and OpenQuok links the profile to that workspace. OpenQuok Cloud registers the Meta app for you. For self-hosted deployments, see the self-host Threads setup guide.
On OpenQuok Cloud, you connect Threads with Add channel. You do not submit operator business verification for OpenQuok's Meta app. If you self-host, you use your own Meta developer app. Meta often requires business verification and App Review before Live publishing. See Meta business verification guide, OpenQuok Cloud, and the connect channels guide.
Yes. Attach one image or video, or multiple files for a carousel, when composing a Threads post in OpenQuok. In per-platform mode, unsupported formats (such as SVG) are blocked early with a clear error before publish. See media rules by platform and the Threads photo editor.
Yes. The post editor shows the 500-character cap and prevents publishing from the dashboard. Scheduled posts via the API or CLI are rejected when the main caption or any follow-up reply exceeds 500 characters. Saving as drafts can store longer copy. Tighten cross-posted copy in the Threads humanizer tool.
Yes. Connect Threads in our web dashboard, then follow MCP setup guides (ask your assistant in chat to list integrations and queue posts), CLI setup guides, the create-post API, or Threads CLI examples. Follow-up replies and Thread-specific settings can also be configured by asking agent in chat.
Yes. Write once in OpenQuok and publish the same idea to Threads, Instagram, X, LinkedIn, TikTok, YouTube, and other connected channels from one workflow. Per-platform captions, aspect ratios, and character limits are applied separately, so each destination gets tailored copy from a single schedule. See Supported channels.
OpenQuok includes auto-repost and recurring schedule slots, so you can recycle evergreen Threads posts on intervals from one day up to one month. Combine it with the media library to keep reusing your best-performing images, videos, and captions without rebuilding posts from scratch. See repeating a post and calendar guide.
Yes. Add follow-up replies in the composer (or pass threads.replies via the API or CLI). Each reply publishes from the same account after the delay you set once the main post goes live. See Threads CLI examples.
Yes. Open channel Settings on the publishing Threads channel, enable Add comments by other accounts, select another connected Threads profile, and set comment text plus delay. OpenQuok publishes the main thread first, then posts the cross-account comment from the acting account. See Cross-account plugs or Threads CLI examples for crossAccountPlugs.
Yes. Connect Threads in our web dashboard, schedule posts, 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.