macOS
CLI or desktop build on Apple Silicon
OPENQUOK Schedule Bluesky from ThinkRail then you approve
Use ThinkRail with openquok-core to draft and schedule Bluesky 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:
mkdir -p ~/.pi/agent/skills/openquok-core
curl -fsSL "https://raw.githubusercontent.com/Ratimon/openquok-monorepo/main/agent/skills/openquok-core/SKILL.md" \
-o ~/.pi/agent/skills/openquok-core/SKILL.mdDraft 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 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 posts. You can publish now, schedule for later, or save drafts and approve on OpenQuok when you are ready.
Built for the open social web with ThinkRail
Who schedules Bluesky with ThinkRail?
Creators & founders
Stay visible on Bluesky without living in the app. Batch posts and reply chains from the calendar. Message ThinkRail to draft Bluesky posts from chat — publish now, schedule, or approve on OpenQuok.
Team & Social managers
Review drafts on kanban as a team. Schedule link posts, images, video, and threaded follow-ups in one workflow. ThinkRail queues Bluesky drafts at volume — your team can publish now or approve first.
Developers
Pipe Bluesky drafts from your backend via the public API or CLI. Mention people with @handle autocomplete. Run ThinkRail per client workspace so Bluesky drafts stay isolated.
Agent operators
Schedule Bluesky posts and reply chains from your agent through MCP. Review drafts on kanban before publish. Run ThinkRail per client workspace so Bluesky drafts stay isolated.
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
# 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
Workspace tools. Sign in or sign up to use your library, Photo Editor, and signatures.
Image attached · 84 / 300
Post Preview
openquok.bsky.social @openquok.bsky.social
Jun 14, 9:00 AM
Ship the weekly product update — up to four images or one video, 300 characters max.
Compose & links
Write 300 graphemesadd @mentionsoptional link cardspreview before you queue
Stay inside the 300-grapheme limit. URLs in the caption become clickable facets; add an optional link-card embed in Settings when the post has no media. Use @handle autocomplete. Attach up to four images or one MP4 — never mixed. Preview letterboxed media before you queue the slot.
CLI command options
# Draft + human checklist (Bluesky)
openquok posts:create --json ./examples/bluesky-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
—
Engagement
1,082
1 channel
Followers
—
No daily series match this metric family for the selected channels.
Likes
Bluesky openquok.bsky.social
9.2%
1,082
Replies
Bluesky openquok.bsky.social
6.4%
274
Reposts
Bluesky openquok.bsky.social
5.5%
315
Quotes
Bluesky openquok.bsky.social
4.1%
100
Insights
See what resonates on Bluesky track likes and repostsand iterate
Bluesky analytics — Trends summary totals and per-post likes, replies, reposts, and quotes from the public App View feed (7, 30, or 90 days). Then schedule more of what already works.
CLI analytics options
# Bluesky platform metrics
INTEGRATION_ID=$(openquok integrations:list | jq -r '.[] | select(.identifier=="bluesky") | .id')
openquok analytics:platform "$INTEGRATION_ID" -d 30
# Per-post insights
openquok analytics:post <post-id> -d 7Draft 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
What performed best on my channels over the last 7 days? Break down impressions and engagement.
Pulled platform analytics (7d)
Top post: 12.4k impressions, 842 reactions — carousel on product tips.
Facebook Page leads with +24% impressions vs last week.
Compare that post on TikTok vs Instagram Reels.
TikTok: 48k views, 2.1k likes. IG Reel: 31k plays, 312 saves. TikTok wins reach; IG leads on saves.
Draft 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
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
# 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 30Backlinks, Playbooks & Building Blocks
Bluesky viral formats
Mix Bluesky-focused backlink guides, playbooks, skills, and MCP servers — then tailor them to your ThinkRail workflow.
comparisons
agent-native scheduling, not another dashboard
Most social scheduler SaaS keeps you in a browser tab. OpenQuok is built for Bluesky 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
- You choose publish-now, schedule, or draft — approve on OpenQuok when you want a review step
CLI
Command reference
Bluesky 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=="bluesky") | .id'Discover your Bluesky integration UUID
openquok integrations:settings "$BLUESKY_ID"Get Bluesky posting rules and character limits
openquok posts:create --jsonSchedule a text-only Bluesky post
openquok posts:create --jsonSchedule up to four images on one Bluesky post
openquok posts:create --jsonSchedule a post and follow-up replies on bluesky.replies
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:
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 Bluesky: Every Supported Platform for ThinkRail
Start with Bluesky, then schedule every other network from ThinkRail.
- Facebook Schedule Facebook from ThinkRail.
- Threads Schedule Threads from ThinkRail.
- Instagram Schedule Instagram from ThinkRail.
- YouTube Schedule YouTube from ThinkRail.
- TikTok Schedule TikTok from ThinkRail.
- LinkedIn Schedule LinkedIn from ThinkRail.
- X Schedule X from ThinkRail.
- Bluesky Schedule Bluesky from ThinkRail.You're here
- Dev.to Schedule Dev.to from ThinkRail.
- Skool Preview Skool workflows for ThinkRail — coming soon.Soon
Autonomous agents & MCP
Beyond ThinkRail: Every Supported Agent
Open the landing page for another autonomous agent or MCP client. Compare setup steps, supported channels, and scheduling workflows beside ThinkRail.
Autonomous agents
OpenClaw
Schedule Bluesky from OpenClaw with openquok-core skills and CLI examples.
Hermes Agent
Schedule Bluesky from Hermes Agent with openquok-core skills and CLI examples.
Grok Bot
Schedule Bluesky from Grok Bot with openquok-core skills and CLI examples.
Dots
Schedule Bluesky from Dots with openquok-core skills and CLI examples.
Meta Muse
Schedule Bluesky from Meta Muse with openquok-core skills and CLI examples.
You're here
ThinkRail
Schedule Bluesky from ThinkRail with openquok-core skills and CLI examples.
Manus
Schedule Bluesky from Manus with openquok-core skills and CLI examples.
Gemini Task
Schedule Bluesky from Gemini Task with openquok-core skills and CLI examples.
MCP clients
Antigravity CLI
Draft and schedule Bluesky with MCP tools from Antigravity CLI.
Android Studio
Draft and schedule Bluesky with MCP tools from Android Studio.
ChatGPT
Draft and schedule Bluesky with MCP tools from ChatGPT.
Codex
Draft and schedule Bluesky with MCP tools from Codex.
Cursor
Draft and schedule Bluesky with MCP tools from Cursor.
Claude Code
Draft and schedule Bluesky with MCP tools from Claude Code.
Claude Cowork
Draft and schedule Bluesky with MCP tools from Claude Cowork.
VS Code / Copilot
Draft and schedule Bluesky with MCP tools from VS Code / Copilot.
Devin Desktop
Draft and schedule Bluesky with MCP tools from Devin Desktop.
Amp
Draft and schedule Bluesky with MCP tools from Amp.
Warp
Draft and schedule Bluesky with MCP tools from Warp.
Muse Code
Draft and schedule Bluesky with MCP tools from Muse Code.
Grok Build
Draft and schedule Bluesky with MCP tools from Grok Build.
Frequently asked questions
ThinkRail + Bluesky,answered
What ThinkRail is, how to install openquok-core, scheduling Bluesky posts, human approval, and Bluesky setup questions.
ThinkRail is a worktree IDE for the pi coding agent. You open a git repo as a project, cut workspaces as git worktrees, and work across Monaco tabs, terminals, diffs, and concurrent pi chat sessions — all scoped to the active worktree. See the ThinkRail integration and agent setup guides.
ThinkRail is a thin host: pi runs in-process and owns models, skills, compaction, and cost. ThinkRail owns the workspace, the editor, and the UI. Install openquok-core where pi discovers skills, then chat from ThinkRail. A standalone pi CLI session can use the same skill files — browse agent hosts and MCP clients for other paths.
Install @openquok/auto-cli in the worktree, add openquok-core to ~/.pi or .pi/skills/, and authenticate once. See the ThinkRail agent guide or the scheduling walkthrough.
The global CLI and auth files live on the machine that runs ThinkRail — the same environment as worktree terminals. Your OpenQuok workspace tokens never need to be pasted into chat; use OAuth device flow or a programmatic opo_ token on that computer. See OAuth2 for apps and Public API docs for token setup.
ThinkRail can draft and schedule Bluesky posts, upload images and video, apply per-platform settings, and pull platform and post analytics for your connected Bluesky 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 ThinkRail + Bluesky and the Bluesky humanizer tool for channel-specific workflows.
Connect your Bluesky account via the Bluesky setup guide or the Bluesky channel landing. Install openquok-core on ThinkRail with the ThinkRail agent guide. Message your assistant to schedule — ThinkRail uses integration UUIDs from openquok integrations:list to target your Bluesky account. Every post lands as a draft or scheduled item until you approve on the calendar or kanban. Browse Bluesky playbooks and Bluesky building blocks for format ideas.
It depends on you. You can ask ThinkRail 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 ThinkRail to use draft-only or not to publish when you want a review step first.
openquok-core runs in the worktree shell for repeatable scheduling. MCP fits ad hoc editor tools — see OpenQuok for Cursor or MCP setup. Many teams use both.
OpenQuok offers a 7-day free trial for scheduling on Pricing. ThinkRail is open source; you bring your own pi provider credentials. Install ThinkRail, add openquok-core, and begin scheduling from a worktree 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.
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 → Bluesky. Enter your PDS service URL (default https://bsky.social for most accounts), handle or email, and an app password from Bluesky settings. OpenQuok encrypts those credentials on the server; connect APIs never return them. See the connect channels guide. For self-hosted deployments, see the self-host Bluesky setup guide.
Yes. URLs in your caption become rich-text facets (clickable links) at publish. For a large preview card, set Link card URL in composer Settings on a text-only post — not combined with images, video, or a quote post. Type @handle in the composer and pick a match from autocomplete; facets apply on the main post and on follow-up reply rows.
No. Create an app password in Bluesky settings while two-factor authentication stays on. Paste that password into Add Channel — not your main account password.
Up to four images or one MP4 video per post — not both in the same post. Text-only posts are valid. Alt text comes from media details when you set it. See media rules by platform and the Bluesky photo editor.
Yes. Add follow-up rows in the composer with delays and optional media. OpenQuok publishes the main post first, then each reply on the same account. See threads and follow-up comments and Bluesky CLI examples.
Yes. Connect Bluesky in our web dashboard with an app password, then follow MCP setup guides (ask your assistant in chat to list integrations and queue posts), CLI setup guides, the create-post API, or Bluesky CLI examples. Pass follow-up replies in bluesky.replies when you schedule from the API or CLI.
Yes. Open workspace Analytics to see likes, replies, reposts, and quotes summed by day for your connected account. Open Statistics on a published post for per-post engagement from the public App View API.
Yes. Connect Bluesky in our web dashboard with an app password, 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.
Read the ThinkRail setup guide
Step-by-step self-host setup for connecting OpenQuok to ThinkRail — 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.