Schedule Threads from Manus then you approve

Message Manus from Telegram, WhatsApp, or Slack. Add the openquok-core skill so it schedules Threads posts while you review on the calendar or kanban.

Install our core skill:

Your Manus project

Chat in Manus,keep skills portable

Ask Manus to draft and schedule like any other task. The openquok-core skill runs openquok in your Cloud Computer or local shell. 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 Meta Threads with Manus

Who schedules Threads with Manus?

Creators & founders

Stay consistent on Threads without daily manual posting. Ask your agent to schedule, reply, and repost while you focus on building. Message Manus 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. Manus 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 Manus per client workspace so Threads drafts stay isolated.

How it works

Five steps,to Manus + OpenQuok

New to OpenQuok? Read the agent setup guide

Connect once

authenticate on the Cloud Computerpick your workspacechat from Manus securely

Choose an OpenQuok workspace, connect with OAuth2 — approve in your browser, and credentials stay on the machine that runs openquok. Ask Manus in chat to draft and schedule without opening another app.

CLI authentication options

Create 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 Brand
    After 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

Targeted channels

Overview

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

Scale what works

when a format hits, scale with parallel Manus sessions

Spot a winner in analytics, then spin another project or Automation while a second chat queues the next wave — credentials and channels stay scoped per workspace as you scale.

Parallel CLI sessions

Playbooks & Building Blocks Directories

Threads viral formats

Mix Threads-focused skills, and MCP servers — then tailor them to your Manus workflow.

Building Blocks

OpenQuok Core

Schedule and manage social posts with the openquok CLI — authenticate, upload media, create drafts and scheduled post…

See All

Browse every Threads building block.

comparisons

agent-native scheduling, not another dashboard

Most social scheduler SaaS keeps you in a browser tab. OpenQuok is built for Threads from Manus

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-off prompts that forget how you schedule each channel
  • Autopilot publishing with no human checkpoint

OpenQuok + Manus

  • > Ask Manus to draft and schedule from the same project chat
  • > Credentials stay on the Cloud Computer or shell that runs openquok
  • > Skills load on demand — import once, invoke with / when you need scheduling
  • > CLI-first openquok-core works beside any other Manus skill or connector
  • > SKILL.md keeps channel rules and CLI examples in a portable package
  • > You choose publish-now, schedule, or draft — approve on OpenQuok when you want a review step

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.json

    Schedule a text-only Threads post

  • openquok posts:create --json ./examples/threads-follow-up-replies.json

    Schedule 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 30

    Pull 30-day Threads analytics

Where you work

Studio, web, mobile, and Skills

Manus runs across Studio, browser, and mobile apps — import skills once, then invoke openquok-core with / in chat or from Automations:

Manus Studio

Desktop workspace for documents, code, and long-running projects

Web app

Run tasks from manus.im in the browser

Mobile

Continue projects from iOS or Android apps

Skills

Import or upload openquok-core, then invoke it with / in chat

Cloud Computer

Dedicated environment with browser, filesystem, and terminal

Automations

Event-triggered workflows beside scheduled tasks

Connectors (optional)

Connectors

Optional integrations when your project needs external services

Autonomous agents & MCP

Beyond Manus: Every Supported Agent

Open the landing page for another autonomous agent or MCP client. Compare setup steps, supported channels, and scheduling workflows beside Manus.

Frequently asked questions

Manus + Threads,answered

What Manus is, how to install openquok-core, scheduling Threads posts, human approval, and Threads setup questions.

Read the Manus setup guide

Step-by-step self-host setup for connecting OpenQuok to Manus — install commands, auth patterns, and configuration snippets.

View setup guide

Start free. Publish with confidence.

Connect your agent, review every draft, and schedule posts across channels before anything goes live.

Discord Support