What changed in 0.3.0

Released October 10, 2026. These notes describe 0.3.0; this documentation site does not distribute the application archive.

Startup and observation

• Runtime dependency checks run at startup. Missing requirements open the app-dependencies window, and affected actions are blocked.
• VM startup checks QEMU’s GTK capability before starting a graphical VM.
• Capture all retains a process tree with names, call counts and exit codes, available in live and saved captures.

Transport and recording

• Bases built for 0.3.0 support configurable per-vCPU buffers from 256 KiB to 4 MiB, with a 1 MiB default.
• Never drop is the default policy, with a bounded wait deadline of 5 seconds.
• Recording writes run on a background thread with a bounded 256 MiB queue.
• The host event table retires completed calls before unfinished ones.

Older 0.2.0 and 0.1.0 bases remain usable with their legacy transport. The new transport controls require new BusyBox or Debian GNOME bases for 0.3.0.

Analysis and interaction

• NAT network captures can start and stop while the VM runs. Each has its own retained pcap, packet list, filters, byte view and Wireshark integration.
• Terminals update the guest PTY size and retain 10,000 scrollback lines.
• Details supports numeric copy formats and captured-data windows.
• Static analysis shows categories still queued or running.
• Desktop bases can launch into a logged-in guest graphical session.

Base builds

Debian builds can reuse a recently bootstrapped root filesystem with matching answers. Kernel builds use ccache in the builder. Downloading a published base remains the simpler path when a custom image is unnecessary.

Read compatibility and telemetry settings before adopting the new bases.