Your coding agents.In Muse.
From Muse, hand work to the coding agents on your Mac.
Invite-only pilot · you approve Muse from your phone or Mac · not reviewed by Meta
Use supported agents you have installed, authenticated and connected.
MuseUse scout to ask a Claude agent to review the latest changes.
- Used scout askworking…reply printed
The Claude agent's review:
- Looks good. One nit: the new helper is exported but unused.
Scout runs Muse
No
Muse runs in Meta's cloud
Replies reach your open session
Not documented
The guide doesn't say. Follow the returned ref.
Start here
- 01 · Connect
Get one route working
Check the prerequisites and access gates, then get one documented route working before asking for work.
Follow the setup → - 02 · Try
Your first useful task
From Muse, ask a coding agent for a short explanation of one function in your project.
Name the project and keep the request small. Asking for no edits describes the task; it does not restrict the agent’s permissions.
- 03 · Read
Wait for the answer
Keep the returned reference. Check the work’s status and read the completed response; a queued receipt is not the answer.
Check what success looks like →
Before your next ask
Where will the reply appear?
The remote client waits and prints the agent’s reply in Muse’s command output.
What if the answer hasn’t arrived?
Inspect the existing task before submitting another one. A wait timeout does not establish that work failed. If it needs access or input, resolve that condition before continuing.
How do I follow up?
Continue using the returned reference or exact session handle supported by this integration. Keep it with the findings so your next question follows the same work.
Can Scout run this integration, or only receive asks from it?
These are separate capabilities. Check the supported directions on this page. Connection alone does not establish that Scout can launch the integration or reach an existing session.
Set it up
Fastest
Give this to Muse
Connect yourself to my Scout. Install the client with `curl -fsSL https://openscout.app/remote/install.sh | sh`, run `scout login --as muse`, and send me the sign-in link it prints. I'll approve it and give you a code; finish with `scout login --code <code>`, then run `scout whoami` and `scout who` and tell me what you see. From then on, hand work to my agents with `scout ask <agent> "<task>"`; `scout --help` lists the rest.
- installs the client
- sends you a sign-in link
- signs in with your code
- checks who it can reach
You need
- Muse's Linux VM does not run a Scout broker or join the mesh. It runs the remote scout client, which calls the broker on your Mac through the hosted gateway at mcp.oscout.net.
- A Muse account (ai.meta.com/muse) with network access to openscout.app and mcp.oscout.net.
- OpenScout on a Mac with a healthy broker (scout doctor) and the MCP bridge running (scout mesh bridge status).
- python3 in Muse's VM (3.8 or newer). Nothing else to install.
- The Scout Mac and its bridge must stay online while Muse works. Muse's VM keeps running when you close the app, so a handoff can outlive your session.
Connect Muse
Start here- 01
Give Muse this message
Paste it into a Muse conversation. It holds no secret: Muse installs the client, starts a login, and sends you a link to approve.
Connect yourself to my Scout. Run: curl -fsSL https://openscout.app/remote/install.sh | sh scout login --as muse Send me the sign-in link it prints. I'll approve it and give you a code; finish with `scout login --code <code>`. Then run `scout whoami` and `scout who` and tell me what you see. From then on, use `scout ask <agent> "<task>"` to hand work to my Scout agents; it waits and prints their reply. Run `scout --help` for the rest. - 02
Approve, and hand back the code
Open the link Muse sends on your phone or Mac. If you're signed in with GitHub, it goes straight to Approve; choose the agent id Muse gets. The page then shows a one-time code: paste it back to Muse. The code is safe in chat: it works once, for a few minutes, and only with a secret that never leaves Muse's VM. Muse's token is saved there, owner-only, never printed, and renews itself.
- 03
Allow the endpoints
If Muse's Settings gate network access, approve openscout.app (the one-time install) and mcp.oscout.net (every call). Start with per-action approval, so you see each Scout call before it runs.
- 04
Hand off work
Ask Muse for something real: “Use scout to ask a Claude agent to review the latest changes in /absolute/path/to/project. Do not edit files. Report what it says.” The path is on the Scout Mac, not in Muse's VM. scout ask waits for the reply; for long work Muse can pass --no-wait and check back with scout wait <id>.
Done when
- scout login prints a sign-in link; after scout login --code, it prints Signed in as muse. scout whoami prints muse. scout who lists your Scout agents.
- A small scout ask prints the agent's reply; with --no-wait it prints an invocation id that scout wait resolves.
An accepted invocation is not completed work.
If it breaks
- scout: the gateway rejected the token
- The sign-in was revoked or not renewed for 30 days. Ask Muse to run scout login again.
- scout: the code was not accepted
- Codes work once and expire within minutes. Ask Muse to run scout login for a fresh link.
- scout: bridge is offline (node_unreachable)
- The gateway is up but the Scout Mac is not connected. On that Mac run scout mesh bridge status and scout doctor. Wake the Mac or restart Scout; retries from Muse will not bring the bridge back.
- python3: command not found
- Ask Muse to install Python 3 in its VM (apt-get install -y python3), then run the install line again.
- Muse tries to install the Scout app or run a broker in its VM
- Stop it. Muse needs only the remote client from openscout.app/remote/install.sh. The Scout daemon is macOS-only, and a broker in the VM would have no agents.
- Calls blocked or waiting
- Sentinel is holding them for approval, or egress to mcp.oscout.net is not allowed. Check the integration's approval mode in Muse Settings.
Where it stops
- Only a listed operator's approval reaches your Mac's bridge. Anyone else who approves a code gets a token for their own account, which has no bridge.
- Stronger isolation: mint with scout mesh bridge token muse on the Scout Mac (it goes to your clipboard, never the screen), store it in Muse's secure credential prompt, and have Muse pipe it to scout login --with-token. Sentinel then keeps the real value outside the VM.
- Core tools only: whoami, ask, invocations, messages, sessions, and work updates. No agents_start, aliases, or terminal control. scout call <tool> reaches any of them directly.
- One identity per token. scout mesh bridge token list shows them; scout mesh bridge token revoke <id> revokes one.
- Scout cannot launch or wake Muse. Muse calls Scout; replies come back through the invocation it holds.
- High-trust local developer pilots. Connection traffic may contain project paths, instructions, messages, and agent results. Data and privacy.