macOS
Native desktop app for Apple Silicon and Intel Macs
OpenQuok Prepare PeerPush launch from Grok Bot then you submit
Use Grok Bot 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):
npm install -g @openquok/auto-cli@latestThen 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 desktop teammate
One prompt, PeerPush launch prep
Ask Grok Bot 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 Grok Bot for profiles and readiness before you submit.
SaaS teams
One workspace for copy. Grok Bot prepares peerpush variants for team review.
Marketing teams
One workspace per client. Grok Bot keeps PeerPush profiles separate.
X as your home network
Grok Bot fits xAI’s cloud computer and many named Bots. X is first-class; connect other networks in OpenQuok when you need them.
Connect once
authenticate on the cloud computerpick your workspacechat from desktop securely
Choose a workspace, connect with OAuth2 — approve in your browser, and credentials stay on the Bot shared computer. Message Grok Bot from desktop or iOS 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 Grok Bot 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 Grok Bot
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 workspace mixing every context as you add channels and parallel sessions
- Autopilot publishing with no human checkpoint
OpenQuok + Grok Bot
- Message Grok Bot from desktop or iOS to draft and schedule
- Credentials stay on the Bot shared cloud computer — workspace isolated
- Skills load on demand via Plugins or / — keep chat context clean
- CLI-first openquok-core works beside any other Bot skill or routine
- Multi-workspace isolation — spin up a workspace per context so channels and drafts never cross wires
- 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 chat
Desktop, mobile, and plugins
Grok Bot teammates run on a shared cloud computer — message them from macOS, Windows, or iOS, then invoke skills with / in chat or Settings → Plugins:
Windows
Desktop app for Windows 10 and 11
iOS
Message your Bot from iPhone or iPad on the go
Plugins
Install skills via Settings → Plugins or / in chat
Routines
Scheduled work on the Bot shared cloud computer
Cloud computer
Persistent browser, filesystem, and terminal for each Bot
Connectors & MCP (optional)
Connectors
Optional MCP connectors for third-party tools
Beyond PeerPush: Every Supported Channel for Grok Bot
Start with PeerPush, then schedule social posts and launch on other directories from Grok Bot.
- X Schedule X from Grok Bot.First-class
- Facebook Schedule Facebook from Grok Bot.
- Threads Schedule Threads from Grok Bot.
- Instagram Schedule Instagram from Grok Bot.
- YouTube Schedule YouTube from Grok Bot.
- TikTok Schedule TikTok from Grok Bot.
- LinkedIn Schedule LinkedIn from Grok Bot.
- Bluesky Schedule Bluesky from Grok Bot.
- Dev.to Schedule Dev.to from Grok Bot.
- Skool Preview Skool workflows for Grok Bot — coming soon.Soon
- PeerPush Launch on PeerPush from Grok Bot.You're here
- Uneed Launch on Uneed from Grok Bot.
Autonomous agents & MCP
Beyond Grok Bot: Every Supported Agent
Open another autonomous agent or MCP client landing page. Compare xAI Grok Bot workflows, X-first channels, and other hosts beside Grok Bot.
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.
You're here
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.
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
Grok Build
Draft and schedule PeerPush with MCP tools from Grok Build.
Cursor
Draft and schedule PeerPush with MCP tools from Cursor.
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.
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.
Frequently asked questions
Grok Bot + PeerPush,answered
What Grok Bot is, how to install openquok-core, PeerPush directory launch, listing readiness, and setup questions.
Grok Bot is an always-on teammate on xAI’s cloud computer. You message it from desktop or iOS. Grok Build is xAI’s terminal coding agent. You connect OpenQuok over MCP in the shell. Cursor is OpenQuok inside Agent and Composer. Same workspace and approval flow. Pick Grok Bot for messaging-first volume. Pick Grok Build when you live in the terminal. Pick Cursor when you stay in the repo.
X is first-class for Grok Bot on OpenQuok. Connect other networks when your workflow needs them. Grok Bot runs on xAI’s cloud computer with many named Bots.
Choose Grok Bot for many named Bots on one xAI cloud desktop without server ops. Choose Grok Build MCP when you want the xAI coding agent in your terminal. Choose OpenClaw when you must self-host and message from Telegram, WhatsApp, or Slack. Choose Dots for OpenAI workplace chat. See the Grok Bot vs OpenClaw guide.
Grok Bot is an AI teammate product with a shared persistent cloud computer — browser, filesystem, and terminal — for each Bot you create. You message it from macOS, Windows desktop, or iOS, install skills via Settings → Plugins or / in chat, and set up routines for scheduled work. See the Grok Bot integration and agent setup guides.
Grok Bot is included with Cursor Pro, Pro+, Ultra, and self-serve Cursor Teams — sign in with the same Cursor account on desktop or iOS. You can also link individual SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+, or sign in with a self-serve Grok Business seat; weekly usage tiers do not stack. SuperGrok Lite is not included. See Cursor Grok Bot plans and billing. OpenQuok billing is separate — you still need a workspace and connected channels on Pricing.
Install @openquok/auto-cli on the Bot cloud computer, add openquok-core as a skill, and authenticate once. See the Grok Bot agent guide or the scheduling walkthrough.
The global CLI and auth files live on the Bot shared cloud computer — the same environment where openquok-core runs shell commands. 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.
Grok Bot 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 Grok Bot + PeerPush and PeerPush CLI examples.
A cloud browser can click through sites, but it is a poor fit for a social calendar. Do not put social passwords or payment details in Grok Bot chat. Scripted logins often hit captchas and can break platform rules.
OpenQuok connects each channel once with OAuth or app credentials and publishes through official APIs. Tokens stay encrypted on our servers. You still message Grok Bot to draft and queue; you approve on the calendar or kanban before anything goes live. See the connect channels guide.
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. Grok Bot uses integration UUIDs from openquok integrations:list to target the right accounts.
It depends on you. You can ask Grok Bot 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 Grok Bot to use draft-only or not to publish when you want a review step first.
openquok-core is CLI-first for repeatable Bot workflows on the shared cloud computer. 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. Grok Bot access depends on your xAI or Cursor plan eligibility — install the app, create a Bot, add openquok-core, and begin scheduling from desktop 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 Grok Bot setup guide
Step-by-step self-host setup for connecting OpenQuok to Grok Bot — 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.