Roadmap
What is next, in the order it matters — and what is deliberately not planned.
Nothing here has a date. The order reflects what would make wisq better for someone using it today, not what is most interesting to build.
Done since
- SPICE
- Complete, and hand-written like the VNC client beside it: display, cursor and input channels on their own connections, sound in both directions, the clipboard through the main channel's agent, and the codecs SPICE invented for itself — LZ, GLZ, QUIC and LZ4 — plus the drawing operations a real desktop leans on.
- Persistence for the local machine
- Solved by saving the machine rather than giving it a disk. The whole state below the kernel — RAM, registers, the timer, the bytes queued for the UART — is written out and restored exactly, so the guest comes back mid-syscall if that is where it was.
Next
- RDP
- The one that matters for Windows guests, and now the only console protocol wisq does not speak. Larger than SPICE by a good margin, and worth doing only properly — the client carries a deliberate stub that refuses rather than pretending.
- More agent backends
- The agent drives libvirt through virsh. Proxmox and plain QEMU without libvirt are both a small amount of code behind the existing interface.
Not planned
- An Android app
- The portable parts are already portable, but the product is the iPhone app. One platform done properly beats two done badly.
- Emulating a desktop operating system locally
- Without a JIT this is a demonstration, not a tool. That is the ceiling wisq is built to avoid rather than to hit.
- A hosted service
- wisq talks to machines you already have. There is no account, no server of ours in the path, and nothing to subscribe to.
- A virtual disk for the local machine
- This was the plan, and it was the wrong one. The rv32 nommu kernels this emulator runs have the virtio-mmio transport but no block driver at all — devtmpfs, proc, ramfs, sysfs, and nothing else. A perfect virtio-blk would have had nobody to talk to, and since you bring your own kernel, whether a disk worked would depend on a build we do not control. Saving the machine sidesteps the guest entirely.