Meta Muse

Connect OpenQuok to Meta Muse for Facebook, Instagram, Threads, and WhatsApp — custom connector, public API, or openquok-core in Muse Secure VM.

4 min read

Connect your agent today

Draft from chat, review in your calendar, and publish only what you approve.

Start your free trial

Prerequisites

A Meta Muse account on a supported device or region. Meta ships Muse as a consumer personal agent (mobile, muse.ai, messaging). This is not Muse Code, Meta’s terminal coding agent for developers.
An OpenQuok workspace with at least one connected social channel.
A programmatic token from Developers → Access (or OAuth device flow if Muse runs the CLI in its Secure VM).

Meta Muse vs Muse Code

Meta Muse handles everyday tasks in a Secure VM and can build custom connectors from public APIs. Muse Code is a developer tool in your terminal with MCP in ~/.config/muse/settings.json. Use this guide for consumer Muse; use the Muse Code MCP guide for the coding agent.

How Muse works

Meta Muse is a personal agent on Muse Secure VM — a dedicated cloud computer with its own browser and credential storage. You can message Muse in the app or WhatsApp. Muse can keep working after you close the app and ask before sensitive actions. OpenQuok connects through a custom connector (public OpenAPI) or openquok-core in the VM; you still approve social publishes on OpenQuok. Product overview: Introducing Muse.

Installation

Confirm you are on Meta Muse

Official consumer product: Meta Muse. Developer tooling (Muse Code, Meta Model API) lives on dev.meta.ai — a different app and subscription.

Create an OpenQuok API key

In the OpenQuok dashboard, open Account → Settings → Developers → Access and create a programmatic token for the workspace Muse should use.

Keep the key for Muse secure credential prompts. Do not paste it into ordinary chat messages.

Choose a connection path

Meta documents that Muse can create a custom connector when a service exposes an API. OpenQuok publishes a public OpenAPI document:

https://www.openquok.com/api/v1/openapi.json

Ask Muse in chat:

Create a custom connector for OpenQuok using https://www.openquok.com/api/v1/openapi.json. Do not publish anything yet. First list my connected social accounts and the available scheduling operations.

When Muse asks for authentication, paste your opo_ token into the secure credential flow — not the main conversation.

API requests use the Authorization header with your programmatic token. See Public API for concepts and limits.

Muse runs tasks inside a Secure VM with a terminal. You can install the global CLI and fetch the openquok-core skill there:

npm install -g @openquok/auto-cli@latest
openquok --version

mkdir -p ~/openquok-core
curl -fsSL "https://raw.githubusercontent.com/Ratimon/openquok-monorepo/main/agent/skills/openquok-core/SKILL.md" 
  -o ~/openquok-core/SKILL.md

Authenticate with device OAuth or a programmatic token:

openquok auth:login
# or
export OPENQUOK_API_KEY=opo_your_programmatic_token
openquok auth:status

Ask Muse to follow SKILL.md when you want shell-based scheduling beside a custom connector.

Verify before you schedule

After the connector or CLI is ready, ask Muse:

List my connected OpenQuok channels and tell me which destinations support this post format before drafting anything.

Then draft with explicit approval:

Turn these notes into platform-specific drafts for my connected accounts, validate every target, and keep the result as drafts for review on OpenQuok.

Meta Muse + OpenQuok notes

Custom connectors are built per user; Meta does not review them the same way as directory connectors. Read OpenQuok privacy and terms before you grant access.
Human approval: drafts and scheduled items appear in your OpenQuok workspace. Review on the calendar or kanban before publish.
Muse Code: terminal coding agents should use Muse Code MCP setup, not this agent-host skill path.

Troubleshooting

Wrong product

If you installed @openquok/auto-cli on your laptop for Muse Code, you still need consumer Muse steps above for the personal agent. Muse Code MCP config does not replace a Meta Muse custom connector.

Muse Code (MCP)

Terminal coding agent — streamable HTTP MCP in settings.json

Public API

Auth, workspaces, and OpenAPI reference

CLI authentication

OAuth device flow and programmatic tokens

MCP setup guides

Cursor, Claude Code, and other MCP clients