Overview

v1 is runtime automation. A directory under <app data>/extensions/v1/<id>/ holds manifest.json and a binary. Studio binds 127.0.0.1:0, spawns that binary, and waits 15 seconds for host.v1.hello. After extension.v1.reportStatus the child may call host.v1.*.

There is no plugin crate to link. The host is the contract.

What v1 can do

• list registered VMs and read live run state and usage
• pause, resume, step, set software pace, and force the software engine
• read and write guest memory and one named register
• snapshot every vCPU's registers
• translate a virtual address and disassemble
• list, add, and remove breakpoints
• list display sources and snapshot framebuffers as MXFB0001

The only host capability v1 advertises is runtime.v1.

What v1 cannot do

• No Studio UI. Settings lists the process. That is the whole surface.
• No custom devices, buses, or PCI functions. contributes on the manifest is accepted and ignored.
• No host.v2.*, gui.*, or devices.*. Those names return JSON-RPC -32601.
• No non-loopback sockets. The bind is 127.0.0.1.
• No launch without Pro.

Pages

1. Packaging — on-disk layout, manifest, zip, argv
2. Protocol — frames and the handshake, with a session that speaks the real messages
3. Runtime — listVms, state, usage, pause, resume
4. Debug — debugger, memory, registers, breakpoints
5. Display — sources and framebuffer envelopes