msks: microvm workspaces¶
msks is a tool that easily allows you to create microvm workspaces. It can be used to run AI harnesses securely.
Each microvm is a cloud-hypervisor VM with its own kernel. It also provides services which allow you to avoid keeping secrets and keys within the VM, a facility to allow you to approve network egress, and a system that allows you to proxy LLM requests without keeping your API keys on the agent host.
msks runs on:
-
Linux on Intel and ARM systems (Debian/Fedora)
-
macOS on M3+ systems
The reading order¶
- Installation: install the Python wheel, and the commands that prepares hosts.
- The host doctor: the command that checks the host for every tool the daemon and client executes, and suggests the fix for each problem.
- First run: what the daemon lands on its first serve — the CA, the config template, the socket — and the first workspace.
- The TUI: the full-screen workspace tree: the workspace, secrets, and image pages, the consent decider, and terminal windows.
- The CLI client: every command line option:
msksagainst the daemon's HTTP API, ssh and rsync over a forward. - Host share mounts: the host trees a workspace mounts into its guest.
- Guest networking: details about VM guest networking.
- Egress consent: the consent postures, verdicts and durations, switching modes live.
- LLM Proxy: how to make use of msksd's built-in LLM proxy.
- Secrets: placeholders, the swap on the wire, and the sentinel discipline.
- Configuration: the daemon's settings: every key, its environment variable, and its default.
- Workspace images: the image contract, the shipped builder, and the published channel: import from a manifest URL.
- Storage: the state disk, the per-workspace volumes, and a capacity report.
- The HTTP API: the
/api/v1surface itself — the endpoints the commands wrap and the authentication model. - Development environment: the devenv side of a checkout — the dev daemon, the shell's client presets, the worktree identity.
- Changelog: what changed, release by release.