macOS
CLI or desktop build on Apple Silicon
OpenQuok Prepare PeerPush launch from ThinkRail then you submit
Use ThinkRail with OpenQuok to prepare PeerPush directory launches. List product profiles, ensure variants, check listing readiness, and track domain rating — you submit on the directory site.
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 skills (core, then directory):
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.mdThen openquok-directory-launch
npx skills add https://github.com/Ratimon/openquok-monorepo/tree/main/agent --skill openquok-directory-launch -yAgent
Prepare my PeerPush launch — list product profiles, ensure the peerpush variant, and show listing readiness before I open the browser extension.
On it — preparing your directory launch.
- 1. Reading openquok-core skills or openquok MCP tool definitions
- 2. directoryProfilesList → main product profile
- 3. directoryVariantsEnsure → peerpush variant tailored
- 4. directoryListingSummary → extension handoff fields ready
Listing summary:
- • Readiness: ready for peerpush.com submit
- • directorySeoOverview → DR 42 · checkedAt 2h ago
Your worktree IDE
One prompt, PeerPush launch prep
Ask ThinkRail to list directory destinations and product profiles, ensure the peerpush variant, and run a listing summary for PeerPush. You review fields in the browser extension and submit on the directory site — no calendar or kanban.
For founders in the AI era
Who launches on PeerPush with OpenQuok?
Indie founders
Spread PeerPush submits. Message ThinkRail for profiles and readiness before you submit.
SaaS teams
One workspace for copy. ThinkRail prepares peerpush variants for team review.
Marketing teams
One workspace per client. ThinkRail keeps PeerPush profiles separate.
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:statusSample workspace
Acme Marketing
Team Members (3/5)
Invite your assistant or team member to manage your account
Team members on your plan: 3/5 used across your account.
Jordan Lee
Sam Rivera
Ava Chen
Pending invitations
Invited · Member · Expires in 6 days
Workspaces and team
Invite by emailassign Membermanage seats by Admin
Add Members by email. Admins manage seats. Everyone shares profiles and launch status in one dashboard. Automate profiles, variants, and listing readiness with openquok directory:* from your terminal or CI — then use the browser extension when you submit on peerpush.com.
CLI command options
# PeerPush profile, variant, and listing readiness
MAIN_ID=$(openquok directory:profiles:list --main-only | jq -r '.data[0].id')
openquok directory:variants:ensure "$MAIN_ID" --site-key peerpush
openquok directory:listings "$MAIN_ID" | jq '.data.destinations[] | select(.providerSlug=="peerpush")'Built-in DR tracking
Track DR movescompare rivalsadapt your launch plan
Monitor domain rating history for your product site, add competitor domains, and see trends next to PeerPush and other listings you submitted in one dashboard — so you know what is working.
CLI analytics options
# PeerPush directory SEO (cached DR metrics)
openquok directory:analytics:overview --profile "$MAIN_ID" | jq '.data.productDomain.checkedAt'
openquok directory:analytics:history --profile "$MAIN_ID" -d 90
openquok directory:analytics:refresh --profile "$MAIN_ID"Backlinks, Playbooks & Building Blocks
PeerPush launch playbooks
Mix PeerPush-tagged playbooks, building blocks, and MCP servers — then tailor directory launch steps 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 PeerPush directory launch 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
PeerPush directory launch commands from the openquok-directory-launch skill (requires openquok-core) — structured JSON on stdout, product profiles, variants, and listing readiness before you submit on the directory site.
openquok directory:destinations:list | jq '.data[] | select(.providerSlug=="peerpush")'List published PeerPush launch destinations
openquok directory:profiles:list --main-onlyList main product profiles in your workspace
openquok directory:variants:ensure <main-profile-id> --site-key peerpushCreate or return the PeerPush variant for a main profile
openquok directory:listings <profile-id>Listing readiness and submission status for PeerPush
openquok directory:analytics:overview --profile <main-profile-id>Domain rating overview — read checkedAt on cached metrics
openquok directory:analytics:competitors:add --domain <competitor-domain> --label "Competitor"Track competitor domains next to your product site
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 PeerPush: Every Supported Channel for ThinkRail
Start with PeerPush, then schedule social posts and launch on other directories 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.
- Dev.to Schedule Dev.to from ThinkRail.
- Skool Preview Skool workflows for ThinkRail — coming soon.Soon
- PeerPush Launch on PeerPush from ThinkRail.You're here
- Uneed Launch on Uneed 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 PeerPush from OpenClaw with openquok-core skills and CLI examples.
Hermes Agent
Schedule PeerPush from Hermes Agent with openquok-core skills and CLI examples.
Grok Bot
Schedule PeerPush from Grok Bot with openquok-core skills and CLI examples.
Dots
Schedule PeerPush from Dots with openquok-core skills and CLI examples.
Meta Muse
Schedule PeerPush from Meta Muse with openquok-core skills and CLI examples.
You're here
ThinkRail
Schedule PeerPush from ThinkRail with openquok-core skills and CLI examples.
Manus
Schedule PeerPush from Manus with openquok-core skills and CLI examples.
Gemini Task
Schedule PeerPush from Gemini Task with openquok-core skills and CLI examples.
Claude Duet
Schedule PeerPush from Claude Duet with openquok-core skills and CLI examples.
MCP clients
Antigravity CLI
Draft and schedule PeerPush with MCP tools from Antigravity CLI.
Android Studio
Draft and schedule PeerPush with MCP tools from Android Studio.
ChatGPT
Draft and schedule PeerPush with MCP tools from ChatGPT.
Codex
Draft and schedule PeerPush with MCP tools from Codex.
Cursor
Draft and schedule PeerPush with MCP tools from Cursor.
Claude Code
Draft and schedule PeerPush with MCP tools from Claude Code.
Claude Cowork
Draft and schedule PeerPush with MCP tools from Claude Cowork.
VS Code / Copilot
Draft and schedule PeerPush with MCP tools from VS Code / Copilot.
Devin Desktop
Draft and schedule PeerPush with MCP tools from Devin Desktop.
Amp
Draft and schedule PeerPush with MCP tools from Amp.
Warp
Draft and schedule PeerPush with MCP tools from Warp.
Muse Code
Draft and schedule PeerPush with MCP tools from Muse Code.
Grok Build
Draft and schedule PeerPush with MCP tools from Grok Build.
Frequently asked questions
ThinkRail + PeerPush,answered
What ThinkRail is, how to install openquok-core, PeerPush directory launch, listing readiness, and 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 list directory destinations and product profiles, ensure PeerPush variants, return listing summaries, and refresh directory SEO overview (read checkedAt before you re-fetch DR). Install openquok-core for auth and shell safety, then openquok-directory-launch for directory:* CLI recipes (or use hosted MCP directory* tools with an opo_ token). Every command returns structured JSON for the agent to parse. See ThinkRail + PeerPush and PeerPush CLI examples.
Facebook, Instagram, Threads, YouTube, TikTok, LinkedIn, and X are supported today. Connect channels in the OpenQuok web app or follow the channel setup guides; see every network on Supported channels. ThinkRail uses integration UUIDs from openquok integrations:list to target the right accounts.
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.
No. OpenQuok autofills the PeerPush form from your business profile. You review the page and click submit on peerpush.com. See PeerPush directory integration and directory submission.
Sign up for free, install the OpenQuok browser extension, and create a product in My Products. Fill name, tagline, description, website, logo, and PeerPush discovery fields. Then open Add directory launch → PeerPush.
PeerPush offers paid instant publish and a free queue path. OpenQuok lists each as a separate destination with its own start URL. Pick the variant that matches your plan on PeerPush. Details are in PeerPush directory integration.
OpenQuok also documents PeerPush on the build backlinks catalog for dofollow and cost context. See PeerPush on Build backlinks and directory launch platforms.
Yes. Create a product profile in your dashboard and install the OpenQuok browser extension for the peerpush.com handoff, then follow MCP setup guides (directory tools list destinations and profiles), directory launch CLI, the directory launch API, or PeerPush CLI examples. Directory SEO metrics are cached — read checkedAt and manualRefreshAvailableAt in API or CLI responses.
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.