Agents
Meta Muse is a personal agent with its own machine
On September 8, Meta shipped Muse — a personal agent in a secure VM that can act across apps. Here is what that means for builders who still have to ship boards.

On September 8, Meta introduced Muse, a personal agent that does not stop at chat. It runs in Muse Secure VM — a dedicated virtual machine with its own browser — and can work on your behalf across apps you already use, including WhatsApp on iOS and Android.
That is a different product shape from a coding assistant in the IDE. Muse is built for schedules, travel, shopping, and the long tail of digital errands. For hardware teams, the interesting part is architectural: another major platform bet that agents need isolation, tool access, and explicit permission boundaries — not a single model call in a text box.
What Muse actually does
- Proactive help on goals, not only Q&A.
- Runs in a secure VM; user data stays in that environment.
- Rollout in the US first; free tier with paid plans for heavy automation.
- Tied to Meta's model stack under chief AI officer Alexandr Wang.
Meta frames Muse as competition for other personal agents. The privacy story is the whole pitch: you choose how much access the agent gets, and the VM is the trust boundary.
Why hardware builders should care
Most Muse headlines will stay in consumer tech. Your work still lives in KiCad, BOM spreadsheets, and manufacturing email threads. Agents that can book flights will not solder a board.
The pattern that does matter: agents as operators. Muse can chain actions across software surfaces with memory and policy. The same expectation is landing in engineering tools — preflight a board, patch the export, open a build — without you re-explaining the project every session.
That is why we built Gate on MCP, not on a chat skin. Your agent calls eddiant.preflight, reads evaluation.blocker, and only submits a build after you confirm. The checker is the authority. See how it works for the human path on the same thread.
Where Muse stops and a build starts
Muse will not run DRC on your PCB, negotiate a price window, or release a transmitting board before the line. Those steps need structured files, engineer review, and a serial on the traveler — not an autonomous inbox manager.
If your roadmap mixes agent hype with a physical product, split the work clearly:
- Personal agents for coordination and research.
- Manufacturing MCP for CAD, BOM, and intake on a named program.
- A single build record from first articles through production volume.
Muse shipped September 8. Your Gerbers still need a human sign-off before copper moves. That gap is the job — not something a personal agent closes by itself.