Set up Muse
Capture the tools you use with Meta's Muse models through Meta Model API.
Meta's Muse models are served by Meta Model API. Worsley captures any OpenAI-compatible tool that uses it, such as OpenCode, through a relay on your computer.
Meta AI, the chat assistant, has no terminal version, and isn't captured yet in the browser.
Sign in to the Worsley CLI
Do this once on each computer where you run your Muse tools.
- 1Install the Worsley CLI. It runs on macOS, Windows and Linux and needs Node.js 22.23.4 or later (on a Mac,
brew install nodeworks too). On macOS or Linux, run:
curl -fsSL https://www.worsley.ai/install.sh | shOn Windows, in PowerShell:
irm https://www.worsley.ai/install.ps1 | iexThe installer checks the download against its published checksum, puts the CLI in your home folder (~/.worsley, or %LOCALAPPDATA%\Worsley on Windows) and adds it to your PATH. Open a new terminal window afterward so the worsley command is found. Run the same command again any time to update.
- 1Sign in. The command below prints a link and a short code, then waits.
worsley login- 1Open the link. Log in to Worsley if asked, check that the code on the page matches the one in your terminal and that it names this computer, then select Connect. If you last logged in more than 10 minutes ago, Worsley asks you to log in again first. Opened the page without the code? Type it in.
- 2Back in the terminal, Worsley confirms Signed in as your email. The sign-in is kept in your system's credential store (macOS Keychain, Windows Credential Manager or Secret Service on Linux), never in a plain file. The code expires after 10 minutes; run
worsley loginagain if it does.
Start the Worsley relay
your tool talks to its model over an API, so instead of reading files, Worsley sits between the two as a small relay on your own computer. Requests and replies pass through unchanged, streaming included, and Worsley keeps a copy of each exchange.
- 1Start the relay, and leave it running in its own terminal window while you work. Press Ctrl+C to stop it.
worsley proxy --upstream metaIt listens on 127.0.0.1:11435, on this computer only. Port taken? Add --port <number>, and use that port in the next step.
Point your tool at the relay
- 1In your tool's settings, change Meta Model API's address (the base URL) to the address below. Keep your Meta API key as it is.
http://127.0.0.1:11435/v1- 1Use your tool as you normally do. Each exchange is uploaded a few seconds after it finishes and appears in Worsley shortly after.
Your API key goes straight through the relay to the provider over HTTPS. Worsley never records or logs it.
Check that it's working
- Open History in Worsley. Your session shows up there with the tool's name, usually within a minute of a finished turn.
- In the terminal, run
worsley status. It shows the account this computer is signed in to and anything still waiting to upload.
What's captured
- Your prompts, the model's replies and the earlier turns of the conversation, with the model's name.
- Not captured: system prompts, tool calls and their results, images, and thinking.
If a session doesn't appear
- Browser: check that the Worsley icon isn't showing Not Connected, Reconnect or No Site Access, and reload the tool's tab. More in Extension isn't capturing.
- Terminal: check that
worsley watchorworsley proxywas running while you worked, and runworsley status. If it says the sign-in was revoked or expired, runworsley loginagain. - Still missing after a few minutes? Contact support and tell us which tool and which browser or terminal you used.
Related articles
- Capturing sessions in your terminalWorsley captures the AI sessions you run in your terminal, as well as those in your browser.
- Set up local modelsCapture Llama and other models you run on your own computer with Ollama, LM Studio or llama.cpp.
- Session isn't appearingWhat to check when a conversation doesn't show up in Worsley.

