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.

How does ThinkRail relate to the pi coding agent?

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.

How do I install the openquok-core skill in ThinkRail?

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.

Where do OpenQuok credentials live?

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.

What can ThinkRail do with Dev.to on OpenQuok?

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.

How does ThinkRail schedule Dev.to posts?

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.

Does ThinkRail publish immediately or wait for approval?

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.

Why use ThinkRail with CLI instead of MCP-only?

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.

Can I try OpenQuok for free?

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.

How do I schedule social media posts with OpenQuok?

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.

What counts as a channel?

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.

How do I connect Dev.to to OpenQuok?

Sign up for free, open a workspace, and choose Add Channel → Dev.to. Paste an API key from DEV Settings → Extensions. OpenQuok keeps the key on the server so it can publish for you; list and connect APIs never return it. Treat the key like a password — if it leaks, rotate it in DEV Settings and reconnect. See the connect channels guide. For self-hosted deployments, see the self-host Dev.to setup guide.

Do I write the article body as markdown?

Yes. Use our post editor — the body is sent as markdown. Title, tags, cover, organization, series, and canonical URL live in Dev.to settings, not in a separate markdown editor. See editor by platform and Dev.to API settings.

How many tags can I set on a scheduled article?

Dev.to allows at most four tags. OpenQuok loads tag suggestions from the connected account when available, or you can type names freely. Title must be at least two characters before you can schedule. See Dev.to API settings and Dev.to CLI examples.

Can I set a cover image and organization?

Yes. Attach an optional cover (recommended 1000×420) from the media library, and pick an organization if your account publishes for one. Personal profile is the default when no organization is selected. Design covers in the Dev.to photo editor.

Can I add an article to a Dev.to series?

Yes. Enter a free-text series name in Dev.to settings (or pass series in providerSettings). Dev.to creates the series if it does not already exist. See Dev.to API settings.

Can I syndicate a post that already lives on my site?

Yes. Set Canonical URL in Dev.to settings (or pass canonical in providerSettings). OpenQuok sends that URL with the article so Dev.to can point at the original. See Dev.to API settings and Dev.to CLI examples.

Can I schedule Dev.to articles from MCP, the API, or CLI?

Yes. Connect Dev.to in our web dashboard with an API key, then follow MCP setup guides (ask your assistant in chat to list integrations and queue posts), CLI setup guides, the create-post API, or Dev.to CLI examples. Pass title, tags, series, cover, and canonical URL in provider settings.

Does OpenQuok show Dev.to analytics?

Yes. Workspace analytics show account-level page views, reactions, and comments over 7, 30, or 90 days, plus per-article insights for published posts. Follow-up comments on Dev.to articles are not supported today. Pull metrics from the analytics CLI.

Is there a free trial for Dev.to scheduling?

Yes. Connect Dev.to in our web dashboard with an API key, schedule articles, 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.

Schedule Dev.to from ThinkRail then you approve

Use ThinkRail with openquok-core to draft and schedule Dev.to 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.md

ThinkRail Session 1

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

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 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 — publish now, schedule, or approve on OpenQuok.

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 can publish now or approve first.

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.

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

# OAuth2 device flow (interactive — opens browser)
openquok auth:login
openquok auth:status

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.

Post body

Queue this markdown article with title, tags, cover, series, and an optional canonical URL before it goes live.

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 schedule

Targeted 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

3,771

1 channel

Engagement

138

1 channel

Followers

—

10/14 10/20

OpenQuok on Dev.to (Page Views)

Page Views

Dev.to OpenQuok on Dev.to

12.6%

3,771

Reactions

Dev.to OpenQuok on Dev.to

8.4%

534

Comments

Dev.to OpenQuok on Dev.to

5.7%

138

Dev.to insights

See what resonates on Dev.to track views and reactionsand iterate

Dev.to analytics—Trends summary totals and per-account page views, reactions, and comments (7, 30, or 90 days). 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 7

ThinkRail Session 1

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

ThinkRail Session 2

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.

ThinkRail Session 1

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 30

Backlinks, Playbooks & Building Blocks

Dev.to viral formats

Mix Dev.to-focused backlink guides, playbooks, skills, and MCP servers — then tailor them to your ThinkRail workflow.

Backlinks

See All

Browse every Dev.to site guide in the backlink directory.

Playbooks

Skill Builder

Build and export a Dev.to SKILL.md from building blocks.

See All

Browse every Dev.to 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 Dev.to building block.

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
You choose publish-now, schedule, or draft — approve on OpenQuok when you want a review step

Typical social scheduler SaaS

OpenQuok + ThinkRail

Copy posts between your AI chat and a separate scheduling tool

Ask the agent in ThinkRail to draft and schedule from the worktree

Siloed API keys and workflows that do not compose with your agent stack

Credentials stay on the machine that runs ThinkRail — workspace isolated

Always-on integrations that bloat agent context

Skills load on demand from ~/.pi or the worktree .pi/skills folder

Locked to one vendor's models or automation layer

CLI-first openquok-core works beside any other pi skill or extension

One working tree mixing every experiment as you add channels and parallel sessions

