Codex ↔ Muse Bridge

Let Codex collaborate with Muse through your existing browser session. Send a task, read Muse's response, and continue working in Codex while the conversation stays visible in Muse.

An experimental, dependency-free JavaScript helper and Codex skill. The bridge uses Muse's chat interface through the host's browser tools. Your Muse login stays in the browser; the bridge needs no server or API key. This is an unofficial community project, unaffiliated with OpenAI or Meta.

Quick start

You need a signed-in Muse account and Codex browser tools exposing Browser.tabs and Tab.playwright. Live checks used Codex's in-app browser through mcp__cua_repl. This repository supplies the skill and helper; browser access must already be available in your Codex environment.

1. Clone the repository and open it in Codex:

   git clone https://github.com/cherry-nft/codex-muse-bridge.git
   cd codex-muse-bridge
   

2. Sign in to Muse in the browser available to Codex.

3. Give Codex a task and an existing conversation URL:

   Read skills/muse-bridge/SKILL.md, then use Muse to help review my approach. Use this conversation: [paste your Muse conversation URL].

For a first test, you can instead ask:

Read skills/muse-bridge/SKILL.md. Create a dedicated Muse side chat, send a short hello, and tell me its reply.

No dependency installation is needed. The repository includes a Codex plugin manifest for packaging, but is not distributed through a plugin marketplace or npm. Cloning it does not install a plugin or change your browser configuration.

How it works

flowchart LR
    C[Codex] -->|uses skill and helper| B[Host browser tools]
    B -->|types a message| M[Muse chat]
    M -->|rendered reply| B
    B -->|message changes and status| C

The skill teaches Codex how to select a conversation, send a message, and interpret the result. The helper accepts the host's existing tab and handles the repeatable parts:

• Find: filter open Muse conversation tabs by title or URL.
• Read: extract loaded messages, roles, links, and generation state from the rendered page. Track message IDs and fingerprints to return changes on subsequent reads.
• Send: preserve existing drafts, require an idle composer, an