Schedule Threads from ThinkRail then you approve

Message ThinkRail 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
Get Started For Free Get Started For Free

Install our core skill:

Your worktree IDE

Chat with pi in ThinkRail,keep main clean

Open a repo. Cut a workspace worktree. Ask the agent to draft and schedule like any other task. The openquok-core skill runs in that worktree’s shell. It finds connected channels, attaches media, and queues drafts. You approve on the calendar before anything publishes.

Built for Meta Threads with ThinkRail

Who schedules Threads with ThinkRail?

Creators & founders

Stay consistent on Threads without daily manual posting. Ask your agent to schedule, reply, and repost while you focus on building. Message ThinkRail to draft Threads posts from chat — you approve before publish.

Social managers

Batch a week of Threads. Review drafts before they publish. Track engagement alongside your other channels. ThinkRail queues Threads drafts at volume — your team approves before publish.

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 ThinkRail per client workspace so Threads drafts stay isolated.

How it works

Five steps,to ThinkRail + OpenQuok

New to OpenQuok? Read the agent setup guide

Connect once

authenticate in the worktreepick your workspacechat from the IDE securely

Choose an OpenQuok workspace, connect with OAuth2 — approve in your browser, and credentials stay on the machine that runs ThinkRail. Ask the agent 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

Views
11.2%
4,935
Likes
9.1%
767
Replies
6.4%
262
Reposts
4.8%
126
Quotes
3.5%
95

Insights

See what resonates on Threads track views and engagementand iterate

Track views, likes, replies, reposts, and quotes from connected Threads profiles inside OpenQuok analytics. Then schedule more of what already works.

CLI analytics options

Scale what works

when a format hits, scale by adding worktrees and parallel chats

Spot a winner in analytics, then cut another worktree for the next client or brand while a second pi session queues the next wave — credentials, channels, and agent context stay isolated 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 ThinkRail workflow.

Playbooks

Skill Builder

Build and export a Threads SKILL.md from building blocks.

See All

Browse every Threads playbook.

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 ThinkRail

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 working tree mixing every experiment as you add channels and parallel sessions
  • Autopilot publishing with no human checkpoint

OpenQuok + ThinkRail

  • > Ask the agent in ThinkRail to draft and schedule from the worktree
  • > Credentials stay on the machine that runs ThinkRail — workspace isolated
  • > Skills load on demand from ~/.pi or the worktree .pi/skills folder
  • > CLI-first openquok-core works beside any other pi skill or extension
  • > Git worktrees isolate each line of work — merge the good branch, delete the rest
  • > Every post lands as draft or scheduled — you approve before anything goes live

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

Worktrees, editor, and terminals

ThinkRail scopes files, diffs, terminals, and pi chats to the active git worktree — then invoke openquok-core like any other skill:

macOS

CLI or desktop build on Apple Silicon

Linux

CLI or desktop on arm64 and x64

Windows

CLI or desktop build for Windows x64

Git worktrees

Each workspace is its own branch and cwd

Monaco editor

Tabs, files tree, and live diffs per worktree

Worktree terminals

PTYs scoped to the active workspace cwd

Optional MCP extensions

Pi MCP extensions

Optional MCP tools beside skills — OpenQuok stays CLI-first

Beyond Threads: Every Supported Platform for ThinkRail

Start with Threads, then schedule every other network from ThinkRail.

Frequently asked questions

ThinkRail + Threads,answered

What ThinkRail is, how to install openquok-core, scheduling Threads posts, human approval, and how agents draft from chat.

Read the ThinkRail setup guide

Step-by-step self-host setup for connecting OpenQuok to ThinkRail — 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.

Start for $0
Discord Support