Git worktrees isolate each line of work — merge the good branch, delete the rest

Autopilot publishing with no human checkpoint

You choose publish-now, schedule, or draft — approve on OpenQuok when you want a review step

CLI

Command reference

Dev.to commands from the openquok-core skill — structured JSON on stdout, human-in-the-loop drafts, and workspace media uploads.

Command Description

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

Schedule a markdown article with title and tags
openquok posts:create --json ./examples/devto-series.json

Schedule an article in a Dev.to series
openquok posts:create --json ./examples/devto-canonical.json

Syndicate an article with a canonical URL
openquok posts:create --json ./examples/devto-organization.json

Publish to an organization with cover image settings
openquok integrations:trigger "$DEVTO_ID" tags

List Dev.to tags for autocomplete
openquok integrations:trigger "$DEVTO_ID" organizations

List organizations you can publish as
openquok analytics:platform "$DEVTO_ID" -d 30

Pull 30-day Dev.to analytics (page views, reactions, comments)
openquok analytics:post "$POST_ID" -d 7

Pull 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:

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 Dev.to: Every Supported Platform for ThinkRail

Start with Dev.to, then schedule every other network from ThinkRail.

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 Dev.to from OpenClaw with openquok-core skills and CLI examples.

Hermes Agent

Schedule Dev.to from Hermes Agent with openquok-core skills and CLI examples.

Grok Bot

Schedule Dev.to from Grok Bot with openquok-core skills and CLI examples.

Dots

Schedule Dev.to from Dots with openquok-core skills and CLI examples.

Meta Muse

Schedule Dev.to from Meta Muse with openquok-core skills and CLI examples.

You're here

ThinkRail

Schedule Dev.to from ThinkRail with openquok-core skills and CLI examples.

Manus

Schedule Dev.to from Manus with openquok-core skills and CLI examples.

Gemini Task

Schedule Dev.to from Gemini Task with openquok-core skills and CLI examples.

MCP clients

Antigravity CLI

Draft and schedule Dev.to with MCP tools from Antigravity CLI.

Android Studio

Draft and schedule Dev.to with MCP tools from Android Studio.

ChatGPT

Draft and schedule Dev.to with MCP tools from ChatGPT.

Codex

Draft and schedule Dev.to with MCP tools from Codex.

Cursor

Draft and schedule Dev.to with MCP tools from Cursor.

Claude Code

Draft and schedule Dev.to with MCP tools from Claude Code.

Claude Cowork

Draft and schedule Dev.to with MCP tools from Claude Cowork.

VS Code / Copilot

Draft and schedule Dev.to with MCP tools from VS Code / Copilot.

Devin Desktop

Draft and schedule Dev.to with MCP tools from Devin Desktop.

Amp

Draft and schedule Dev.to with MCP tools from Amp.

Warp

Draft and schedule Dev.to with MCP tools from Warp.

Muse Code

Draft and schedule Dev.to with MCP tools from Muse Code.

Grok Build

Draft and schedule Dev.to with MCP tools from Grok Build.

Frequently asked questions

ThinkRail + Dev.to,answered

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

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 your free trial

Schedule Dev.to from ThinkRail then you approve

Install our core skill:

Chat with pi in ThinkRail,keep main clean

Who schedules Dev.to with ThinkRail?

Engineers & indie hackers

Developer relations

Agencies & technical blogs

Five steps,to ThinkRail + OpenQuok

1. Install ThinkRail

2. Open a worktree workspace

3. Chat, edit, and run terminals

4. Install openquok-core skill

5. Integrate & customize other skills or MCPs

1. Install ThinkRail

2. Open a worktree workspace

3. Chat, edit, and run terminals

4. Install openquok-core skill

5. Integrate & customize other skills or MCPs

authenticate in the worktreepick your workspacechat from the IDE securely

ThinkRail

Ship technical posts with tags and series you approve

Write markdown articles in Dev.toreview drafts on the kanban boardbefore you approve

Targeted channels

Overview

Trends

See what resonates on Dev.to track views and reactionsand iterate

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

Dev.to viral formats

Backlinks

See All

Playbooks

Skill Builder

See All

Building Blocks

OpenQuok Core

See All

agent-native scheduling, not another dashboard

Typical social scheduler SaaS

OpenQuok + ThinkRail

Typical social scheduler SaaS

OpenQuok + ThinkRail

Command reference

Worktrees, editor, and terminals

macOS

Linux

Windows

Git worktrees

Monaco editor

Worktree terminals

Pi MCP extensions

Beyond Dev.to: Every Supported Platform for ThinkRail

Beyond ThinkRail: Every Supported Agent

OpenClaw

Hermes Agent

Grok Bot

Dots

Meta Muse

ThinkRail

Manus

Gemini Task

Antigravity CLI

Android Studio

ChatGPT

Codex

Cursor

Claude Code

Claude Cowork

VS Code / Copilot

Devin Desktop

Amp

Warp

Muse Code

Grok Build

ThinkRail + Dev.to,answered

Read the ThinkRail setup guide

Start free. Publish with confidence.