macOS
CLI or desktop build on Apple Silicon
OPENQUOK Schedule Dev.to from ThinkRail then you approve
Message ThinkRail 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
Get Started For Free Get Started For Free Get Started For Free
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 drafts. You approve on the calendar before anything publishes.
Built for technical writers with ThinkRail
Who schedules Dev.to with ThinkRail?
Engineers & indie hackers
Ship changelogs and tutorials from the calendar, not the Dev.to editor. Message ThinkRail to draft Dev.to posts from chat — you approve before publish.
Developer relations
Batch docs and release notes with tags, series, and covers. Review on kanban before publish. ThinkRail queues Dev.to drafts at volume — your team approves before publish.
Agencies & technical blogs
Connect client accounts with an API key. Pipe markdown drafts via API or MCP. Run ThinkRail per client workspace so Dev.to 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 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
# 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
Page Views
12.6%
4,202
Reactions
8.4%
664
Comments
5.7%
187
Dev.to insights
See what resonates on Dev.to track views and reactionsand iterate
Track page views, reactions, and comments from your connected DEV Community account over 7, 30, or 90 days inside OpenQuok analytics. Use per-article insights once a post is published. 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 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 30Playbooks & Building Blocks Directories
Dev.to viral formats
Mix Dev.to-focused 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 Dev.to 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
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 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 Dev.to: Every Supported Platform for ThinkRail
Start with Dev.to, 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.
- Dev.to Schedule Dev.to from ThinkRail.You're here
Frequently asked questions
ThinkRail + Dev.to,answered
What ThinkRail is, how to install openquok-core, scheduling Dev.to posts, human approval, and how agents draft from chat.
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 Dev.to posts, upload images and video, apply per-platform settings, and pull platform and post analytics for your connected Dev.to 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 + Dev.to and the Dev.to humanizer tool for channel-specific workflows.
Connect your Dev.to account via the Dev.to setup guide or the Dev.to 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 Dev.to account. Every post lands as a draft or scheduled item until you approve on the calendar or kanban. Browse Dev.to playbooks and Dev.to building blocks for format ideas.
Posts created through the CLI land in your OpenQuok workspace as drafts or scheduled items — nothing goes live on autopilot. You review on the calendar or kanban, move posts through draft and review, and approve what should publish. ThinkRail handles volume; you handle quality.
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.
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.