iOS
Message Muse from iPhone or iPad
OpenQuok Prepare PeerPush launch from Meta Muse then you submit
Use Meta Muse 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):
Create a custom connector for OpenQuok using the public API spec at https://www.openquok.com/api/v1/openapi.json. Do not publish anything yet. First list my connected social accounts and the available scheduling operations.Then 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 everyday agent
One prompt, PeerPush launch prep
Ask Meta Muse 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 Meta Muse for profiles and readiness before you submit.
SaaS teams
One workspace for copy. Meta Muse prepares peerpush variants for team review.
Marketing teams
One workspace per client. Meta Muse keeps PeerPush profiles separate.
Meta-owned channels first
Facebook, Instagram, and Threads are first-class for Meta Muse. You can still schedule every other supported network from the same OpenQuok workspace.
Connect once
store credentials in Musepick your workspacechat from anywhere securely
Use Muse secure credential storage for your OpenQuok API key. Choose a workspace, validate connected channels, and draft from mobile or web without opening another scheduling tab.
Public API authentication
# Programmatic token (Authorization header)
export OPENQUOK_API_KEY=opo_your_programmatic_token
# Custom connector: give Muse the OpenAPI URL
# https://www.openquok.com/api/v1/openapi.jsonSample 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 (Secure VM)
# 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 Meta Muse 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 Meta Muse
Typical social scheduler SaaS
- Copy posts between your AI chat and a separate scheduling tool
- No first-party Muse connector for every SaaS on day one
- API keys pasted into chat history
- Autopilot publishing with no human checkpoint
- One workspace mixing every client as you add channels
- Terminal coding agents mixed up with consumer Muse
OpenQuok + Meta Muse
- Message Meta Muse to draft and schedule through OpenQuok
- Custom connectors from the public OpenAPI document Meta documents for APIs
- Store OpenQuok tokens in Muse secure credential prompts
- You choose publish-now, schedule, or draft — approve on OpenQuok when you want a review step
- Multi-workspace isolation — scoped API keys per brand so drafts never cross wires
- Clear split: Meta Muse here; Muse Code MCP setup lives on its own integration page
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
Mobile, web, and connectors
Meta Muse meets you on the devices you already use. OpenQuok connects through custom connectors, the public API, CLI in the Secure VM, or hosted MCP when your environment supports it:
Android
Use Muse on Android phones and tablets
muse.ai
Chat in the browser at meta.ai
Reach Muse from WhatsApp when Meta enables it for your account
Secure VM
Muse runs tasks in an isolated environment with a terminal and filesystem
Secure credentials
Store API keys in Muse credential prompts — not in ordinary chat
OpenQuok surfaces
Custom connector
Muse can wire OpenQuok from your public OpenAPI document
Public API
REST endpoints for accounts, drafts, schedules, and publishing
openquok CLI
Shell commands inside the Secure VM when you install the skill
Hosted MCP
Use OpenQuok MCP when your Muse environment exposes MCP configuration
Beyond PeerPush: Every Supported Channel for Meta Muse
Start with PeerPush, then schedule social posts and launch on other directories from Meta Muse.
- Facebook Schedule Facebook from Meta Muse.First-class
- Instagram Schedule Instagram from Meta Muse.First-class
- Threads Schedule Threads from Meta Muse.First-class
- YouTube Schedule YouTube from Meta Muse.
- TikTok Schedule TikTok from Meta Muse.
- LinkedIn Schedule LinkedIn from Meta Muse.
- X Schedule X from Meta Muse.
- Bluesky Schedule Bluesky from Meta Muse.
- Dev.to Schedule Dev.to from Meta Muse.
- Skool Preview Skool workflows for Meta Muse — coming soon.Soon
- PeerPush Launch on PeerPush from Meta Muse.You're here
- Uneed Launch on Uneed from Meta Muse.
Autonomous agents & MCP
Beyond Meta Muse: Every Supported Agent
Open another autonomous agent or MCP client landing page. Compare setup steps, Meta-first channels, and scheduling workflows beside Meta Muse.
Autonomous agents
You're here
Meta Muse
Schedule PeerPush from Meta Muse with openquok-core skills and CLI examples.
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.
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
Muse Code
Draft and schedule PeerPush with MCP tools from Muse Code.
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.
Grok Build
Draft and schedule PeerPush with MCP tools from Grok Build.
Frequently asked questions
Meta Muse + PeerPush,answered
What Meta Muse is, how to install openquok-core, PeerPush directory launch, listing readiness, and setup questions.
Meta Muse is Meta's personal AI agent for everyday work — not just Q&A. It runs on Muse Secure VM, can use a browser on your behalf, and chats like messaging in the Muse app or WhatsApp. It is powered by Muse Spark for agentic tasks. US rollout includes iOS, Android, and muse.ai. Overview: https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/. See the Meta Muse integration and agent guide.
Muse Secure VM is a dedicated cloud computer for one person's Muse. It holds connected app data and credentials in isolated storage. Muse asks before sensitive actions like email or purchases. OpenQuok fits the same pattern: schedule posts as drafts, then you approve on OpenQuok before anything goes live.
Yes. Muse can continue long tasks after you close the app and return when it needs input or when something changes. Pair that with OpenQuok so Muse queues social drafts while you focus elsewhere — publishing still waits for your calendar or kanban approval.
Yes — when your OpenQuok workspace has Facebook or Instagram connected. Ask Muse to call OpenQuok through a custom connector or openquok-core in the Secure VM. Muse drafts and queues posts; you approve on OpenQuok before anything publishes to your Page or professional account. See supported channels.
Not as a pre-reviewed directory connector on day one. Meta says you can ask Muse to create a custom connector when a service exposes an API. OpenQuok publishes a public OpenAPI document and REST API so Muse can wire scheduling without a separate adapter.
Create a programmatic token under Developers → Access in your OpenQuok workspace. When Muse asks for credentials, use its secure credential prompt — do not repeat the key in normal chat. API requests use the Authorization header with your opo_ token. See Public API docs.
Start with a custom connector and the OpenAPI URL when you use consumer Muse in chat. Install openquok-core in the Secure VM when you want shell workflows. Use hosted MCP when your Muse environment exposes MCP configuration — same tools as other MCP clients.
List connected channels, inspect publishing rules, draft and schedule posts, upload media, and pull analytics. See supported channels and CLI post commands.
It depends on you. You can ask Muse 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 Muse to use draft-only or not to publish when you want a review step first.
Muse stores connector secrets in its secure credential store. When you use the CLI path, auth files live inside the Secure VM — not on your phone chat history. Rotate tokens from OpenQuok Developers → Access if you revoke access.
OpenQuok offers a 7-day free trial for scheduling on Pricing. Meta Muse access depends on Meta's plans for your region — connect OpenQuok once your Muse account is active.
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 Meta Muse setup guide
Step-by-step self-host setup for connecting OpenQuok to Meta Muse — 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.