Recordings and history

Reopen a run

Select a VM and open Run History. It includes runs from earlier boots with their command line, user, status, exit code and launch mode. Double-click a run to open its saved trace.

Earlier observations can be inspected while the VM is stopped. Select the appropriate saved run or capture rather than executing the program again.

What is retained

• Raw syscall telemetry and captured objects.
• Run metadata and terminal output.
• Capture all process history.
• Completed static-analysis reports.
• Separate network pcaps for each capture.

An unavailable item is distinct from an empty result. Preserve the run’s error and loss information when exporting observations into notes.

Quotas and storage

The app reports recording storage and quota state. Raw telemetry is written through a bounded background writer queue. Slow storage can still affect observation throughput.

Network pcaps count against the boot’s quota and a running packet capture stops when it is full. Keep host space for both recording data and VM disk overlays.

The default data directory is ~/antinomie, or the directory selected with –data-dir. Use the app’s directory actions to locate a VM’s stored data.

Shut down cleanly

Stopping or closing the app requests guest shutdown, continues collecting during shutdown, then finalizes the recording. A guest that does not stop within the shutdown deadline is forced off and the result is recorded accordingly.

Do not move or replace an active VM’s files. For backups, stop the VM and app first so the disk overlay and recording metadata are no longer being written.