Extensions

MX Studio extensions are child processes. Studio launches them, speaks JSON-RPC 2.0 on a per-extension loopback socket, and serves the same introspection the rest of the app uses. They do not become part of the Studio UI, and they do not add devices.

Extensions need MX Studio Pro. Without that entitlement Settings hides the Extensions page, and every host command returns Extensions need MX Studio Pro.

v1

The shipping contract is v1. Folders, method names, and the handshake all live under that family so a later family can land beside it.

• Overview — what v1 can and cannot do
• Packaging — manifest.json, zip install, launch flags
• Protocol — frames, host.v1.hello, status, shutdown
• Runtime — VMs, state, usage, pause and resume
• Debug — memory, registers, breakpoints, step, pace
• Display — display sources and MXFB0001 framebuffers